-
Notifications
You must be signed in to change notification settings - Fork 24.4k
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
Very strange behavior of index templates #5000
Comments
I switched to using default-mapping.json (having the 'default' type with 'dynamic_templates' within it). |
Hi @bax1989, can you reproduce this issue? It would be great if you can attach a complete recreation to the issue so that we can reproduce it and understand what causes it. |
I can't give you a concrete scenario since it's a concurrency issue as it seems and does not get reproduced constantly. |
Hi @bax1989 If you're still seeing this issue, then it should be fixed by #8688 |
Observed : Indices are dynamically generated but the mapping lack from some of them.
e.g Items of type 'A' indexed on index 'a' led to the creation of index 'a', the creation of type 'A' on this index, and properties that starts with 'parent_' not being analyzed.
On the other hand, Item Type 'B' which must have been generated on index 'b' isn't there at all, the documents themselves are there (/B/_count returns the correct number, /B/b/_count returns 0). The index metadata returned(b/_mapping) also reveals that there is no type 'B' on the index, only the 'default' type. The documents listed via /b/_search have their type attribute equals to 'B'.
Everything is done from Java Client.
Start node, put template, insert items in parallel.
The text was updated successfully, but these errors were encountered: