Skip to content

Conversation

@kacpermuda
Copy link
Contributor

@kacpermuda kacpermuda commented Feb 27, 2024

When using inlets/outlets with OpenLineage, only Table entity was supported (without schema). This PR adds support for Table's schema, File entity and User entity as Table owners - this adds ownership schema to the Dataset.


^ Add meaningful description above
Read the Pull Request Guidelines for more information.
In case of fundamental code changes, an Airflow Improvement Proposal (AIP) is needed.
In case of a new dependency, check compliance with the ASF 3rd Party License Policy.
In case of backwards incompatible changes please leave a note in a newsfragment file, named {pr_number}.significant.rst or {issue_number}.significant.rst, in newsfragments.

Copy link
Contributor

@dirrao dirrao left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I believe good to add example DAG.

@kacpermuda
Copy link
Contributor Author

I believe good to add example DAG.

There is one here, and also when #37620 is merged, it will be in provider docs - then I'll update the information, that the File is also supported 😉

@kacpermuda kacpermuda changed the title [OpenLineage] feat: Add OpenLineage support for File lineage entity as inlet/outlet [OpenLineage] feat: Add OpenLineage support for File and User Airflow's lineage entity Feb 28, 2024
@kacpermuda kacpermuda force-pushed the feat/ol-add-file-lineage-support branch from fbb22fa to d980ba6 Compare February 28, 2024 16:16
@kacpermuda kacpermuda force-pushed the feat/ol-add-file-lineage-support branch from d980ba6 to ad65747 Compare February 28, 2024 17:41
@kacpermuda
Copy link
Contributor Author

I added support for File, Column and User entities and adjusted the documentation to reflect that change. It should be good to go now 🚀

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants