Github user jvrao commented on the issue:
https://github.com/apache/bookkeeper/pull/200
@sijie what is the major drive of this change? Current method of trying
speculative reads has any major flaw? I understand this is better organized as
speculative reads has its own policy, but trying to understand what use-case
drove you to this change at Twitter?
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---
