[
https://issues.apache.org/jira/browse/BOOKKEEPER-2?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ivan Kelly updated BOOKKEEPER-2:
--------------------------------
Attachment: BOOKKEEPER-2.diff
Patch is pretty straight forward. For all new ledgers, store the password and
digest type. They can then be opened without having to specify the password
using asyncOpenLedger on BookKeeperAdmin. I've only create async versions of
the calls for now. We can add sync in future is people want them. This api
isn't for general use, only from administrative tools.
> bookkeeper does not put enough meta-data in to do recovery properly
> -------------------------------------------------------------------
>
> Key: BOOKKEEPER-2
> URL: https://issues.apache.org/jira/browse/BOOKKEEPER-2
> Project: Bookkeeper
> Issue Type: Sub-task
> Reporter: Benjamin Reed
> Fix For: 4.2.0
>
> Attachments: BOOKKEEPER-2.diff
>
>
> somewhere, probably zookeeper, we need to keep track of the the information
> about keys used for access and for mac validation as well as the digest type
> for entries. we can't write a general recovery tool without it.
--
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
