-
Type:
Task
-
Resolution: Unresolved
-
Priority:
Major - P3
-
None
-
Affects Version/s: None
-
Component/s: None
-
None
-
Query Execution
-
None
-
None
-
None
-
None
-
None
-
None
-
None
The subtree for each thread is now "prepared" from within the main thread, so that we can reuse the CollectionAcquisition already obtained by it. This could be not optimal if the plan preparation is costly (e.g. when compiling several projection expressions) so we could use each thread to do their own preparation.
In any case verify if the current solution (running inside the main thread) doesn't expose to deadlock scenarios (e.g. prepare() tries to use the transaction associated to the producer's OperationContext and it's unable to obtain them while the mainOperationContext holds the same lock)