Info
Unlike the splitChunk command, splitVector does not check if the chunk with the exact boundaries exists before performing a scan on the specified range. This can lead to unnecessary work done by the splitVector since the result will be unusable by the splitChunk command. This is because it will be rejected by the chunk exists check.
Top User Comments
schwerin commented on Thu, 19 May 2016 15:37:48 +0000:
I'm pretty sure the hadoop connector uses splitVector, and this change would really just be detecting an error made by the splitting code (in mongos). The splitVector operation as written works as desired.
renctan commented on Tue, 17 May 2016 14:37:27 +0000:
The main use case for splitVector is for splitting chunks and it would be pointless to call it on an input that can produce an output that cannot be used for splitting. It's more of an optimization as opposed to correctness.
schwerin commented on Tue, 17 May 2016 13:09:27 +0000:
I'm not sure this is a bug.
