On Tue, Jun 10, 2014 at 11:44 PM, Ralph Meijer <[email protected]> wrote: > > * Does using explicit routing (in this cased defined in mapping to use a > customer id field) have the same routing issue? >
Yes. The issue is on the hashing function, so it occurs when using explicit routing as well. > * Does the tool take explicit routing into account, or am I now messing > things up royally? > Yes it does. When you use custom routing, either explicitely by setting the routing value in the mappings or indexing requests, or implicitely in case of parent/child, Elasticsearch stores a special `_routing` value that the tool uses in order to identify the right shard for this document. * If so, can I remove those duplicates, while keeping my explicit routing? > Yes: the tool has a `delete` action to remove documents that have been routed to the wrong shard. -- Adrien Grand -- 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/CAL6Z4j6faxqZkLH7ghO7%3DkkWXgWp7ZXPQKG9xVTtTV-n1zcmoA%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
