Description
OpenLineage events generated by Airflow tasks currently do not include information about the provider package version. This missing metadata makes it difficult to track which version of a provider package was responsible for generating specific lineage events, which is important for debugging, auditing, and understanding lineage data provenance.
Use case/motivation
OpenLineage events should include the provider package version that generated the event. This missing metadata creates challenges for debugging when lineage data is incorrect, knowing the provider version helps identify if issues are version-specific
Desired behavior: Include provider package version in OpenLineage events alongside existing metadata.
Related issues
NA
Are you willing to submit a PR?
Code of Conduct
Description
OpenLineage events generated by Airflow tasks currently do not include information about the provider package version. This missing metadata makes it difficult to track which version of a provider package was responsible for generating specific lineage events, which is important for debugging, auditing, and understanding lineage data provenance.
Use case/motivation
OpenLineage events should include the provider package version that generated the event. This missing metadata creates challenges for debugging when lineage data is incorrect, knowing the provider version helps identify if issues are version-specific
Desired behavior: Include provider package version in OpenLineage events alongside existing metadata.
Related issues
NA
Are you willing to submit a PR?
Code of Conduct