feat(metadata-integration/openlineage): support env and orchestrator in openlineage event emission #15251
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…in openlineage event emission
github-actions
bot
added
ingestion
datahub-cyborg
bot
added
the
needs-review
Codecov Report❌ Patch coverage is
📢 Thoughts on this report? Let us know! |
...openlineage-converter/src/test/java/io/datahubproject/openlineage/OpenLineageConfigTest.java
Show resolved
Hide resolved
datahub-cyborg
bot
added
pending-submitter-response
treff7es
reviewed
Nov 11, 2025
...src/test/java/io/datahubproject/openapi/openlineage/config/OpenLineageServletConfigTest.java
Outdated
Show resolved
Hide resolved
datahub-cyborg
bot
added
needs-review
datahub-cyborg
bot
added
pending-submitter-response
datahub-cyborg
bot
added
needs-review
sgomezvillamor
approved these changes
Nov 11, 2025
datahub-cyborg
bot
added
pending-submitter-merge
and removed
needs-review
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Add Configurable Environment and Orchestrator for OpenLineage Integration
Adding flexible configuration options for the DataHub OpenLineage REST endpoint, allowing users to customize the environment/fabric type and orchestrator without requiring code changes or modifying OpenLineage events.
Motivation
DataHub's OpenLineage endpoint previously had hardcoded values:
Fabric Type: Always set to PROD
Orchestrator: Tightly coupled to either the processing_engine facet or producer URL parsing
This limitation prevented users from:
Ingesting metadata from multiple environments (DEV, TEST, QA, STG, etc.) into a single DataHub instance
Using custom orchestrators or metadata management tools (Unity Catalog, Dataplex, DataWorks, custom platforms) that don't match known patterns