Is your feature request related to a problem or challenge?
Right now when a TaskContext is created from SessionState or SessionContext, the task_id is hardcoded as None; at the same time, there is no way for the user to edit task_id. Thus, task_id as it is right now is effectively useless.
Describe the solution you'd like
It would be nice to allow user to set their own task_id, so that for example, in a custom table provider / physical plan they can log messages along with task_id for tracability.
Describe alternatives you've considered
No response
Additional context
No response
Is your feature request related to a problem or challenge?
Right now when a TaskContext is created from SessionState or SessionContext, the task_id is hardcoded as None; at the same time, there is no way for the user to edit task_id. Thus, task_id as it is right now is effectively useless.
Describe the solution you'd like
It would be nice to allow user to set their own task_id, so that for example, in a custom table provider / physical plan they can log messages along with task_id for tracability.
Describe alternatives you've considered
No response
Additional context
No response