[
https://issues.apache.org/jira/browse/PHOENIX-6501?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17502661#comment-17502661
]
Lars Hofhansl edited comment on PHOENIX-6501 at 3/8/22, 1:32 AM:
-----------------------------------------------------------------
Sorry - doing too many things as the same time - the index was correct. I
accidentally use count\(*), which does not need to do the merge. So the query
in question is still "hanging".
was (Author: lhofhansl):
Sorry - doing too many things as the same time - the index was correct. I
accidentally use count(*), which does not need to do the merge. So the query in
question is still "hanging".
> Use batching when joining data table rows with uncovered global index rows
> --------------------------------------------------------------------------
>
> Key: PHOENIX-6501
> URL: https://issues.apache.org/jira/browse/PHOENIX-6501
> Project: Phoenix
> Issue Type: Improvement
> Affects Versions: 5.1.2
> Reporter: Kadir Ozdemir
> Assignee: Kadir OZDEMIR
> Priority: Major
> Attachments: PHOENIX-6501.master.001.patch
>
>
> PHOENIX-6458 extends the existing uncovered local index support for global
> indexes. The current solution uses HBase get operations to join data table
> rows with uncovered index rows on the server side. Doing a separate RPC call
> for every data table row can be expensive. Instead, we can buffer lots of
> data row keys in memory, use a skip scan filter and even multiple threads to
> issue a separate scan for each data table region in parallel. This will
> reduce the cost of join and also improve the performance.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
