Hadoop QA commented on ZOOKEEPER-358:

+1 overall.  Here are the results of testing the latest attachment 
  against trunk revision 779716.

    +1 @author.  The patch does not contain any @author tags.

    +1 tests included.  The patch appears to include 3 new or modified tests.

    +1 javadoc.  The javadoc tool did not generate any warning messages.

    +1 javac.  The applied patch does not increase the total number of javac 
compiler warnings.

    +1 findbugs.  The patch does not introduce any new Findbugs warnings.

    +1 release audit.  The applied patch does not increase the total number of 
release audit warnings.

    +1 core tests.  The patch passed core unit tests.

    +1 contrib tests.  The patch passed contrib unit tests.

Test results: 
Findbugs warnings: 
Console output: 

This message is automatically generated.

> Throw exception when ledger does not exist
> ------------------------------------------
>                 Key: ZOOKEEPER-358
>                 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-358
>             Project: Zookeeper
>          Issue Type: Improvement
>          Components: contrib-bookkeeper
>    Affects Versions: 3.1.1
>            Reporter: Luca Telloli
>            Assignee: Flavio Paiva Junqueira
>            Priority: Minor
>             Fix For: 3.2.0
>         Attachments: ZOOKEEPER-358.patch, ZOOKEEPER-358.patch
> Currently, openLedger() in the BookKeeper client returns null if the ledger 
> ID does not exist on ZK. Maybe it would be better to throw a specific 
> exception so it can be handled by the client side. 

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

Reply via email to