[
https://issues.apache.org/jira/browse/PHOENIX-5793?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17082922#comment-17082922
]
Hadoop QA commented on PHOENIX-5793:
------------------------------------
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12999848/PHOENIX-5793-v5.patch
against master branch at commit ed0ca183fe6e54aa83ad826e4cf3e77267a0b306.
ATTACHMENT ID: 12999848
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:green}+1 tests included{color}. The patch appears to include 1 new
or modified tests.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:red}-1 release audit{color}. The applied patch generated 1 release
audit warnings (more than the master's current 0 warnings).
{color:green}+1 lineLengths{color}. The patch does not introduce lines
longer than 100
{color:red}-1 core tests{color}. The patch failed these unit tests:
Test results:
https://builds.apache.org/job/PreCommit-PHOENIX-Build/3747//testReport/
Release audit warnings:
https://builds.apache.org/job/PreCommit-PHOENIX-Build/3747//artifact/patchprocess/patchReleaseAuditWarnings.txt
Console output:
https://builds.apache.org/job/PreCommit-PHOENIX-Build/3747//console
This message is automatically generated.
> 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
>
> Attachments: PHOENIX-5793-v2.patch, PHOENIX-5793-v3.patch,
> PHOENIX-5793-v4.patch, PHOENIX-5793-v5.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)
