[jira] [Updated] (BOOKKEEPER-518) Lazily load hedwig metadata for different types of requests

["Jiannan Wang (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/BOOKKEEPER-518?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jiannan Wang updated BOOKKEEPER-518:
------------------------------------

    Assignee: Jiannan Wang
    
> Lazily load hedwig metadata for different types of requests
> -----------------------------------------------------------
>
>                 Key: BOOKKEEPER-518
>                 URL: https://issues.apache.org/jira/browse/BOOKKEEPER-518
>             Project: Bookkeeper
>          Issue Type: Sub-task
>          Components: hedwig-client, hedwig-server
>            Reporter: Sijie Guo
>            Assignee: Jiannan Wang
>             Fix For: 4.3.0
>
>
> Currently, acquire a topic needs to load both persistence info and subscriptions info at the same time. only after that, the topic acquisition could succeed. but it seems that, for a sub/closesub/unsub request, we just need subscription info. for a pub request, we just need persistence info. especially, for a subscriber requests, we don't need to create a new ledger if there is no messages. we could delay provisioning ledger when messages arrive. otherwise, it introduced unnecessary metadata creation.
> for some applications, lazily loading might be necessary. for some applications, it might be not. it should be configurable.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira