Document bounds parameter of moveChunk
(DOCS-990)
|
|
| Status: | Closed |
| Project: | Documentation |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | v1.2 |
| Type: | Sub-task | Priority: | Major - P3 |
| Reporter: | Thomas Rueckstiess | Assignee: | Ed Costello |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||
| Participants: | |||||
| Days since reply: | 10 years, 49 weeks, 2 days ago | ||||
| Description |
|
The "find" parameter in the moveChunk command is misleading, as it sounds like any regular find query could be used here to specify a chunk. This is not the case and needs to be stated more clearly. In particular, the find parameter must include the shard key as an equality match, it is not possible to include any comparison operators like $gt or $lt. Doing this will not result in an error, but instead in a different chunk to be moved, as the value will be treated as a document type which compares higher than any numbers or strings. |