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

Posted to dev@bookkeeper.apache.org by "Sijie Guo (JIRA)" <ji...@apache.org> on 2017/06/22 00:29:00 UTC

[jira] [Resolved] (BOOKKEEPER-223) PendingReadOp tries to read all entries at once

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

Sijie Guo resolved BOOKKEEPER-223.
----------------------------------
       Resolution: Won't Do
    Fix Version/s:     (was: 4.5.0)

There is already an listener based pending read op, which it calls the callback individually. it doesn't really meet all the requirement here, but it serves some purpose.

> PendingReadOp tries to read all entries at once
> -----------------------------------------------
>
>                 Key: BOOKKEEPER-223
>                 URL: https://issues.apache.org/jira/browse/BOOKKEEPER-223
>             Project: Bookkeeper
>          Issue Type: Bug
>          Components: bookkeeper-client
>            Reporter: Ivan Kelly
>            Assignee: Ivan Kelly
>
> PendingReadOp tries to read all entries from the bookie ensemble at once, and fill an enumeration with what comes back. This is bad. If we have a ledger with millions of entries, and you try to read the whole thing, you're client will crap out. Of course you can get around this by only requesting a little bit at a time, but why doesn't the client do this for you, as we are effectively exposing a iterator interface anyhow?



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)