You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In data warehousing scenario, a data load batch/session ID would be good to have in the loaded data, in order to preserve history and distinguish between load runs.
There is a LocalExecutionId field in CurrentExecution/ExecutionLog tables, which seems to have exactly the data required. It would be just enough to add that ID to parameters of a worker pipeline and leave a developer of a worker pipeline to optionally include that parameter in the data.
If I were to implement it, I'd concatenate that value with others in this list: activity('Get Pipeline Params').output.firstRow.Params and use in the Azure Function activity "Execute Worker Pipeline" in the pipeline 04-Infant.
The text was updated successfully, but these errors were encountered:
In data warehousing scenario, a data load batch/session ID would be good to have in the loaded data, in order to preserve history and distinguish between load runs.
There is a LocalExecutionId field in CurrentExecution/ExecutionLog tables, which seems to have exactly the data required. It would be just enough to add that ID to parameters of a worker pipeline and leave a developer of a worker pipeline to optionally include that parameter in the data.
If I were to implement it, I'd concatenate that value with others in this list: activity('Get Pipeline Params').output.firstRow.Params and use in the Azure Function activity "Execute Worker Pipeline" in the pipeline 04-Infant.
The text was updated successfully, but these errors were encountered: