[SERVER-65062] Check the shard version for views when AutoGetCollection is instantiated Created: 30/Mar/22 Updated: 29/Oct/23 Resolved: 01/Apr/22 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Sharding |
| Affects Version/s: | None |
| Fix Version/s: | 6.0.0-rc0 |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Antonio Fuschetto | Assignee: | Antonio Fuschetto |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | PM-2144-Milestone-0 | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Backwards Compatibility: | Fully Compatible |
| Sprint: | Sharding EMEA 2022-04-04 |
| Participants: |
| Description |
|
As a prerequisite to push the CollectionShardingState to the Storage Catalog, when the collection locks are acquired (AutoGetCollection class), the shard version attached to the operation context must be consistent with the information stored in the local metadata. The goal of this task is to check that the shard version attached to the request is unsharded when the passed namespace corresponds to a view in the local catalog. |
| Comments |
| Comment by Githook User [ 01/Apr/22 ] |
|
Author: {'name': 'Antonio Fuschetto', 'email': 'antonio.fuschetto@mongodb.com', 'username': 'afuschetto'}Message: |