[
https://issues.apache.org/jira/browse/BOOKKEEPER-250?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13295361#comment-13295361
]
Sijie Guo commented on BOOKKEEPER-250:
--------------------------------------
{quote}
ManagerLayout should use protobufs
{quote}
good point. would improve it in new patch.
{quote}
But I don't understand why TopicManager has now become an implementer of the
manager interface?
{quote}
MMTopicManager is using version write for ledger election, so it writes the
owner info as persist znode in ZooKeeper, which is different from
ZKTopicManager. I tried to leverage ManagerLayout to record manager class and
version, and initiate the topic manager according to manager layout info
recorded in zookeeper to load right manager.
> Need a ledger manager like interface to manage metadata operations in Hedwig
> ----------------------------------------------------------------------------
>
> Key: BOOKKEEPER-250
> URL: https://issues.apache.org/jira/browse/BOOKKEEPER-250
> Project: Bookkeeper
> Issue Type: Sub-task
> Reporter: Sijie Guo
> Assignee: Sijie Guo
> Fix For: 4.2.0
>
> Attachments: BOOKKEEPER-250.diff, BOOKKEEPER-250.diff,
> BOOKKEEPER-250.diff_v2
>
>
> it would be better to a ledger-manager like interface to manage metadata
> operations in Hedwig, which might be easy for use to adapt to meta store api.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
