Query planning logic depends substantially on whether or not the set of available indices is multikey, and on which indexed paths are multikey. If this information changes due to a concurrent update or insert creating a new array path, in progress queries may be using a plan that is now invalid. One way to fix this would be to kill all in-progress queries for a particular collection when making a change to that collection's multikeyness metadata.
- is duplicated by
-
SERVER-4975 covered index projection may be improperly applied after index becomes multikey during yield
-
- Closed
-
-
-
- Closed
-
- related to
-
SERVER-41058 Add concurrency workload targeted at multikey index writes
-
- Backlog
-