[
https://issues.apache.org/jira/browse/PHOENIX-2575?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15178108#comment-15178108
]
ramkrishna.s.vasudevan commented on PHOENIX-2575:
-------------------------------------------------
Oops !!
bq.Was there any discussion around this to see if an alternative approach could
be made? This puts Phoenix in a crappy position.
The intention to do this in HBase was just to avoid one more HDFS call.
So in existing Phoenix LocalIndex code this call itself was not done?
Now calling super.getLastKey() - does not impact the local index behaviour?
Because previouly u did not want that to be called at all but now you r using
that result.
> 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)