You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@phoenix.apache.org by "Chen Feng (Jira)" <ji...@apache.org> on 2020/04/01 03:07:00 UTC
[jira] [Updated] (PHOENIX-5793) Support parallel init and fast null
return for SortMergeJoinPlan.
[ https://issues.apache.org/jira/browse/PHOENIX-5793?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Chen Feng updated PHOENIX-5793:
-------------------------------
Attachment: (was: PHOENIX-5793-v5.patch)
> Support parallel init and fast null return for SortMergeJoinPlan.
> -----------------------------------------------------------------
>
> Key: PHOENIX-5793
> URL: https://issues.apache.org/jira/browse/PHOENIX-5793
> Project: Phoenix
> Issue Type: Improvement
> Reporter: Chen Feng
> Assignee: Chen Feng
> Priority: Minor
> Attachments: PHOENIX-5793-v2.patch, PHOENIX-5793-v3.patch, PHOENIX-5793-v4.patch
>
>
> For a join sql like A join B. The implementation of SortMergeJoinPlan currently inits the two iterators A and B one by one.
> By initializing A and B in parallel, we can improve performance in two aspects.
> 1) By overlapping the time in initializing.
> 2) If one child query is null, the other child query can be canceled since the final result must be null.
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)