-
Notifications
You must be signed in to change notification settings - Fork 25.2k
Reindex from remote cluster #17447
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
Comments
I like the syntax. I think we'll need the http based java API for it though. |
Not necessarily. A simple HTTP client should be sufficient for this. |
+1 @nik9000 eagerly waiting for this to be released in 1.x |
It'll be a 5.0 or 5.1 feature depending on when I get time to really start it. You should be able to connect to 1.x with it though. |
Is the _source._ingest feature working to get metadata fields from a remote source? I can't get it to work. Have tried posting in forum, no response. |
Could you tell what would happen to data that is created or updated when performing reindex api? |
Reindex sees a consistent view of the data. It won't notice the changes. |
So how to add that changes. |
We don't have native support for that. If you ask around on discuss.elastic.co you might find people that have some solutions. |
Hey Guys, Have you tried changing the remote host from this format "host": "192.168.1.2:9200", to this format "host": "https://something.com" ? Thanks for the help! |
The reindex API should be able to pull data from an index in a remote cluster. This would allow importing an index in a 1.x cluster into a cluster running Elasticsearch 5 or later.
The syntax could look like this:
The
username
andpassword
and any other options withinremote
would be used to configure the HTTP client contacting the remote server, and thequery
etc would be passed to the remote server without parsing (which deals with any API changes).The text was updated successfully, but these errors were encountered: