[
https://issues.apache.org/jira/browse/PHOENIX-5793?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17141208#comment-17141208
]
Hudson commented on PHOENIX-5793:
---------------------------------
ABORTED: Integrated in Jenkins build PreCommit-PHOENIX-Build #3982 (See
[https://builds.apache.org/job/PreCommit-PHOENIX-Build/3982/])
PHOENIX-5793 Support parallel init and fast null return for (chenglei: rev
d48e3624d71427707759928830b42e1bd42cea90)
* (edit)
phoenix-core/src/test/java/org/apache/phoenix/execute/SortMergeJoinTest.java
* (edit)
phoenix-core/src/it/java/org/apache/phoenix/end2end/SortMergeJoinMoreIT.java
* (edit)
phoenix-core/src/main/java/org/apache/phoenix/execute/SortMergeJoinPlan.java
> 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
> Affects Versions: 5.0.0
> Reporter: Chen Feng
> Assignee: Chen Feng
> Priority: Minor
> Fix For: 5.1.0, 4.16.0
>
> Attachments: PHOENIX-5793-v2.patch, PHOENIX-5793-v3.patch,
> PHOENIX-5793-v4.patch, PHOENIX-5793-v5.patch, PHOENIX-5793_v1-4.x.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)
