Hi,
Although we use logical sharding, there are cases in our environment as you
described. We handle them manually:
0. prepare new version of a document
1. remove the old version of the document
2. post it and commit
With logical sharding it is relatively easy, but we do need to store
location m
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
