Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Propagate Caching information to FlyteAdmin #138

Closed
chanadian opened this issue Dec 11, 2019 · 3 comments
Closed

Propagate Caching information to FlyteAdmin #138

chanadian opened this issue Dec 11, 2019 · 3 comments
Assignees
@kumare3
Labels
enhancement New feature or request pri2
Milestone
0.6.0

Comments

@chanadian
Copy link
Contributor

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
@chanadian chanadian added enhancement New feature or request pri2 labels Dec 11, 2019
@georgesnelling georgesnelling mentioned this issue Dec 11, 2019
Closed
@kumare3 kumare3 added this to the 0.5.0 milestone May 22, 2020
@kumare3 kumare3 pinned this issue May 22, 2020
@kumare3 kumare3 unpinned this issue May 28, 2020
@EngHabu EngHabu removed this from the 0.5.0 milestone Jun 25, 2020
@kumare3
Copy link
Contributor

kumare3 commented Jul 7, 2020

related to #71

@kumare3 kumare3 added this to the 0.6.0 milestone Jul 7, 2020
@kumare3 kumare3 self-assigned this Jul 7, 2020
@kumare3 kumare3 mentioned this issue Jul 7, 2020
Merged
8 tasks
This was referenced Jul 24, 2020
Merged
Merged
Merged
@kumare3
Copy link
Contributor

kumare3 commented Jul 28, 2020

In Review:
flyteorg/flyteidl#70
flyteorg/flyteplugins#105
flyteorg/flytepropeller#167
flyteorg/flyteadmin#110

@kumare3 kumare3 closed this as completed Jul 31, 2020
@kumare3
Copy link
Contributor

kumare3 commented Jul 31, 2020

now merged

eapolinario pushed a commit to eapolinario/flyte that referenced this issue Dec 6, 2022
@honnix
Archive and unarchive a project (flyteorg#138)
463bfb6 
* Use state for a project to archive or activate it
eapolinario pushed a commit to eapolinario/flyte that referenced this issue Dec 20, 2022
@akhurana001
Update Spark Plugin (flyteorg#138)
3421687
eapolinario pushed a commit to eapolinario/flyte that referenced this issue Dec 20, 2022
@iaroslav-ciupin
Extract out data store metrics for re-usability (flyteorg#138)
bcfa537 
* 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
@yindia
#none fixed storage config in docs (flyteorg#138)
7c4a270
eapolinario pushed a commit to eapolinario/flyte that referenced this issue Aug 21, 2023
@honnix
Archive and unarchive a project (flyteorg#138)
d184a33 
* Use state for a project to archive or activate it
eapolinario pushed a commit to eapolinario/flyte that referenced this issue Aug 21, 2023
@akhurana001
Update Spark Plugin (flyteorg#138)
991d724
eapolinario pushed a commit to eapolinario/flyte that referenced this issue Aug 21, 2023
@iaroslav-ciupin
Extract out data store metrics for re-usability (flyteorg#138)
cb61229 
* 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
@yindia
#none fixed storage config in docs (flyteorg#138)
81471f1
austin362667 pushed a commit to austin362667/flyte that referenced this issue May 7, 2024
@yindia @austin362667
#none fixed storage config in docs (flyteorg#138)
f9efd04
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@kumare3 kumare3

Labels
enhancement New feature or request pri2
Projects
None yet
Milestone
0.6.0
Development

No branches or pull requests
3 participants
@EngHabu @chanadian @kumare3