-
Notifications
You must be signed in to change notification settings - Fork 20
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
Is index.version.created supposed to be fixed? #17
Comments
No, elasticsearch check the version itself. |
Interesting. The results are the same if I leave out |
@kiwionly Do you know what value Elasticsearch is querying specifically? The plugin is built for |
Could you explain more, I think u should just leave the index version settings when creating index as ES check the versioning. |
If I set the Example error when creating an index using
Results in this error from
The errors from Elasticsearch directly are pretty much the same:
Thanks, |
I check ES code it check the versioning, that why put that here to ensure it work. You might want to review the code in ES. |
Response from the Elasticsearch team:
|
This plugin is port from ES 2.1 and I suspected the fork I using possible not port to index version more then 2 yet. My first goal is to make it work, for the upgrade I still no plan, probably will take a look only when got time. |
Hi,
In my index settings I changed the
index.version.created
number from the example1070499
to the propper version to match my ES deployment (2030399
) and creating mappings after doing so fails withIs this hard-coded somewhere in the plugin itself?
Cheers,
D
The text was updated successfully, but these errors were encountered: