-
Notifications
You must be signed in to change notification settings - Fork 672
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
Propagate Caching information to FlyteAdmin #138
Comments
related to #71 |
8 tasks
This was referenced Jul 24, 2020
Merged
now merged |
eapolinario
pushed a commit
to eapolinario/flyte
that referenced
this issue
Dec 6, 2022
* Use state for a project to archive or activate it
eapolinario
pushed a commit
to eapolinario/flyte
that referenced
this issue
Dec 20, 2022
eapolinario
pushed a commit
to eapolinario/flyte
that referenced
this issue
Dec 20, 2022
* Extract out data store metrics for re-usability and add RefreshConfig method to DataStore * Add some tests to improve coverage
eapolinario
pushed a commit
to eapolinario/flyte
that referenced
this issue
Dec 20, 2022
eapolinario
pushed a commit
to eapolinario/flyte
that referenced
this issue
Aug 21, 2023
* Use state for a project to archive or activate it
eapolinario
pushed a commit
to eapolinario/flyte
that referenced
this issue
Aug 21, 2023
eapolinario
pushed a commit
to eapolinario/flyte
that referenced
this issue
Aug 21, 2023
* Extract out data store metrics for re-usability and add RefreshConfig method to DataStore * Add some tests to improve coverage
eapolinario
pushed a commit
to eapolinario/flyte
that referenced
this issue
Apr 30, 2024
austin362667
pushed a commit
to austin362667/flyte
that referenced
this issue
May 7, 2024
robert-ulbrich-mercedes-benz
pushed a commit
to robert-ulbrich-mercedes-benz/flyte
that referenced
this issue
Jul 2, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
When Propeller successfully looks up a cached task execution, it needs to propagate that information in the NodeEvent. FlyteAdmin should store the information that the node execution has a cached task execution. This information could include the original execution which populated the cache and expose that in the NodeExecutions response objects.
The UI/CLI then has the capability to show an indication if a task execution is cached and from what lineage. Here is the corresponding UI issue: #21
The text was updated successfully, but these errors were encountered: