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

[FEATURE] Checkpoint folder data cleanup limitation #102

Closed
dai-chen opened this issue Oct 25, 2023 · 1 comment
Closed

[FEATURE] Checkpoint folder data cleanup limitation #102

dai-chen opened this issue Oct 25, 2023 · 1 comment
Assignees
Labels
enhancement New feature or request

Comments

@dai-chen
Copy link
Collaborator

dai-chen commented Oct 25, 2023

Is your feature request related to a problem?

Currently Flint pass the exact same checkpoint location path given by user to Spark. It's user responsibility to:

  1. Make sure the checkpoint location is used by only 1 Flint index refreshing
  2. Clean up the checkpoint folder after Flint index drop

What solution would you like?

Flint cleans up the folder when user drops index. Add this to limitation doc if no time to improve this in 0.1.1 release.

@dai-chen dai-chen added enhancement New feature or request untriaged labels Oct 25, 2023
@dai-chen dai-chen assigned dai-chen and unassigned dai-chen Oct 25, 2023
@dai-chen dai-chen added 0.1.1 and removed untriaged labels Oct 25, 2023
@dai-chen
Copy link
Collaborator Author

This limitation could be removed in #104.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Development

No branches or pull requests

1 participant