[
https://issues.apache.org/jira/browse/BOOKKEEPER-879?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15024739#comment-15024739
]
Enrico Olivelli commented on BOOKKEEPER-879:
--------------------------------------------
I would like to start working on this issue, I have some question:
1) which is the best name for this new field ? maybe "creationTimestamp"
2) I see that LedgerMetadata serialized format is very difficult to extend, the
ensemble list ends with a 'closed' line, should I create a new METADATA_VERSION
= 2 ? or use some trick like adding a "timestamp:xxxx" line (using a prefix ?)
? I don't know how to preserve compatibility for rolling upgrades
3) I see that LedgerMetadata conversion from String to byte[] is done using the
system encoding, sould I file another issue for this problem ? actually data
does not contain locale sensitive info (usually addresses use only latin
characters)
> 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
>
> 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)
