-
Type: Task
-
Resolution: Fixed
-
Priority: Major - P3
-
Affects Version/s: None
-
Component/s: None
-
None
-
Fully Compatible
-
Sharding EMEA 2023-05-29, Sharding EMEA 2023-06-12, Sharding EMEA 2023-06-26, Sharding EMEA 2023-07-10
The command removeTagRange(nss, min, max, tagName) from util_sh.js removes the range independently of the given tag name; the tagName parameter is ignored. This command (removeTagRange) is an alias for removeRangeFromZone. On the other hand, removeRangeFromZone(nss, min, max) from the mongo shell removes the range from the tag without passing this as a parameter. It can be done this way because there is a 1:N relationship between tags - ranges. One range can only belong to one tag, thus there is no need to have the tag name to remove a range.
The goals of this ticket:
- Match the behaviour between the mongo command (util_sh.js) and the mongo shell command (shard.ts).
- Flag for downstream impact to update the docs, they are not aware that the tagName parameter that does not exist in the mongosh.
- related to
-
SERVER-37938 removeTagRange returns {ok: 1} even as it ignores matching range
- Closed