feat: OpenLineage lineage enhancements - full object coverage, richer UI, and API-level sync - #6719
Open
ntkathole wants to merge 3 commits into
Open
feat: OpenLineage lineage enhancements - full object coverage, richer UI, and API-level sync#6719ntkathole wants to merge 3 commits into
ntkathole wants to merge 3 commits into
Conversation
Signed-off-by: ntkathole <nikhilkathole2683@gmail.com>
Signed-off-by: ntkathole <nikhilkathole2683@gmail.com>
|
Codecov Report❌ Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## master #6719 +/- ##
==========================================
- Coverage 46.77% 46.58% -0.19%
==========================================
Files 414 416 +2
Lines 50191 50987 +796
Branches 7181 7352 +171
==========================================
+ Hits 23475 23753 +278
- Misses 25077 25548 +471
- Partials 1639 1686 +47
... and 5 files with indirect coverage changes Continue to review full report in Codecov by Harness.
🚀 New features to boost your workflow:
|
ntkathole
force-pushed
the
lineage_enhancements
branch
2 times, most recently
from
August 10, 2026 05:49
ceaa23c to
e0f64b8
Compare
Signed-off-by: ntkathole <nikhilkathole2683@gmail.com>
ntkathole
force-pushed
the
lineage_enhancements
branch
from
August 10, 2026 07:42
e0f64b8 to
3ad7895
Compare
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
What this PR does / why we need it:
This PR enhances the Feast OpenLineage integration to provide comprehensive, production-ready lineage tracking across all Feast objects and interaction paths.
Full object coverage in lineage: Extends lineage support beyond Feature Views and Feature Services to include SavedDatasets, On-Demand Feature Views, Entities, and DataSources - both in the OpenLineage graph and in Feast-only registry lineage. SavedDatasets now show connectivity to their upstream FeatureService, FeatureViews, and DataSources via storage matching.
Richer OpenLineage UI: Adds producer-based color coding, Feast type filtering, directional focus-on filtering (upstream + downstream without cross-branch bleed), node subtitles showing source type, detailed data source metadata in the side panel (path, table, query, timestamp fields, field mappings), and a toggle that auto-defaults to Feast-only lineage when no OL events exist yet.
API and registry sync: Wires OpenLineage emission and cleanup into the RegistryServer layer so that objects created, edited, or deleted via REST API / gRPC (not just feast apply) are immediately reflected in the lineage graph. Adds delete_dataset and delete_job store methods for clean removal.