Draft
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
We expose the Elasticsearch
_reindexAPI via a new HTTP endpoint on the status server. This allows for triggering manual reindexing operations directly.Usage
To trigger a reindex, send a
POSTrequest to the/reindexendpoint of the status server (default port12800). The body of the request should contain the standard Elasticsearch reindex JSON payload.Example
Implementation Details
The implementation involves:
Reindexmethod has been added to the internal client./reindexaccepts JSON requests and proxies them to the Elasticsearch_reindexAPI.