You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@bookkeeper.apache.org by "Matteo Merli (JIRA)" <ji...@apache.org> on 2016/05/16 21:48:16 UTC

[jira] [Closed] (BOOKKEEPER-879) Record ledger creation time

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

Matteo Merli closed BOOKKEEPER-879.
-----------------------------------

Closed as part of BookKeeper-4.4.0 release

> Record ledger creation time
> ---------------------------
>
>                 Key: BOOKKEEPER-879
>                 URL: https://issues.apache.org/jira/browse/BOOKKEEPER-879
>             Project: Bookkeeper
>          Issue Type: New Feature
>          Components: bookkeeper-client, bookkeeper-server
>    Affects Versions: 4.3.1
>            Reporter: Enrico Olivelli
>            Assignee: Enrico Olivelli
>             Fix For: 4.4.0
>
>
> I think that a creation timestamp would be very useful and it does not cost very much. It would be an immutable value. 
> Nowadays (on 4.3.1) I must keep that info together with the id of the ledger,  for instance in zookeeper,  but if that reference gets lost there is now way to know how old a ledger is.
> I think that this timestamp should be captured on client while calling createLedger or asyncCreateLedger.
> In addition to this very common field maybe it would be useful to add a custom byte[] field named "custom client data" in order to let the client 'describe' the ledger without the need of extra data on Zookeeper. 



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