Details
-
Bug
-
Resolution: Fixed
-
Major
-
4.6.2, 5.0.0
-
4.6.2-3889
-
Untriaged
-
Yes
Description
Found this issue while verifying:
https://issues.couchbase.com/browse/MB-22757
Index created:
CREATE INDEX idx ON default( DISTINCT ARRAY v FOR v in join_yr END)
Query issued:
EXPLAIN select meta().id from default where any v in join_yr satisfies v = 2016 END and (ANY v IN default.join_yr SATISFIES v = 2014 END)
This query uses the right index and is a covered query as expected in MB-22757.
But it gives different results than the same query using primary index.
select meta().id from default where any v in join_yr satisfies v = 2016 END and (ANY v IN default.join_yr SATISFIES v = 2014 END) order by meta().id limit 2
gives different results than
select meta().id from default use index (`#primary`) where any v in join_yr satisfies v = 2016 END and (ANY v IN default.join_yr SATISFIES v = 2014 END) order by meta().id limit 2
Attachments
Issue Links
For Gerrit Dashboard: MB-23966 | ||||||
---|---|---|---|---|---|---|
# | Subject | Branch | Project | Status | CR | V |
76931,2 | MB-23966. IntersectScan on same index is used don't use filters from predicate for covering | watson | query | Status: MERGED | +2 | +1 |
76932,2 | MB-23966. IntersectScan on same index is used don't use filters from predicate for covering | master | query | Status: MERGED | +2 | +1 |
76987,4 | CBQE-4095:Add test case for MB-23966 Test for MB-23966 Results are different in query using covered Intersectscan of array index and primary scan | watson | testrunner | Status: MERGED | +2 | +1 |
76989,2 | CBQE-4095:Add test case for MB-23966 Test for MB-23966 Results are different in query using covered Intersectscan of array index and primary scan | master | testrunner | Status: MERGED | +2 | +1 |