[
https://issues.apache.org/jira/browse/BOOKKEEPER-879?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15097788#comment-15097788
]
Enrico Olivelli commented on BOOKKEEPER-879:
--------------------------------------------
I have to change LedgerMetadata.parseConfig in order to take the ZK ctime
field, I have some options:
1) change the signature and add an explicit "long ctime"
2) change the Version structure (for ZKVersion we will get the ctime from the
Stat)
the option 2 is not good because ctime is not about versioning, since it is
immutable
for the option 1 I hit anyway a problem on MSLedgerManagerFactory, can I let it
to be 0 for MSLedgerManagerFactory ?
> 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
> 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)
