You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@bookkeeper.apache.org by "Ivan Kelly (JIRA)" <ji...@apache.org> on 2013/02/13 16:48:24 UTC

[jira] [Closed] (BOOKKEEPER-444) Refactor pending read op to make speculative reads possible

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

Ivan Kelly closed BOOKKEEPER-444.
---------------------------------

    
> Refactor pending read op to make speculative reads possible
> -----------------------------------------------------------
>
>                 Key: BOOKKEEPER-444
>                 URL: https://issues.apache.org/jira/browse/BOOKKEEPER-444
>             Project: Bookkeeper
>          Issue Type: Sub-task
>            Reporter: Ivan Kelly
>            Assignee: Ivan Kelly
>             Fix For: 4.2.0
>
>         Attachments: 0001-BOOKKEEPER-444-Refactor-pending-read-op-to-make-spec.patch, 0001-BOOKKEEPER-444-Refactor-pending-read-op-to-make-spec.patch
>
>
> The code to handle the state of a single entry read request is scattered all over PendingReadOp. Some even leaks into LedgerEntry. This jira is to refactor this code into one place to make speculative reads easier to implement.

--
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