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

Hudson commented on PHOENIX-1139:
---------------------------------

FAILURE: Integrated in Phoenix | 4.0 | Hadoop2 #90 (See 
[https://builds.apache.org/job/Phoenix-4.0-hadoop2/90/])
PHOENIX-1139 Failed to disable local index when index update fails(Rajeshbabu) 
(rajeshbabu: rev 8325029cd55e689983a24dcdddcdc9842c637655)
* 
phoenix-core/src/it/java/org/apache/phoenix/end2end/index/MutableIndexFailureIT.java
* phoenix-core/src/main/java/org/apache/phoenix/schema/MetaDataClient.java
* 
phoenix-core/src/main/java/org/apache/phoenix/index/PhoenixIndexFailurePolicy.java
* 
phoenix-core/src/main/java/org/apache/phoenix/hbase/index/balancer/IndexLoadBalancer.java


> Failed to disable local index when index update fails
> -----------------------------------------------------
>
>                 Key: PHOENIX-1139
>                 URL: https://issues.apache.org/jira/browse/PHOENIX-1139
>             Project: Phoenix
>          Issue Type: Bug
>    Affects Versions: 5.0.0, 4.1
>            Reporter: Jeffrey Zhong
>            Assignee: rajeshbabu
>             Fix For: 5.0.0, 4.2
>
>         Attachments: PHOENIX-1139.patch
>
>
> When PhoenixIndexFailurePolicy is triggered when index update failed, we got 
> following error:
> {noformat}
> 2014-07-29 18:24:53,552 WARN  [defaultRpcServer.handler=0,queue=0,port=61926] 
> org.apache.phoenix.index.PhoenixIndexFailurePolicy(136): Attempt to disable 
> index _LOCAL_IDX_T failed with code = TABLE_NOT_FOUND. Will use default 
> failure policy instead.
> {noformat}
> The reason is that in PhoenixIndexFailurePolicy code, we construct index 
> table name from underlying hbase index table name. While local index table 
> can't be derived because underlying local index table name is always like 
> "_LOCAL_IDX_<DATA TABLE NAME>".



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to