Hi, I use explicit routing in some of my logging indexes, and I have a *lot* of data. The tool provided to fix the routing issue that showed up in 1.2.0 takes forever on my indexes, but while it has been running, I'm wondering if I even have the problem sketched by the (very informative) blog item. I don't seem to have lost access to events, and am now getting reports of duplicate events.
So, to make this really clear: * Does using explicit routing (in this cased defined in mapping to use a customer id field) have the same routing issue? * Does the tool take explicit routing into account, or am I now messing things up royally? * If so, can I remove those duplicates, while keeping my explicit routing? * All this might be useful to mention in an update to the blog post. I've shutdown the tool for the time being. -- Cheers, ralphm -- 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/27ccbc63-8fb6-4020-9b41-1ad8855426d8%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
