[
https://issues.apache.org/jira/browse/PHOENIX-6983?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17737302#comment-17737302
]
Lars Hofhansl edited comment on PHOENIX-6983 at 6/26/23 5:50 PM:
-----------------------------------------------------------------
isn't this the same as hinting not to use the index in question, or hinting a
full scan?
[~stoty]
was (Author: lhofhansl):
isn't this the same as hinting not to use the index in question, or hinting a
full scan?
> Add hint to disable server merges for uncovered index queries
> -------------------------------------------------------------
>
> Key: PHOENIX-6983
> URL: https://issues.apache.org/jira/browse/PHOENIX-6983
> Project: Phoenix
> Issue Type: Improvement
> Components: core
> Affects Versions: 5.2.0, 5.1.3
> Reporter: Istvan Toth
> Assignee: Istvan Toth
> Priority: Major
> Fix For: 5.2.0, 5.1.4
>
>
> In certain cases, the new server merge code is far less efficient than the
> old skip-scan-merge code path.
> Specifically, when a large number of rows is matched on the index table, then
> each of those rows has to be resolved from the data table, and the filtering
> must be done on the index RS.
> With the old code path, these filters were pushed to the data table, and
> processed in parallel, with much better performance.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
