phoenix-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Maryann Xue (JIRA)" <>
Subject [jira] [Commented] (PHOENIX-4616) Move join query optimization out from QueryCompiler into QueryOptimizer
Date Thu, 08 Mar 2018 06:12:00 GMT


Maryann Xue commented on PHOENIX-4616:

Thank you very much for the review, [~jamestaylor]!
 # The change in the join tests was needed because I ran into a random failure in {{testJoinWithOffset()}}
which I suspect was due to unstable result order since the test case did not specify an ORDER
 # I thought it would be better to keep the optimization logic all in one place so it would
be easier to maintain and extend later on. One way is to use the QueryPlanVisitor here to
get rid of "instanceof" check while still keeping everything in QueryOptimizer. What do you

> Move join query optimization out from QueryCompiler into QueryOptimizer
> -----------------------------------------------------------------------
>                 Key: PHOENIX-4616
>                 URL:
>             Project: Phoenix
>          Issue Type: Improvement
>            Reporter: Maryann Xue
>            Assignee: Maryann Xue
>            Priority: Major
>         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:

This message was sent by Atlassian JIRA

View raw message