[SERVER-3102] invalidate querypattern when index becomes multikey Created: 16/May/11  Updated: 12/Jul/16  Resolved: 30/May/12

Status: Closed
Project: Core Server
Component/s: Querying
Affects Version/s: None
Fix Version/s: 2.1.2

Type: Improvement Priority: Major - P3
Reporter: Aaron Staple Assignee: Unassigned
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
depends on SERVER-958 Range queries on arrays behave differ... Closed
Related
is related to SERVER-958 Range queries on arrays behave differ... Closed
Participants:

 Description   

Single and multi key indexes have different index bounds. We may want to invalidate stored query patterns when the key nature of an index changes.



 Comments   
Comment by Aaron Staple [ 30/May/12 ]

This has already been implemented:

Author:

{u'login': u'astaple', u'name': u'Aaron', u'email': u'aaron@10gen.com'}

Message: SERVER-5301 Clear query plan cache when an index becomes multikey.
Branch: master
https://github.com/mongodb/mongo/commit/870e5cf7e25951c6dc8ed75e2d7343db4f0bfd8c

Comment by auto [ 26/Sep/11 ]

Author:

{u'login': u'agirbal', u'name': u'agirbal', u'email': u'antoine@10gen.com'}

Message: SERVER-3102: clear JS contexts in case of OOM
Branch: master
https://github.com/mongodb/mongo/commit/7fcb73791cbdc8b0bb87fa1b28461b2ac168ef2d

Generated at Thu Feb 08 03:02:05 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.