Amit, One solid work-around is to always create the index before you bulk-load it. Either with explicit mappings or letting ES guess them by default should work fine. It should get you by until the bug is fixed in a future release, and should be rather easy to implement.
In my case, I lock down ES to prevent auto-index creation and auto-create of unmapped fields, so I must always create the index and its mappings before loading data into the index. This means that I haven't run into this bug. And it's not a bad workaround; in fact, it is a very good practice. Sometimes ES guesses wrong. It can't read my mind, so I don't expect it to. Hope this helps. Brian -- You received this message because you are subscribed to the Google Groups "elasticsearch" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/0eba0b15-d012-4858-b6c5-3f10591c6869%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
