[PHOENIX-4616] Move join query optimization out from QueryCompiler into QueryOptimizer

• Type: Improvement
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 4.14.0, 5.0.0
• Assignee: Wei Xue
• Reporter: Wei Xue
• Created: 16/Feb/18 18:45
• Updated: 26/Jul/18 01:15
• Resolved: 04/Apr/18 19:22

Description

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

Issue Links

• is depended upon by: PHOENIX-4617 Make sure QueryPlan.getSourceRefs() get all data table refs for join queries and sub-queries