[
https://issues.apache.org/jira/browse/ZOOKEEPER-959?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12977827#action_12977827
]
Benjamin Reed commented on ZOOKEEPER-959:
-----------------------------------------
flavio and i talked about this this morning. i think flavio's proposal works.
it does have the downside of adding per record overhead. for some applications
this might be a feature because you can put each record on a timeline, but for
others that don't care, it would be an unnecessary overhead. another option
would be to put timestamps into the znode that represents the ledger. we
obviously wouldn't update the timestamp on every write. i was thinking the
timestamps would be updated only on close or recovery. i think that would be
sufficient for your needs. right?
> Last modification time of a bookkeeper ledger
> ---------------------------------------------
>
> Key: ZOOKEEPER-959
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-959
> Project: ZooKeeper
> Issue Type: Improvement
> Components: contrib-bookkeeper
> Reporter: dhruba borthakur
> Fix For: 3.4.0
>
>
> I would like to discuss how hard or easy it will be to implement a bookkeeper
> api that returns the last modification time of a ledger. This is related to
> ZOOKEEPER-465.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
