[jira] [Updated] (PHOENIX-5094) Index can transition from INACTIVE to ACTIVE via Phoenix Client

2019-01-27 Thread Kiran Kumar Maturi (JIRA) 


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

Kiran Kumar Maturi updated PHOENIX-5094:

Attachment: PHOENIX-5094-4.14-HBase-1.3.02.patch

> Index can transition from INACTIVE to ACTIVE via Phoenix Client
> ---
>
> Key: PHOENIX-5094
> URL: https://issues.apache.org/jira/browse/PHOENIX-5094
> Project: Phoenix
>  Issue Type: Bug
>Affects Versions: 5.0.0, 4.14.1
>Reporter: Monani Mihir
>Assignee: Kiran Kumar Maturi
>Priority: Major
> Attachments: PHOENIX-5094-4.14-HBase-1.3.01.patch, 
> PHOENIX-5094-4.14-HBase-1.3.02.patch
>
>
> Suppose Index is in INACTIVE state and Client load is running continuously. 
> With INACTIVE State, client will keep maintaining index.
> Before Rebuilder could run and bring index back in sync with data table, If 
> some mutation for Index fails from client side, then client will transition 
> Index state (From INACTIVE--> PENDING_DISABLE).
> If client succeeds in writing mutation in subsequent retries, it will 
> transition Index state again ( From PENDING_DISABLE --> ACTIVE) .
> Above scenario will leave some part of Index out of sync with data table.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Created] (PHOENIX-5113) Reason through the correct plans for salted tables and local indexes

2019-01-27 Thread Lars Hofhansl (JIRA) 
Lars Hofhansl created PHOENIX-5113:
--

 Summary: Reason through the correct plans for salted tables and 
local indexes
 Key: PHOENIX-5113
 URL: https://issues.apache.org/jira/browse/PHOENIX-5113
 Project: Phoenix
  Issue Type: Task
Reporter: Lars Hofhansl


In PHOENIX-5109 I encountered various test failures in part due to salted 
tables.

Often it is not clear what the best strategy is for retained the current 
behavior in PHOENIX-5109.
This Jira is to reason through the issues and assure that Phoenix always picks 
the right plans (heuristically).



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

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

2019-01-27 Thread Lars Hofhansl (JIRA) 
Lars Hofhansl created PHOENIX-5112:
--

 Summary: 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


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)