[jira] [Updated] (PHOENIX-5112) Simplify QueryPlan selection in Phoenix

2020-05-05 Thread Chinmay Kulkarni (Jira)


 [ 
https://issues.apache.org/jira/browse/PHOENIX-5112?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Chinmay Kulkarni updated PHOENIX-5112:
--
Summary: Simplify QueryPlan selection in Phoenix  (was: Simplify QueryPlan 
selection in Phoenix.)

> 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
(v8.3.4#803005)


[jira] [Updated] (PHOENIX-5112) Simplify QueryPlan selection in Phoenix.

2019-05-24 Thread Lars Hofhansl (JIRA)


 [ 
https://issues.apache.org/jira/browse/PHOENIX-5112?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Lars Hofhansl updated PHOENIX-5112:
---
Affects Version/s: 5.1.0
   4.15.0

> 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)


[jira] [Updated] (PHOENIX-5112) Simplify QueryPlan selection in Phoenix.

2019-05-18 Thread Lars Hofhansl (JIRA)


 [ 
https://issues.apache.org/jira/browse/PHOENIX-5112?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Lars Hofhansl updated PHOENIX-5112:
---
Attachment: 5112-master.txt

> 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)


[jira] [Updated] (PHOENIX-5112) Simplify QueryPlan selection in Phoenix.

2019-05-18 Thread Lars Hofhansl (JIRA)


 [ 
https://issues.apache.org/jira/browse/PHOENIX-5112?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Lars Hofhansl updated PHOENIX-5112:
---
Attachment: (was: 5112-master.txt)

> 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
>
>
> 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)


[jira] [Updated] (PHOENIX-5112) Simplify QueryPlan selection in Phoenix.

2019-05-18 Thread Lars Hofhansl (JIRA)


 [ 
https://issues.apache.org/jira/browse/PHOENIX-5112?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Lars Hofhansl updated PHOENIX-5112:
---
Attachment: (was: 5112-master.txt)

> 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
>
>
> 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)


[jira] [Updated] (PHOENIX-5112) Simplify QueryPlan selection in Phoenix.

2019-01-31 Thread Lars Hofhansl (JIRA)


 [ 
https://issues.apache.org/jira/browse/PHOENIX-5112?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Lars Hofhansl updated PHOENIX-5112:
---
Attachment: 5112-master.txt

> 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, 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)


[jira] [Updated] (PHOENIX-5112) Simplify QueryPlan selection in Phoenix.

2019-01-31 Thread Lars Hofhansl (JIRA)


 [ 
https://issues.apache.org/jira/browse/PHOENIX-5112?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Lars Hofhansl updated PHOENIX-5112:
---
Attachment: 5112-master.txt

> 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)


[jira] [Updated] (PHOENIX-5112) Simplify QueryPlan selection in Phoenix.

2019-01-29 Thread Lars Hofhansl (JIRA)


 [ 
https://issues.apache.org/jira/browse/PHOENIX-5112?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Lars Hofhansl updated PHOENIX-5112:
---
Attachment: 5112-master.txt

> 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
>
>
> 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)