[
https://issues.apache.org/jira/browse/PHOENIX-752?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gabriel Reid resolved PHOENIX-752.
----------------------------------
Resolution: Fixed
Bulk resolve of closed issues imported from GitHub. This status was reached by
first re-opening all closed imported issues and then resolving them in bulk.
> Fix issue #502 Use QueryOptimizer.optimize to choose single table query plan
> ----------------------------------------------------------------------------
>
> Key: PHOENIX-752
> URL: https://issues.apache.org/jira/browse/PHOENIX-752
> Project: Phoenix
> Issue Type: Task
> Reporter: Maryann Xue
>
> Given fact that the compilation of both outer tables and inner tables in a
> join query cannot be strictly isolated and the input and output of compiling
> an outer/inner table depends on and is depended on by other tables'
> compilation input/output, calling QueryOptimizer.optimize within the process
> of join query compilation would require defining a trickier but
> incomprehensible interface for QueryCompiler.compile() (which in turn is
> called by Optimizer.optimize()).
> So instead, we do optimize() right before the real compilation process: for
> each join table in the query, we compose an independent query to get the
> optimized plan and the index table used by this plan. We then re-write the
> original join query by replacing the column references and the table
> references with the corresponding index tables and columns. And finally we
> will start to compile this new join-query statement.
> Changes:
> 1. Add JoinCompiler.optimize(), which takes in the original join statement
> and returns an optimized join statement.
> 2. Re-use the IndexStatementRewriter class for re-writing multiple-table
> queries.
> 3. Unit tests: add HashJoinWithIndexTest and testJoinPlanWithIndex().
--
This message was sent by Atlassian JIRA
(v6.2#6252)
