Mailing-List: contact issues-help@hbase.apache.org; run by ezmlm
Precedence: bulk
Date: Tue, 10 Feb 2015 12:36:11 +0000 (UTC)
From: "Andrey Stepachev (JIRA)" <jira@apache.org>
To: issues@hbase.apache.org
Message-ID: <JIRA.12773831.1423571572000.57.1423571771519@Atlassian.JIRA>
In-Reply-To: <JIRA.12773831.1423571572000@Atlassian.JIRA>
References: <JIRA.12773831.1423571572000@Atlassian.JIRA>
 <JIRA.12773831.1423571572787@arcas>
Subject: [jira] [Updated] (HBASE-13004) Make possible to explain why
 HTU.waitFor fails
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


     [ https://issues.apache.org/jira/browse/HBASE-13004?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Andrey Stepachev updated HBASE-13004:
-------------------------------------
    Attachment: HBASE-13004.patch

Added ExplainingPredicate to Waiter
Added explainTableAvailability to explain why table possibly was not available (act as example of usage of EP)

> 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)