You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@bookkeeper.apache.org by "Flavio Junqueira (JIRA)" <ji...@apache.org> on 2011/06/23 10:23:47 UTC

[jira] [Updated] (BOOKKEEPER-11) Read from open ledger

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

Flavio Junqueira updated BOOKKEEPER-11:
---------------------------------------

    Attachment: BOOKKEEPER-11.patch

Preliminary patch, it does not include tests, but compiles and original tests pass (not surprising given the patch).

This patch changes the API to add calls that allow an application to:

# Open a ledger unsafely for reading. Unsafely means that the client won't try to recover if the ledger is not closed. Opening a ledger this way, enables a client app to read from an open ledger;
# Request the last confirmed entry from some quorum of bookies.

> Read from open ledger
> ---------------------
>
>                 Key: BOOKKEEPER-11
>                 URL: https://issues.apache.org/jira/browse/BOOKKEEPER-11
>             Project: Bookkeeper
>          Issue Type: New Feature
>            Reporter: Flavio Junqueira
>         Attachments: BOOKKEEPER-11.patch, zk-1001-design-doc.pdf, zk-1001-design-doc.pdf
>
>
> The BookKeeper client currently does not allow a client to read from an open ledger. That is, if the creator of a ledger is still writing to it (and the ledger is not closed), then an attempt to open the same ledger for reading will execute the code to recover the ledger, assuming that the ledger has not been correctly closed.
> It seems that there are applications that do require the ability to read from a ledger while it is being written to, and the main goal of this jira is to discuss possible implementations of this feature.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira