[DOCS-4459] Explicitly call out that moveChunk with 'find' should _not_ be used with hashed shard keys Created: 02/Dec/14  Updated: 16/Mar/15  Resolved: 11/Dec/14

Status: Closed
Project: Documentation
Component/s: manual
Affects Version/s: None
Fix Version/s: v1.3.15

Type: Task Priority: Major - P3
Reporter: Ronan Bohan Assignee: Sam Kleinman (Inactive)
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
Participants:
Days since reply: 9 years, 9 weeks, 6 days ago

 Description   

There are two variants to the 'moveChunk' command, one using 'find' and the other using 'bounds'. On http://docs.mongodb.org/manual/reference/command/moveChunk/ we state that the bounds variant should be used for hashed shard keys. We don't say anything similar for the find variant. We should either:

  • state that this form should not be used for hashed shard keys (balancing the statement in the bounds variant), or (optionally / additionally)
  • state that the document supplied to the find in the case of a hashed shard key should use the hashed value of the shard key, not the raw value of the shard key (problem is that to get the hash you need to use the internal _hasBSONElement command)


 Comments   
Comment by Githook User [ 11/Dec/14 ]

Author:

{u'username': u'tychoish', u'name': u'Sam Kleinman', u'email': u'samk@10gen.com'}

Message: DOCS-4459: clarify move chunk and hashed shard key
Branch: master
https://github.com/mongodb/docs/commit/c9382cac7161aef843eb5501f10ae6e31242d659

Generated at Thu Feb 08 07:48:02 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.