[
https://issues.apache.org/jira/browse/BOOKKEEPER-257?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13636274#comment-13636274
]
Flavio Junqueira commented on BOOKKEEPER-257:
---------------------------------------------
bq. LedgerManager#asyncProcessLedgers is not exposed as an API for clients. Do
you guys want to expose LedgerManager to application directly?
Agreed, if we do it, it might be a good idea to wrap it in some way.
bq. It would be nice to expose something a little more user friendly for
clients. Perhaps on BookKeeper admin.
In the way I interpreted [~jiannan]'s observation, he was saying that
[~wsorenson] could process the ledgers directly. According to the description
of the jira, they want a list to iterate over the ledgers, so perhaps they
could do their processing there directly. There is the issue of exposing
internals as [~hustlmsp] has pointed out.
> Ability to list all ledgers
> ---------------------------
>
> Key: BOOKKEEPER-257
> URL: https://issues.apache.org/jira/browse/BOOKKEEPER-257
> Project: Bookkeeper
> Issue Type: New Feature
> Reporter: Ivan Kelly
> Fix For: 4.3.0
>
>
> When an application is using bookkeeper it must keep a copy of the ledger ids
> it creates so that they can be used later, and once they are no longer
> useful, deleted. However, in the case of a crash between ledger creation and
> persisting the application copy of the id, the ledger will be dangling.
> Therefore I propose we have the ability to get a list of all ledger ids,
> which clients can use for garbage collection. However, I don't think it
> should be part of the BookKeeper class, rather part of a new BookKeeperAdmin
> class.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
