You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@bookkeeper.apache.org by "Sijie Guo (JIRA)" <ji...@apache.org> on 2016/07/11 21:02:11 UTC

[jira] [Resolved] (BOOKKEEPER-922) Create a generic (K,V) map to store ledger metadata

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

Sijie Guo resolved BOOKKEEPER-922.
----------------------------------
    Resolution: Fixed

Issue resolved by merging pull request 46
            [https://github.com/apache/bookkeeper/pull/46]

            {noformat}
            commit 6d71b8292bc255e21f2dcf048be191650c01b4dc
Author:     Rithin <ri...@salesforce.com>
AuthorDate: Mon Jul 11 14:01:30 2016 -0700
Commit:     Sijie Guo <si...@apache.org>
CommitDate: Mon Jul 11 14:01:30 2016 -0700

    BOOKKEEPER-922: CreaterId in ledger metadata
    
    Introduces a generic Map<String, byte[]> customMetadata to be stored as part of ledger metadata on the metadata server(zk).
    
    Author: Rithin Shetty <rithingmail.com>
    
    Author: Rithin <ri...@salesforce.com>
    
    Reviewers: Enrico Olivelli <eo...@gmail.com>, Sijie Guo <si...@apache.org>
    
    Closes #46 from rithin-shetty/JIRA-922-ledgerCustomMetadata

            {noformat}
            

> Create a generic (K,V) map to store ledger metadata
> ---------------------------------------------------
>
>                 Key: BOOKKEEPER-922
>                 URL: https://issues.apache.org/jira/browse/BOOKKEEPER-922
>             Project: Bookkeeper
>          Issue Type: Improvement
>          Components: bookkeeper-client
>    Affects Versions: 4.3.2
>            Reporter: Venkateswararao Jujjuri (JV)
>            Assignee: Rithin Shetty
>             Fix For: 4.5.0
>
>
> We have introduced ctime into ledger metadata through https://issues.apache.org/jira/browse/BOOKKEEPER-879.
> In the same token we would like to introduce createrId also. This can be a 128 bit UUID. Caller can write tools to group ledgers by createrId, in the future we can even enhance this to run queries based on createrId. 
>  



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)