-
Notifications
You must be signed in to change notification settings - Fork 25.2k
Mappings defined at index creation time in YAML are ignored #1755
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
Not for the create index API, in this case, ti is expected to be in json... |
Sorry, I meant when you provide both settings and mappings, it is expected to be provided in json, not |
Thanks! I'm sure documenting this will be useful to others. |
Is this still the case? The documentation is still unclear: https://www.elastic.co/guide/en/elasticsearch/reference/current/indices-create-index.html |
"stashing" the thread context is typically used to execute something with a differenet set of privileges (access to system indices, or a different user). In these cases we don't want to lose the project-id from the context (just like we don't want to lose APM tracing information). This change preserves the project-id during stash.
According to documentation I would have assumed that creation of mappings work in YAML too (since the first example on that page uses it):
http://www.elasticsearch.org/guide/reference/api/admin-indices-create-index.html
In JSON, it works as expected:
But, the following doesn't work:
Below is my indexing and searching setup:
tested with 0.18 and 0.19.
Sorry for formatting. Github Markdown seems broken.
The text was updated successfully, but these errors were encountered: