[ 
https://issues.apache.org/jira/browse/BOOKKEEPER-552?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15882990#comment-15882990
 ] 

ASF GitHub Bot commented on BOOKKEEPER-552:
-------------------------------------------

Github user jvrao commented on the issue:

    https://github.com/apache/bookkeeper/pull/112
  
    Couple of questions:
    1. Charan with this change how does LongHierarchicalLedgerManager users 
(Salesforce) has backward compatibility?
    2.  @knusbaum Why not keep LongHierarchicalLedgerManager around? even when 
HierarchicalLedgerManager supporting both ids.?


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

Reply via email to