Hi there,

Let's say we use custom hashing algorithm and there is a document already
indexed in "shard1". After some time the same document has changed and
should be indexed to "shard2" (because of routing rules used in indexing
program). It has been indexed without issues and as a result 2 "almost" the
same documents are in different shards. In my case, they are duplicates for
the end user. Is it possible to reject a document if it already exists in
different shard ? It would be even easier to handle such cases prior to
adding new with the same ID.

Regards.

Reply via email to