Hey Andrzej,
Thank you for your response.
In this specific case updated field is not id or unique field, it is just
some random field I am using for routing. So in this case, it may make
sense to be able to route document to new location by updating (atomic or
not) :).
I would think that
Hi Niko,
Please create a Jira issue, this looks like a bug. It also needs more
discussion - I’m not convinced we should allow updates (atomic or not) to the
id field, because (as the name suggests) this field defines the identity of the
document, and if the identity is modified is it still the
Hello,
I came up with a situation with collection created with "router.field" and
using atomic update format for route.field in document that documents were
routed into wrong shard in CompositeIdRouter.
After doing some investigation I noticed that CompositeIdRouter#sliceHash
takes field value
