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] Support dropping Flint index in Failed state #2705

Open
dai-chen opened this issue Jun 4, 2024 · 0 comments
Open

[FEATURE] Support dropping Flint index in Failed state #2705

dai-chen opened this issue Jun 4, 2024 · 0 comments
Labels
enhancement New feature or request

Comments

@dai-chen
Copy link
Collaborator

dai-chen commented Jun 4, 2024

Is your feature request related to a problem?

The current implementation of the FlintIndexOpDrop class in the OpenSearch Spark project does not handle the case where an index is in the FAILED state. This can occur when a Spark streaming job terminates with an exception, causing the index state to transition to FAILED. In such cases, the current DROP index statement is unable to clean up the failed index.

What solution would you like?

The proposed solution is adding support for the FAILED precondition in the FlintIndexOpDrop class, specifically in the checkPreconditions method. This would allow the drop index statement to successfully remove indices that are in the FAILED state.

What alternatives have you considered?

One alternative would be to manually delete the failed index using the OpenSearch API. However, this requires deleting index meta log entry in internal request index too.

Do you have any additional context?

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

No branches or pull requests

1 participant