[
https://issues.apache.org/jira/browse/BOOKKEEPER-1087?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16033676#comment-16033676
]
ASF GitHub Bot commented on BOOKKEEPER-1087:
--------------------------------------------
Github user sijie commented on the issue:
https://github.com/apache/bookkeeper/pull/177
@eolivelli I think a better approach is to complete the reviews for all the
sub-tasks for a given master JIRA before merging. otherwise, I have to rebase
every time you merged.
for example, all the ledger recovery changes are sub-tasks of
https://issues.apache.org/jira/browse/BOOKKEEPER-757. I haven't sent them out
yet.
If you are okay, you can defer merging to me.
> Ledger Recovery - Add a parallel reading request in PendingReadOp
> -----------------------------------------------------------------
>
> Key: BOOKKEEPER-1087
> URL: https://issues.apache.org/jira/browse/BOOKKEEPER-1087
> Project: Bookkeeper
> Issue Type: Sub-task
> Components: bookkeeper-client
> Reporter: Sijie Guo
> Assignee: Sijie Guo
> Fix For: 4.5.0
>
>
> bookkeeper recovery improvement (part-2): add a parallel reading request
> in PendingReadOp
> - add a parallel reading request in PendingReadOp
> - allow PendingReadOp to configure whether to do parallel reading or not
> - add flag in ClientConfiguration to allow configuring whether to do
> parallel reading in LedgerRecoveryOp or not.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
