[
https://issues.apache.org/jira/browse/BOOKKEEPER-562?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Flavio Junqueira updated BOOKKEEPER-562:
----------------------------------------
Attachment: BOOKKEEPER-562.patch
I have fixed it according to the comments. One point I was thinking about, it
is not necessary to have ledgerId parameter for the complete call, is it? We
can always pass it as part of the context object if necessary, but I wanted to
make sure that we agree.
> Ability to tell if a ledger is closed or not
> --------------------------------------------
>
> Key: BOOKKEEPER-562
> URL: https://issues.apache.org/jira/browse/BOOKKEEPER-562
> Project: Bookkeeper
> Issue Type: New Feature
> Reporter: Whitney Sorenson
> Assignee: Flavio Junqueira
> Fix For: 4.3.0
>
> Attachments: BOOKKEEPER-562-1.patch, BOOKKEEPER-562.patch,
> BOOKKEEPER-562.patch, BOOKKEEPER-562.patch, BOOKKEEPER-562.patch,
> BOOKKEEPER-562.patch
>
>
> We need to be able to differentiate between open and closed ledgers, because
> we want to persist ledgers which are closed and wait for ledgers that are
> open to close.
> There doesn't seem to be an easy way to get a list of closed / open ledgers
> or to query bk to ask if a specific ledger is open or closed.
--
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
