You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "Andrey Stepachev (JIRA)" <ji...@apache.org> on 2015/02/10 13:36:11 UTC
[jira] [Updated] (HBASE-13004) Make possible to explain why
HTU.waitFor fails
[ https://issues.apache.org/jira/browse/HBASE-13004?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Andrey Stepachev updated HBASE-13004:
-------------------------------------
Status: Patch Available (was: Open)
> Make possible to explain why HTU.waitFor fails
> ----------------------------------------------
>
> Key: HBASE-13004
> URL: https://issues.apache.org/jira/browse/HBASE-13004
> Project: HBase
> Issue Type: Bug
> Components: test
> Affects Versions: 2.0.0
> Reporter: Andrey Stepachev
> Assignee: Andrey Stepachev
> Priority: Minor
> Attachments: HBASE-13004.patch
>
>
> HBaseTestingUtility has good methods for waiting conditions, but with one drawback, when waitfor fails, there is no way to explain what happened (fail() called from internals and that is not very easy to intercept and explain state of failure).
> That would be great to have enhanced Predicate which can explain state after it failed to wait for.
> That can looks like
> {code}
> HUT.waitFor(10000, new ExplainingPredicate() {
> boolean evaluate() {
> ... some evaluation code
> }
> String explain() {
> ... generate brief explanation of what to be expected, but not happened
> }
> }
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)