[
https://issues.apache.org/jira/browse/PHOENIX-3050?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16398598#comment-16398598
]
Hudson commented on PHOENIX-3050:
---------------------------------
FAILURE: Integrated in Jenkins build Phoenix-4.x-HBase-0.98 #1833 (See
[https://builds.apache.org/job/Phoenix-4.x-HBase-0.98/1833/])
PHOENIX-3050 Handle DESC columns in child/parent join optimization (maryannxue:
rev 977699afe0d66f1434b8bc1c5a751767e563d6ce)
* (edit)
phoenix-core/src/main/java/org/apache/phoenix/compile/QueryCompiler.java
* (edit)
phoenix-core/src/it/java/org/apache/phoenix/end2end/join/HashJoinMoreIT.java
* (edit)
phoenix-core/src/main/java/org/apache/phoenix/compile/WhereOptimizer.java
* (edit) phoenix-core/src/main/java/org/apache/phoenix/compile/JoinCompiler.java
> 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
> Fix For: 4.14.0, 5.0.0
>
> 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
(v7.6.3#76005)
