[
https://issues.apache.org/jira/browse/PHOENIX-5112?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16848081#comment-16848081
]
Hudson commented on PHOENIX-5112:
---------------------------------
ABORTED: Integrated in Jenkins build Phoenix-4.x-HBase-1.3 #407 (See
[https://builds.apache.org/job/Phoenix-4.x-HBase-1.3/407/])
PHOENIX-5112 Simplify QueryPlan selection in Phoenix. (larsh: rev
a425c7200b8cb9f17a1081284f688db48cedcfdf)
* (edit)
phoenix-core/src/main/java/org/apache/phoenix/optimize/QueryOptimizer.java
> Simplify QueryPlan selection in Phoenix.
> ----------------------------------------
>
> Key: PHOENIX-5112
> URL: https://issues.apache.org/jira/browse/PHOENIX-5112
> Project: Phoenix
> Issue Type: Improvement
> Affects Versions: 4.15.0, 5.1.0
> Reporter: Lars Hofhansl
> Assignee: Lars Hofhansl
> Priority: Major
> Fix For: 4.15.0, 5.1.0
>
> Attachments: 5112-master.txt, 5112-master.txt
>
>
> Brought to light in part in PHOENIX-5109, plan selection in Phoenix is too
> complicated with its logic spread over multiple areas. My recent changes let
> most index through the initial filters and next step is to put all the logic
> in {{QueryOptimizer.orderPlansBestToWorst}}.
> One exception is plans with global indexes for queries with uncovered
> queries, those should still be handled in {{addPlan}}.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
