Currently there are no guards in reindex_array against sending multiple source chunks to the same destination, which means that whoever writes last will win. This is a risk that users of reindex probably just need to accept - but we can consider if it would be easy to keep track of all the locations we have moved a chunk to, and then error if we write to one more than once.
Currently there are no guards in
reindex_arrayagainst sending multiple source chunks to the same destination, which means that whoever writes last will win. This is a risk that users ofreindexprobably just need to accept - but we can consider if it would be easy to keep track of all the locations we have moved a chunk to, and then error if we write to one more than once.