Join GitHub today
GitHub is home to over 40 million developers working together to host and review code, manage projects, and build software together.Sign up
Mapping potentially lost with `"dynamic" : "strict"`, `_default_` mapping and failed document index #8650
The effect is very similar to #5623
This can cause several problems:
To fix this, there is two options:
Option 1 is rather tricky to implement and I do not see why the type should not be created in the mapping so I'll make a pr for option 2 shortly.
I just checked 0992e7f, but https://gist.github.com/miccon/a4869fe04f9010015861 still fails.
I suppose that when the mapping is created after the failed indexing request, the _all mapping is set to true (by default) and then the _all cannot by set to false anymore.
IMHO not creating the type at all would be the cleaner solution, because even when the default mapping is set to strict creating the type can prevent you from updating the mapping later on (as the _all mapping is created automatically).