Details
-
Improvement
-
Resolution: Gone away
-
Major - P3
-
None
-
None
-
None
-
Query
Description
As far as I can tell, the distinction exists because there are certain commands which require an ExpressionContext but manage a unique_ptr to the resolved collator on their own. This is confusing especially to new engineers, since its not obvious which one is valid and when.
As part of the review for SERVER-43844, a couple of ideas involved holding by intrusive_ptr or always cloning the collator even if its "owned" elsewhere.
Attachments
Issue Links
- is related to
-
SERVER-45406 Provide ExpressionContext in PlanStage layer
-
- Closed
-