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.

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

[Core feature] Cache eviction override for a single execution #2867

Open
2 tasks done
MorpheusXAUT opened this issue Sep 12, 2022 · 4 comments · May be fixed by flyteorg/flyteconsole#851
Open
2 tasks done

[Core feature] Cache eviction override for a single execution #2867

MorpheusXAUT opened this issue Sep 12, 2022 · 4 comments · May be fixed by flyteorg/flyteconsole#851
Assignees
Labels
datacatalog DataCatalog related issues enhancement New feature or request flytepropeller stale

Comments

@MorpheusXAUT
Copy link
Contributor

Motivation: Why do you think this is important?

As suggested in #2633, cache eviction/cleanup functionality provides Flyte users as well as administrators with more control about what data is to be cached by Flyte and allows for cleanup of no longer required results.

Goal: What should the final outcome look like, ideally?

This issue tracks implementation of the first suggested part of the RFC, providing a cache eviction override for a single execution.

flyteadmin and flytepropeller should allow users to skip any existing cache for a single execution, overwriting any stored data in datacatalog after the execution finishes successfully.

All relevant Flyte clients (flyteconsole, flytekit, flytectl) should support the new override functionality.

Describe alternatives you've considered

As no similar functionality exists (except manually deleting entries in datacatalog's Postgres database and blob storage), no alternatives were considered in the RFC.

Propose: Link/Inline OR Additional context

https://hackmd.io/qOztkaj4Rb6ypodvGEowAg?view#Cache-eviction-override-for-a-single-execution

Are you sure this issue hasn't been raised already?

  • Yes

Have you read the Code of Conduct?

  • Yes
@MorpheusXAUT MorpheusXAUT added enhancement New feature or request untriaged This issues has not yet been looked at by the Maintainers labels Sep 12, 2022
@MorpheusXAUT MorpheusXAUT self-assigned this Sep 12, 2022
@MorpheusXAUT
Copy link
Contributor Author

I'm currently in the process of implementing this based on our RFC. This issue was mainly created as a tracking issue for the various PRs to come across Flyte repos.

If you'd prefer, I can also split this into smaller issues per Flyte component.

@eapolinario eapolinario removed the untriaged This issues has not yet been looked at by the Maintainers label Sep 16, 2022
@github-actions
Copy link

github-actions bot commented Sep 4, 2023

Hello 👋, This issue has been inactive for over 9 months. To help maintain a clean and focused backlog, we'll be marking this issue as stale and will close the issue if we detect no activity in the next 7 days. Thank you for your contribution and understanding! 🙏

@github-actions github-actions bot added the stale label Sep 4, 2023
@hamersaw
Copy link
Contributor

hamersaw commented Sep 6, 2023

Commenting to keep open.

@github-actions github-actions bot removed the stale label Sep 7, 2023
@pvditt pvditt self-assigned this Jan 22, 2024
@pingsutw pingsutw added flytepropeller datacatalog DataCatalog related issues labels Feb 15, 2024
@pvditt pvditt linked a pull request Mar 12, 2024 that will close this issue
8 tasks
Copy link

Hello 👋, this issue has been inactive for over 9 months. To help maintain a clean and focused backlog, we'll be marking this issue as stale and will engage on it to decide if it is still applicable.
Thank you for your contribution and understanding! 🙏

@github-actions github-actions bot added the stale label Nov 12, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
datacatalog DataCatalog related issues enhancement New feature or request flytepropeller stale
Projects
None yet
5 participants