-
Type: Task
-
Resolution: Fixed
-
Priority: Critical - P2
-
Affects Version/s: None
-
Labels:None
Changed the output of the shardingState command. Now, instead of the version portion of the command output looking like:
"versions": { "<database>.<collection>" : Timestamp(<...>), "<database>.<collection>" : Timestamp(<...>) }
it will instead look like:
"versions": { "<database>.<collection>": { "placementVersion": Timestamp(<...>), "timestamp": Timestamp(<...>) }, "<database>.<collection>": { "placementVersion": Timestamp(<...>), "timestamp": Timestamp(<...>) } }
Description of Linked Ticket
The shardingState command attaches the versions of each collection as part of the output of the command. However, we are only attaching the timestamp (major and minor version) and ignoring the epoch and timestamp (and soon, the index version as well). We should check if we can change the output of this user command, and either update the version to include the epoch, timestamp, and index version or change the name of the command to appendCollectionPlacement (since we are not appending a shard version currently)
- documents
-
SERVER-70790 shardingState command appends only the major and minor version of the ShardVersion
- Closed