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
As described in OpenLineage/OpenLineage#664 , the OpenLineage Airflow implementation has always sent back the ParentRunFacet with less than correct information in the runId and job name fields. It's possible to backfill this information in existing databases, which is necessary for a complete and correct implementation of #1928 .
The approach would be to split the parent job name on the . character to determine the DAG name and concatenate that with the runId (usually something like scheduled__2022-03-14T01:40:10+00:00) to generate UUID (see UUIDv3 generation in the OpenLineage implementation here). Note that some job names have the DAG followed by the task group, then the task id, all separated by . characters, so we should choose the left-most name of the task id.
The text was updated successfully, but these errors were encountered:
As described in OpenLineage/OpenLineage#664 , the OpenLineage Airflow implementation has always sent back the
ParentRunFacet
with less than correct information in therunId
and jobname
fields. It's possible to backfill this information in existing databases, which is necessary for a complete and correct implementation of #1928 .The approach would be to split the parent job name on the
.
character to determine the DAG name and concatenate that with the runId (usually something likescheduled__2022-03-14T01:40:10+00:00
) to generate UUID (see UUIDv3 generation in the OpenLineage implementation here). Note that some job names have the DAG followed by the task group, then the task id, all separated by.
characters, so we should choose the left-most name of the task id.The text was updated successfully, but these errors were encountered: