You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@phoenix.apache.org by "Kadir OZDEMIR (Jira)" <ji...@apache.org> on 2022/03/07 20:33:00 UTC

[jira] [Comment Edited] (PHOENIX-6501) Use batching when joining data table rows with uncovered index rows

    [ https://issues.apache.org/jira/browse/PHOENIX-6501?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17502543#comment-17502543 ] 

Kadir OZDEMIR edited comment on PHOENIX-6501 at 3/7/22, 8:32 PM:
-----------------------------------------------------------------

[~larsh], Thank you for checking it. Would you please post the steps to run the test? I want to run it and see if I can find the root cause. 


was (Author: kozdemir):
[~larsh], Thank you for checking it. Would please post the steps to run the test? I want to run it and see if I can find the root cause. 

> Use batching when joining data table rows with uncovered 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)