[SERVER-34325] OperationShardingState should store namespace and db separately, in case a command is not on a full namespace Created: 04/Apr/18  Updated: 29/Oct/23  Resolved: 05/Apr/18

Status: Closed
Project: Core Server
Component/s: Sharding
Affects Version/s: 3.7.3
Fix Version/s: 3.7.4

Type: Bug Priority: Major - P3
Reporter: Esha Maharishi (Inactive) Assignee: Esha Maharishi (Inactive)
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Backwards Compatibility: Fully Compatible
Operating System: ALL
Sprint: Sharding 2018-04-09
Participants:

 Comments   
Comment by Esha Maharishi (Inactive) [ 05/Apr/18 ]

Note, this commit actually makes the OperationShardingState support storing client shardVersions and databaseVersions for multiple namespaces and databases, respectively (but we don't have a protocol to actually send or parse versions for multiple namespaces/databases yet).

Comment by Githook User [ 05/Apr/18 ]

Author:

{'email': 'esha.maharishi@mongodb.com', 'name': 'Esha Maharishi', 'username': 'EshaMaharishi'}

Message: SERVER-34325 OperationShardingState should store namespace and db separately, in case a command is not on a full namespace
Branch: master
https://github.com/mongodb/mongo/commit/9da53de7efe7230cc7b3e957e869f94693d7b802

Generated at Thu Feb 08 04:36:18 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.