You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@bookkeeper.apache.org by "Ivan Kelly (JIRA)" <ji...@apache.org> on 2012/07/04 10:51:35 UTC

[jira] [Updated] (BOOKKEEPER-317) Exceptions for replication

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

Ivan Kelly updated BOOKKEEPER-317:
----------------------------------

    Attachment: BOOKKEEPER-317.diff

Fixed the typo in compatibility, renamed exception and added serialVersionUIDs which are randomly generated.

I didn't add the structural stuff for error codes and #create(). These things are for async apis. These exceptions are only for the replication service, which will run as a daemon, with no interactive apis. api's for checking a ledger or running replication will be async, but they will be on org.apache.bookkeeper.client.BookKeeperAdmin (they have to be in the client package to access internals). As such, they will use BKException.
                
> Exceptions for replication
> --------------------------
>
>                 Key: BOOKKEEPER-317
>                 URL: https://issues.apache.org/jira/browse/BOOKKEEPER-317
>             Project: Bookkeeper
>          Issue Type: Sub-task
>            Reporter: Ivan Kelly
>            Assignee: Ivan Kelly
>             Fix For: 4.2.0
>
>         Attachments: BOOKKEEPER-317.diff, BOOKKEEPER-317.diff
>
>
> A couple of the BOOKKEEPER-237 jiras need to add new exceptions. This jira creates the umbrella exception which they can all go under.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira