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
The OpenLineage standard column lineage facet has been extended in 1.17.1 so that each field in inputFields can now have an array of transformations describing transformations specific to that input field in the context of the output field. See OpenLineage/OpenLineage#2756.
Ideally Marquez should support storing and serving this data if present in OpenLineage events.
Note that the existing transformationType and transformationDescription fields at the output field level still exist but have been deprecated.
Database
The corresponding table in Marquez would be column_lineage, with each row there effectively representing one entry in inputFields. We could add another table joining with this e.g. column_lineage_transformations or - perhaps more pragmatically - use a JSON column on the existing table to hold transformations.
API
The transformations array could be added to the ColumnLineageInputField model which is included in the column lineage response and the dataset response.
The text was updated successfully, but these errors were encountered:
I'd be happy to contribute this change (since I would also like to see the feature implemented), but would probably need a little guidance on how to get started
The OpenLineage standard column lineage facet has been extended in 1.17.1 so that each field in
inputFields
can now have an array oftransformations
describing transformations specific to that input field in the context of the output field. See OpenLineage/OpenLineage#2756.Ideally Marquez should support storing and serving this data if present in OpenLineage events.
Note that the existing
transformationType
andtransformationDescription
fields at the output field level still exist but have been deprecated.Database
The corresponding table in Marquez would be
column_lineage
, with each row there effectively representing one entry ininputFields
. We could add another table joining with this e.g.column_lineage_transformations
or - perhaps more pragmatically - use a JSON column on the existing table to hold transformations.API
The
transformations
array could be added to theColumnLineageInputField
model which is included in the column lineage response and the dataset response.The text was updated successfully, but these errors were encountered: