[
https://issues.apache.org/jira/browse/PHOENIX-3050?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16279258#comment-16279258
]
Hadoop QA commented on PHOENIX-3050:
------------------------------------
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12894919/PHOENIX-3050.patch
against master branch at commit d77c237b560900671c3a9c58f6f2398342655e8a.
ATTACHMENT ID: 12894919
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:red}-1 tests included{color}. The patch doesn't appear to include
any new or modified tests.
Please justify why no new tests are needed for this
patch.
Also please list what manual steps were performed to
verify this patch.
{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:red}-1 lineLengths{color}. The patch introduces the following lines
longer than 100:
+ public Pair<List<Expression>, List<Expression>>
compileJoinConditions(StatementContext lhsCtx, StatementContext rhsCtx,
Strategy strategy) throws SQLException {
+ SortOrder toSortOrder = strategy == Strategy.SORT_MERGE ?
SortOrder.ASC : (strategy == Strategy.HASH_BUILD_LEFT ? right.getSortOrder() :
left.getSortOrder());
+ right = CoerceExpression.create(right, toType,
toSortOrder, right.getMaxLength());
+ Pair<List<Expression>, List<Expression>> joinConditions =
joinSpec.compileJoinConditions(context, subContexts[i],
JoinCompiler.Strategy.HASH_BUILD_RIGHT);
+ Pair<List<Expression>, List<Expression>> joinConditions =
lastJoinSpec.compileJoinConditions(lhsCtx, context,
JoinCompiler.Strategy.HASH_BUILD_LEFT);
+ Pair<List<Expression>, List<Expression>> joinConditions =
lastJoinSpec.compileJoinConditions(type == JoinType.Right ? rhsCtx : lhsCtx,
type == JoinType.Right ? lhsCtx : rhsCtx, JoinCompiler.Strategy.SORT_MERGE);
{color:green}+1 core tests{color}. The patch passed unit tests in .
Test results:
https://builds.apache.org/job/PreCommit-PHOENIX-Build/1652//testReport/
Release audit warnings:
https://builds.apache.org/job/PreCommit-PHOENIX-Build/1652//artifact/patchprocess/patchReleaseAuditWarnings.txt
Console output:
https://builds.apache.org/job/PreCommit-PHOENIX-Build/1652//console
This message is automatically generated.
> Handle DESC columns in child/parent join optimization
> -----------------------------------------------------
>
> Key: PHOENIX-3050
> URL: https://issues.apache.org/jira/browse/PHOENIX-3050
> Project: Phoenix
> Issue Type: Bug
> Affects Versions: 4.8.0
> Reporter: Maryann Xue
> Assignee: Maryann Xue
> Priority: Minor
> Attachments: PHOENIX-3050.patch
>
>
> We found that child/parent join optimization would not work with DESC pk
> columns. So as a quick fix for PHOENIX-3029, we simply avoid DESC columns
> when optimizing, which would have no impact on the overall approach and no
> impact on ASC columns.
>
> But eventually we need to make the optimization work with DESC columns too.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
