[
https://issues.apache.org/jira/browse/PHOENIX-5112?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16843531#comment-16843531
]
Lars Hofhansl edited comment on PHOENIX-5112 at 5/19/19 9:04 PM:
-----------------------------------------------------------------
* IndexRebuildTaskIT does not fail for me (in 4.x-HBase-1.4) with the patch. It
does fail (with or without patch) in 4.x-HBase-1.5 and master).
* MutableIndexSplitForwardScanIT does not fail either (4.x-HBase-1.4) with the
patch... Wait it's disabled in 4.x
* HashJoinMoreIT fails with or without the patch (4.x-HBase-1.4)
* And UpgradeIT passes (again 4.x-HBase-1.4)
So I think this is good to go.
was (Author: lhofhansl):
* IndexRebuildTaskIT does not fail for me (in 4.x-HBase-1.4) with the patch. It
does fail (with or without patch) in 4.x-HBase-1.5 and master).
* MutableIndexSplitForwardScanIT does not fail either (4.x-HBase-1.4) with the
patch... Wait it's disabled in 4.x
* HashJoinMoreIT fails with or without the patch (4.x-HBase-1.4)
> 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)
