[SERVER-83108] $listCatalog doesn't respect readConcern Created: 10/Nov/23 Updated: 10/Nov/23 Resolved: 10/Nov/23 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Jordi Olivares Provencio | Assignee: | Jordi Olivares Provencio |
| Resolution: | Works as Designed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||||||
| Operating System: | ALL | ||||||||||||||||
| Backport Requested: |
v7.1, v7.0
|
||||||||||||||||
| Sprint: | CAR Team 2023-11-13, CAR Team 2023-11-27 | ||||||||||||||||
| Participants: | |||||||||||||||||
| Description |
|
Say we rename a collection a collection and the rename has only been applied to a minority of nodes in a replica set. That is, the majority timestamp hasn't yet advanced. If a user were to perform $listCatalog targeting the old collection name with majority readConcern then the aggregation will fail since it is now checking against the latest version of the catalog instead of respecting the read concern. |
| Comments |
| Comment by Jordi Olivares Provencio [ 10/Nov/23 ] |
|
Mistakenly opened this up as it is correctly working |
| Comment by Gregory Noma [ 10/Nov/23 ] |
|
Is this specific to either the collection-level $listCatalog or the collectionless $listCatalog? Or does it affect both? |