[SERVER-8768] implement support for interleaving btree and non btree cursors in query optimizer cursor selection code Created: 27/Feb/13  Updated: 07/Mar/14  Resolved: 23/Sep/13

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

Type: Improvement Priority: Major - P3
Reporter: Aaron Staple Assignee: hari.khalsa@10gen.com
Resolution: Duplicate Votes: 1
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Duplicate
duplicates SERVER-3071 Index Intersection Closed
Related
is related to SERVER-4531 new process for selecting a geo index... Closed
Participants:

 Description   

The query optimizer implementation for speculatively evaluating cursors produced by multiple query plans currently only supports btree and unindexed cursors. Certain geo cursors are not supported, and as a result all non btree cursors are excluded from speculative evaluation. This means that non btree cursors are only used to resolve an unhinted query when no btree cursors are helpful candidates for the query, as described in SERVER-4531. A hint can still be used to force usage of a non btree index in such cases.

Instead it may be desirable for the query optimizer to support speculative evaluation of btree and non btree cursors simultaneously.


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