AIP-62: add lineage support for Object Store #40829
Merged
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.
This PR is based on #40819
This adds support for getting lineage directly from Object Store's
ObjectStoragePath
.Not every operation is being tracked, only those that modify or read the files, not the metadata.
Copy/rename/move operations are being tracked internally, while for tracking reads and writes there's
TrackingFileWrapper
- proxy that collects reads and writes.This allows also tracking data reads/writes from other systems that accept file APIs - for example, from Object Store tutorial in Airflow:
can generate lineage.
FileTransferOperator
already has OL support (AIP-53 one).