-
Notifications
You must be signed in to change notification settings - Fork 791
SOLR-17725: CoreAdmin API to upgrade an index in-place to facilitate Solr upgrade across major versions #3903
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
base: main
Are you sure you want to change the base?
Conversation
|
First (half-baked) draft. WIP. |
…ion for custom update.chain
3085bea to
daaaecb
Compare
|
Looking good. Basic (manual) tests with /admin/cores?action=UPGRADECOREINDEX working fine. Will publish response with segment status before and after index upgrade. Also need to add tests. |
… has been renamed. It's being used in this feature..
|
Sample response in synchronous mode (/admin/cores?action=UPRGADECOREINDEX&core=techproducts) Sample response in async mode ("/admin/cores?action=UPRGADECOREINDEX&core=techproducts&async=request_id" and checking status with action=REQUESTSTATUS) |
https://issues.apache.org/jira/browse/SOLR-17725
Description
Provide a /admin/cores api (action=UPGRADECOREINDEX) to upgrade older lucene segments to latest version (by targeted reindexing). Calling this REST endpoint on an index created in version X-1 (assuming you are on version X) would help prepare the index for when Solr is upgraded to X+1 without having to recreate the index from source.
Solution
Please provide a short description of the approach taken to implement your solution.
Tests
Please describe the tests you've developed or run to confirm this patch implements the feature or solves the problem.
Checklist
Please review the following and check all that apply:
mainbranch../gradlew check.