Taewoo Kim created ASTERIXDB-2374:
-------------------------------------
Summary: Index-only plan does work as expected.
Key: ASTERIXDB-2374
URL: https://issues.apache.org/jira/browse/ASTERIXDB-2374
Project: Apache AsterixDB
Issue Type: Bug
Reporter: Taewoo Kim
Currently, the index-only plan is generated, but none of search result goes to
the index-only-plan path. That is, every search result from a secondary index
search is fed into the primary index.
The cause is that after loading tuples from in-memory search cursor to a
priority queue, we set a boolean variable "includeMutableComponents" to false.
Thus, when LSMBTreeRangeSearchCursor conducts a search, it thinks that it is
fetching tuples from the disk and does not apply "searchCallback.proceed()".
The index-only plan relies on this result and it is always set to false.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
