[
https://issues.apache.org/jira/browse/ASTERIXDB-920?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15237947#comment-15237947
]
Taewoo Kim commented on ASTERIXDB-920:
--------------------------------------
Also, for the future references, I would like to keep the information regarding
the index-only plan and composite keys.
Suppose we have two int fields A and B and a composite index on (A,B).
1) If a query predicate is "A > 10": picks the index. Qualified as an
index-only plan.
2) If a query predicate is "B > 5": does not pick the index. Index-only plan
check will not be conducted.
3) If a query predicate is "A > 10 and B > 5": picks the index. Qualified as an
index-only plan. An additional SELECT operator will be added to the right path
(instantTryLock success path) of Index-only plan to filter out false positives
that satisfy "A > 10" and not "B > 5".
> Wrong results for a primary index with composite keys
> -----------------------------------------------------
>
> Key: ASTERIXDB-920
> URL: https://issues.apache.org/jira/browse/ASTERIXDB-920
> Project: Apache AsterixDB
> Issue Type: Bug
> Components: AsterixDB, Storage
> Reporter: asterixdb-importer
> Assignee: Ildar Absalyamov
> Attachments: fbm.adm
>
>
> Wrong results for a primary index with composite keys
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
