Loading...

XML

Word

Printable

JSON

Type: Bug
Resolution: Done
Priority: Major - P3
Fix Version/s: 2.6.0-rc0
Affects Version/s: None
Component/s: Index Maintenance, Querying
Labels:
None

Assigned Teams:

Query Execution
Operating System:
ALL
Confidence Status:
None
Work Order:
3
CAR Domain/s:
None

Aha! Reference:
None
Tracking Level:
None
Risk Status:
None
Exec Notes:
None
Goal Name(s):
None
Goal Link:
None

Our documentation on multikey behavior and bounds creation is incomplete. Also our bounds w/the new planner are probably not as tight as they could be.

is related to

SERVER-7959 Potentially unexpected scans with compound indexes when some fields are multikey

Closed

SERVER-12281 When choosing multikey index bounds, never choose a superset if a subset is available

Backlog

related to

SERVER-12475 Query on compound multi-key indexes lost performance between 2.4.6 and 2.5.5-pre-

Closed

Assignee:: David Storch
Reporter:: hari.khalsa@10gen.com
Participants:: David Storch, Githook User, hari.khalsa@10gen.com
Votes:: 0 Vote for this issue
Watchers:: 5 Start watching this issue

Created:: Jan 24 2014 05:40:40 PM UTC
Updated:: Feb 09 2025 09:21:04 PM UTC
Resolved:: Feb 12 2014 06:33:02 PM UTC
Confidence Status Last Update:: 10/Feb/14 9:48 PM

Details

Description

Attachments

Issue Links

Forms

Activity

People

Dates