Details
-
Bug
-
Resolution: Fixed
-
Major
-
6.5.1, Cheshire-Cat
-
7.0.0-1336
-
Untriaged
-
Unknown
Description
Very similar scenario to MB-31203
Create default bucket
Insert docs like the following:
{a:100, d:200}create 2 indexes:
create index idx1 on default(a);
create index idx2 on default(a,d);
run queries:
explain select * from default where a > 0;
Sometimes idx1 is picked up, sometimes idx2 is picked up, however we should expect it to always pickup idx1 right? Will check if this problem also exists in 6.5.1
Attachments
Issue Links
- relates to
-
MB-31203 skip range scan index selection choosing longest matching index
- Closed
For Gerrit Dashboard: MB-38018 | ||||||
---|---|---|---|---|---|---|
# | Subject | Branch | Project | Status | CR | V |
122730,6 | MB-38018. re-work index selection | master | query | Status: ABANDONED | +1 | 0 |
123324,1 | MB-31203, MB-38018. Index selection is based on continuous keys only | master | query | Status: ABANDONED | 0 | 0 |