hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ted Yu (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-13004) Make possible to explain why HBaseTestingUtility.waitFor fails
Date Tue, 10 Feb 2015 17:44:12 GMT

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

Ted Yu commented on HBASE-13004:
--------------------------------

Addendum integrated.

> Make possible to explain why HBaseTestingUtility.waitFor fails
> --------------------------------------------------------------
>
>                 Key: HBASE-13004
>                 URL: https://issues.apache.org/jira/browse/HBASE-13004
>             Project: HBase
>          Issue Type: Bug
>          Components: test
>    Affects Versions: 1.0.0, 2.0.0
>            Reporter: Andrey Stepachev
>            Assignee: Andrey Stepachev
>            Priority: Minor
>             Fix For: 2.0.0, 1.1.0
>
>         Attachments: HBASE-13004-branch-1.patch, HBASE-13004-branch-1.patch, HBASE-13004.patch,
HBASE-13004.patch, master-addendum.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}
> HBaseTestingUtility.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)

Mime
View raw message