[
https://issues.apache.org/jira/browse/PHOENIX-4616?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16431373#comment-16431373
]
Hudson commented on PHOENIX-4616:
---------------------------------
FAILURE: Integrated in Jenkins build PreCommit-PHOENIX-Build #1824 (See
[https://builds.apache.org/job/PreCommit-PHOENIX-Build/1824/])
PHOENIX-4616 Move join query optimization out from QueryCompiler into
(maryannxue: rev 49fca494bf9e13918db558e8276676e3dfda9d74)
* (edit)
phoenix-core/src/main/java/org/apache/phoenix/optimize/QueryOptimizer.java
PHOENIX-4616 Move join query optimization out from QueryCompiler into
(maryannxue: rev 0b1b219ef0e803d7ff254408c24b4bb67a5d88f9)
* (edit)
phoenix-core/src/main/java/org/apache/phoenix/optimize/QueryOptimizer.java
> Move join query optimization out from QueryCompiler into QueryOptimizer
> -----------------------------------------------------------------------
>
> Key: PHOENIX-4616
> URL: https://issues.apache.org/jira/browse/PHOENIX-4616
> Project: Phoenix
> Issue Type: Improvement
> Reporter: Maryann Xue
> Assignee: Maryann Xue
> Priority: Major
> Fix For: 4.14.0, 5.0.0
>
> Attachments: PHOENIX-4616.patch
>
>
> Currently we do optimization for join queries inside QueryCompiler, which
> makes the APIs and code logic confusing, so we need to move join optimization
> logic into QueryOptimizer.
> Similarly, but probably with a different approach, we need to optimize UNION
> ALL queries and derived table sub-queries in QueryOptimizer.optimize().
> Please also refer to this comment:
> https://issues.apache.org/jira/browse/PHOENIX-4585?focusedCommentId=16367616&page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#comment-16367616
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
