[
https://issues.apache.org/jira/browse/ZOOKEEPER-276?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Flavio Paiva Junqueira updated ZOOKEEPER-276:
---------------------------------------------
Attachment: ZOOKEEPER-276.patch
On issue 1: we have checked with Patrick Hunt (and Patrick checked with Doug
Cutting) that it is ok to use org.apache.bookkeeper). I also prefer it that way;
On issue 2: Unfortunately my compiler doesn't complain about the override tags
you mentioned (I'm on macos, jvm 1.6.0), so I just removed the ones you pointed
out. Please give it another try.
> Bookkeeper contribution
> -----------------------
>
> Key: ZOOKEEPER-276
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-276
> Project: Zookeeper
> Issue Type: New Feature
> Reporter: Luca Telloli
> Assignee: Flavio Paiva Junqueira
> Fix For: 3.1.0
>
> Attachments: ZOOKEEPER-276.patch, ZOOKEEPER-276.patch,
> ZOOKEEPER-276.patch, ZOOKEEPER-276.patch, ZOOKEEPER-276.patch
>
>
> BookKeeper is a system to reliably log streams of records. In BookKeeper,
> servers are "bookies", log streams are "ledgers", and each unit of a log (aka
> record) is a "ledger entry". BookKeeper is designed to be reliable; bookies,
> the servers that store ledgers can be byzantine, which means that some subset
> of the bookies can fail, corrupt data, discard data, but as long as there are
> enough correctly behaving servers the service as a whole behaves correctly;
> the meta data for BookKeeper is stored in ZooKeeper.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
