[
https://issues.apache.org/jira/browse/BOOKKEEPER-552?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15883552#comment-15883552
]
ASF GitHub Bot commented on BOOKKEEPER-552:
-------------------------------------------
Github user knusbaum commented on the issue:
https://github.com/apache/bookkeeper/pull/112
@jvrao @reddycharan
So my plan is this: Keep LongHierarchicalLedgerManager as is currently in
master, move HierarchicalLedgerManager to LegacyHierarchicalLedgerManager and
create the new backwards-compatible one as HierarchicalLedgerManager. This way,
if you're already using LongHierarchicalLedgerManager, it will still work. If
you're using the current HierarchicalLedgerManager, that will work, and if you
(for some unknown reason) want to use the old legacy one, it still exists as
well.
Thoughts?
> 64 Bits Ledger ID Generation
> ----------------------------
>
> Key: BOOKKEEPER-552
> URL: https://issues.apache.org/jira/browse/BOOKKEEPER-552
> Project: Bookkeeper
> Issue Type: Sub-task
> Components: bookkeeper-client, bookkeeper-server, hedwig-server
> Reporter: Jiannan Wang
> Assignee: Kyle Nusbaum
> Attachments: BOOKKEEPER-552.patch, BOOKKEEPER-552.patch,
> BOOKKEEPER-552.patch
>
>
> This task aims to find and implement 64 bits global unique ledger id
> generation mechanisms.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
