Loading...

XML

Word

Printable

JSON

Type: Improvement
Resolution: Fixed
Priority: Major - P3
Fix Version/s: 3.4.16, 3.6.5, 4.0.0-rc0
Affects Version/s: None
Component/s: Sharding
Labels:
None

Backwards Compatibility:
Fully Compatible
Backport Requested:

v3.6, v3.4
Sprint:
Sharding 2018-05-07
Case:
Confidence Status:
None
Work Order:
3

Aha! Reference:
None
Tracking Level:
None
Risk Status:
None
Exec Notes:
None
Goal Name:
None
Goal Link:
None

The moveChunk/mergeChunks commands do not introduce any new chunk boundaries that do not already exist. Disallowing specifying shard keys with $ in the field names that they accept prevents fixing sharding routing information, which might inadvertently have been created by older versions of the server.

Because of this we should disable these checks.

is related to

SERVER-32862 sh.addShardToZone() allows unusual (invalid?) chunks to be created

Closed

related to

SERVER-6349 sh.addTagRange() doesn't valid namespace is sharded, nor min/max are valid for the shard key, nor shards contain the tag

Closed

SERVER-19171 Shell does not always use extended JSON Shell Syntax

Closed

SERVER-66584 sh.updateZoneKeyRange() does not support $minKey or $maxKey

Closed

Assignee:: Kaloian Manassiev
Reporter:: Kaloian Manassiev
Participants:: Andy Schwerin, David Storch, Githook User, Kaloian Manassiev
Votes:: 0 Vote for this issue
Watchers:: 5 Start watching this issue

Created:: Apr 24 2018 05:40:32 PM UTC
Updated:: Oct 29 2023 10:32:26 PM UTC
Resolved:: Apr 30 2018 10:06:27 PM UTC
Confidence Status Last Update:: 25/Apr/18 2:22 PM

Details

Description

Attachments

Issue Links

Activity

People

Dates