-
Notifications
You must be signed in to change notification settings - Fork 24.9k
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
add indices pipeline settings check when deleting a pipeline #77013
add indices pipeline settings check when deleting a pipeline #77013
Conversation
…ted in the index configuration
Pinging @elastic/es-data-management (Team:Data Management) |
@elasticmachine ok to test |
@elasticmachine update branch |
@elasticmachine run elasticsearch-ci/part-1 |
@weizijun, thank you for this contribution. It's a helpful improvement and we'd like to get it merged. There are a couple failing tests:
Each of those tests is attempting to delete an ingest pipeline that is either default or final on an index. The fix for those will be to delete the index before deleting the ingest pipeline. If you can make those changes, we'll get this reviewed and merged. |
ok, I will fix, and passed ./gradlew check |
@danhermann I have fixed the failed tests. but the elasticsearch-ci/part-1 is blocked |
@elasticmachine run elasticsearch-ci/part-1 |
@elasticmachine ok to test |
@elasticmachine update branch |
@elasticmachine update branch |
hi, @danhermann, all tests passed. can you help to review this PR? |
@weizijun, apologies for the delay on this one. I will review it and help you to get it merged. One suggestion for improvement that I have is to update the error message to include the number of indices from which the pipeline must first be removed. Perhaps something like this:
That way a user is informed immediately about the number of places from which the ingest pipeline must be removed before it can be deleted rather than removing it from the first index, attempting to delete it again, finding that it cannot be deleted because it's used on another index, etc. The "including" list of indices might include just the first 3 indices encountered in case it's used on a large number of indices. |
* upstream/master: (250 commits) [Transform] HLRC cleanups (elastic#78909) [ML] Make ML indices hidden when the node becomes master (elastic#77416) Introduce a Few Settings Singleton Instances (elastic#78897) Simplify TestCluster extraJar configuration (elastic#78837) Add @OverRide annotations to methods in EnrichPlugin class (elastic#76873) Add v7 restCompat for invalidating API key with the id field (elastic#78664) EQL: Refine repeatable queries (elastic#78895) Fix DataTierTests package and add a validation test (elastic#78880) Fix split package org.elasticsearch.common.xcontent (elastic#78831) Store DataTier Preference directly on IndexMetadata (elastic#78668) [DOCS] Fixes typo in calendar API example (elastic#78867) Improve Node Shutdown Observability (elastic#78727) Convert encrypted snapshot license object to LicensedFeature (elastic#78731) Revert "Make nodePaths() singular (elastic#72514)" (elastic#78801) Fix incorrect generic type in PolicyStepsRegistry (elastic#78628) [DOCS] Fixes ML get calendars API (elastic#78808) Implement GET API for System Feature Upgrades (elastic#78642) [TEST] More MetadataStateFormat tests (elastic#78577) Add support for rest compatibility headers to the HLRC (elastic#78490) Un-ignoring tests after backporting fix (elastic#78830) ... # Conflicts: # server/src/main/java/org/elasticsearch/ingest/IngestService.java # server/src/test/java/org/elasticsearch/ingest/IngestServiceTests.java
@elasticmachine run elasticsearch-ci/bwc |
@elasticmachine update branch |
@elasticmachine run elasticsearch-ci/part-2 |
@elasticmachine update branch |
@elasticmachine run elasticsearch-ci/part-2 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@weizijun, the one remaining test failure is a known flaky test, so this looks good. I'll get it merged and backported for the appropriate release. Thanks for building this feature!
@danhermann thank you for review this PR! |
When deleting a pipeline, check whether the pipeline is actually deleted in the indices settings.
If the indices have the deleting pipeline, fail the delete request.