phoenix-issues mailing list archives

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

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

James Taylor commented on PHOENIX-5112:
---------------------------------------

How about as a separate effort figuring out why the unit tests never pass?

> Simplify QueryPlan selection in Phoenix.
> ----------------------------------------
>
>                 Key: PHOENIX-5112
>                 URL: https://issues.apache.org/jira/browse/PHOENIX-5112
>             Project: Phoenix
>          Issue Type: Improvement
>            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