phoenix-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hudson (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (PHOENIX-5112) Simplify QueryPlan selection in Phoenix.
Date Sat, 25 May 2019 01:55:00 GMT

    [ https://issues.apache.org/jira/browse/PHOENIX-5112?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16848006#comment-16848006
] 

Hudson commented on PHOENIX-5112:
---------------------------------

FAILURE: Integrated in Jenkins build Phoenix-4.x-HBase-1.5 #6 (See [https://builds.apache.org/job/Phoenix-4.x-HBase-1.5/6/])
PHOENIX-5112 Simplify QueryPlan selection in Phoenix. (larsh: rev 20b3b679024e13b34fe17ab556e03e02cc660899)
* (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
>            Priority: Major
>         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)

Mime
View raw message