[SERVER-37548] MongoInterfaceStandalone::isSharded should not use AutoGetCollectionForReadCommand Created: 10/Oct/18 Updated: 29/Oct/23 Resolved: 01/Nov/18 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Aggregation Framework, Sharding |
| Affects Version/s: | None |
| Fix Version/s: | 4.1.5 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Charlie Swanson | Assignee: | Charlie Swanson |
| 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: | Query 2018-10-22, Query 2018-11-05 |
| Participants: |
| Description |
|
The AutoGetCollectionForReadCommand helper will automatically check that the shard version attached to the operation context matches the version of the namespace in question - this only makes sense when there is a single involved namespace. We've actually seen this bug before, and made this change as part of preliminary work for sharded $lookup. Unfortunately, this change was reverted. This part of the change should be revived. |
| Comments |
| Comment by Githook User [ 01/Nov/18 ] |
|
Author: {'name': 'Charlie Swanson', 'email': 'charlie.swanson@mongodb.com', 'username': 'cswanson310'}Message: |