-
Type:
Task
-
Resolution: Unresolved
-
Priority:
Major - P3
-
None
-
Affects Version/s: None
-
Component/s: None
-
None
-
Catalog and Routing
-
1
-
🟦 Shard Catalog
-
None
-
None
-
None
-
None
-
None
-
None
SERVER-99711 discovered a potential problem with how we currently do yields and restores with collection acquisitions against two different databases. Today we don't have this case but in the future it could show up as a potential blocker if queries need access to two different databases.
As the change might be a bit tricky to implement we should add a tassert such that it detects this behaviour and makes the user contact us if they want to use it. Notably this is targeted more to Query engineers as they are the ones who would want to enable it for general query use.
- is related to
-
SERVER-99711 Investigate canonical ordering of locks during yield/restore
-
- Backlog
-