[
https://issues.apache.org/jira/browse/BOOKKEEPER-879?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15028540#comment-15028540
]
Enrico Olivelli commented on BOOKKEEPER-879:
--------------------------------------------
I agree that the ZK backup/restore as I describe is not feasible.
If we are going to use the ZK metadata (z-node ctime/mtime) maybe it would be
better not to include this info in LedgerMetadata but to add a new data
structure like LedgerInfo (maybe a better name). ctime and mtime are only for
descriptive purposes and are not useful to Bookkeeper Internals.
We can simply add a new method to BookKeeperAdmin, in this case the
LedgerHandle and other internals will not be touched by this new feature, and
there will be not impact on compatibility of older clients
> 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)
