[
https://issues.apache.org/jira/browse/ASTERIXDB-2374?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16457068#comment-16457068
]
ASF subversion and git services commented on ASTERIXDB-2374:
------------------------------------------------------------
Commit 1d8de29a34941bd255e5ba3bf7b47d57e93d3a24 in asterixdb's branch
refs/heads/master from [~wangsaeu]
[ https://git-wip-us.apache.org/repos/asf?p=asterixdb.git;h=1d8de29 ]
[ASTERIXDB-2374][RT] Index-only plan on B+Tree disk components
- user model changes: no
- storage format changes: no
- interface changes: no
Details: Let the index-only plan properly work on the disk components of B+Tree.
Currently, only the records from in-memory components has been applied because
searchCallback.proceed() is only called for those.
Change-Id: I655eacc5517352a382d1b61f7b630f0f307b7c7b
Reviewed-on: https://asterix-gerrit.ics.uci.edu/2623
Tested-by: Jenkins <[email protected]>
Contrib: Jenkins <[email protected]>
Integration-Tests: Jenkins <[email protected]>
Reviewed-by: Dmitry Lychagin <[email protected]>
> Index-only plan does not work as expected.
> ------------------------------------------
>
> Key: ASTERIXDB-2374
> URL: https://issues.apache.org/jira/browse/ASTERIXDB-2374
> Project: Apache AsterixDB
> Issue Type: Bug
> Reporter: Taewoo Kim
> Assignee: Taewoo Kim
> Priority: Critical
>
> Currently, the index-only plan is generated, but none of the 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.
>
> (EDIT) The cause is that if we fetch a tuple from disk, the result of
> searchCallback.proceed() always needs to be set to true. And it isn't now.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
