You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@asterixdb.apache.org by "Taewoo Kim (JIRA)" <ji...@apache.org> on 2017/07/02 19:48:02 UTC
[jira] [Created] (ASTERIXDB-1971) Index-only plan on Non-enforced
index issue
Taewoo Kim created ASTERIXDB-1971:
-------------------------------------
Summary: Index-only plan on Non-enforced index issue
Key: ASTERIXDB-1971
URL: https://issues.apache.org/jira/browse/ASTERIXDB-1971
Project: Apache AsterixDB
Issue Type: Improvement
Reporter: Taewoo Kim
Index-only plan only conducts a search on a secondary index and skips the primary-index search and the final verification (SELECT). Therefore, it is crucial for the index-only plan that a secondary-index search generates the final (trustworthy) result for the given search.
By nature, a non-enforced index casts a numeric value when if the type between the given value and the type of the index are different. Therefore, a search on a non-enforced index may generate a super-set of the final result.
So, we need to find a resolution - 1) non index-only plan on the non-enforced index at all, 2) a partial application of index-only plan
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)