-
Notifications
You must be signed in to change notification settings - Fork 310
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Adds metadata to FlyteFile #3160
base: master
Are you sure you want to change the base?
Adds metadata to FlyteFile #3160
Conversation
Signed-off-by: Thomas J. Fan <[email protected]>
Signed-off-by: Thomas J. Fan <[email protected]>
Code Review Agent Run #6d466dActionable Suggestions - 9
Additional Suggestions - 1
Review Details
|
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## master #3160 +/- ##
==========================================
- Coverage 83.58% 74.67% -8.92%
==========================================
Files 3 212 +209
Lines 195 22040 +21845
Branches 0 2866 +2866
==========================================
+ Hits 163 16458 +16295
- Misses 32 4778 +4746
- Partials 0 804 +804 ☔ View full report in Codecov by Sentry. |
Changelist by BitoThis pull request implements the following key changes.
|
Signed-off-by: Thomas J. Fan <[email protected]>
Signed-off-by: Thomas J. Fan <[email protected]>
Code Review Agent Run #7a5220Actionable Suggestions - 1
Review Details
|
…file-metadata Signed-off-by: Thomas J. Fan <[email protected]>
Code Review Agent Run #a08b41Actionable Suggestions - 0Review Details
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Do you think it's worth reserving certain fields (e.g. file size)?
I do not think we need to reserve them. If we have file size, we can add it by default, but then a user can override it. I'm on the fence about automatically adding metadata, because there is no way for Flyte to make sure it's in sync. With user provided metadata, it is the user's responsible to make sure the reference does not change underneath them. |
fsspec has tbh, I'd be ok with adding metadata by default (controlled by an env var) and an explanation in the docs. |
Tracking issue
Closes flyteorg/flyte#6257
Why are the changes needed?
With this PR, metacata can be attached to a FlyteFile.
What changes were proposed in this pull request?
This PR adds
metadata
to FlyteFile so that it an adjust the Literal's metadata.How was this patch tested?
Unit test and integration tests were updated.
The UI automatically shows the new metadata:
Summary by Bito
This PR has two main components: 1) Adds metadata support to FlyteFile with serialization/deserialization handling and type validation, enabling storage of string key-value pairs and preserving metadata during workflow execution. 2) Implements modular agent-related dependencies by moving them to an optional dependency group, with updates to Dockerfile.agent and dependency management through pyproject.toml.Unit tests added: True
Estimated effort to review (1-5, lower is better): 2