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

James Taylor edited comment on PHOENIX-2575 at 3/3/16 4:02 PM:
---------------------------------------------------------------

For the patch, why not just remove the override of getLastKey instead of 
calling super.getLastKey()? Please commit to 4.x and master branches. I 
supposed we'll need a new RC, but I'd really like to understand the big picture 
here and what our time lines are.

Does the patch fix local indexing or just prevent the test from hanging? Is 
local indexing broken when the latest version of HBase is used? What's the 
timeframe for finishing the local index redo work and does this address this 
particular issues?




was (Author: jamestaylor):
+1 on the patch too. Please commit to 4.x and master branches. I supposed we'll 
need a new RC, but I'd really like to understand the big picture here and what 
our time lines are.

Does the patch fix local indexing or just prevent the test from hanging? Is 
local indexing broken when the latest version of HBase is used? What's the 
timeframe for finishing the local index redo work and does this address this 
particular issues?



> Prevent LocalIndexIT from hanging indefinitely
> ----------------------------------------------
>
>                 Key: PHOENIX-2575
>                 URL: https://issues.apache.org/jira/browse/PHOENIX-2575
>             Project: Phoenix
>          Issue Type: Bug
>            Reporter: Samarth Jain
>            Assignee: Rajeshbabu Chintaguntla
>             Fix For: 4.8.0
>
>         Attachments: PHOENIX-2575.patch, PHOENIX-2575.patch
>
>
> On one of the test runs on 4.x-HBase-1.0, I see that the LocalIndexIT class 
> didn't complete. Run - 
> https://builds.apache.org/job/Phoenix-4.x-HBase-1.0/300/console. This is an 
> attempt to prevent the indefinite hang by adding a timeout to count down 
> latches.



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

Reply via email to