[
https://issues.apache.org/jira/browse/HDFS-12000?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16078375#comment-16078375
]
Mukul Kumar Singh commented on HDFS-12000:
------------------------------------------
Thanks for the document [~cheersyang], the idea looks very good. I have some
questions
1) I would feel that we should keep a monotonically increasing number in place
of timestamp. This would be needed in cases where there are multiple PUT
requests for the same key at the same time, we might end up assigning the same
version in this case. Something like AtomicLong will help in generating
efficient version ids.
2) for Info key would it make sense to know how many versions of the key exists
? This will be useful to understand and debug space allocation issues.
> Ozone: Container : Add key versioning support
> ---------------------------------------------
>
> Key: HDFS-12000
> URL: https://issues.apache.org/jira/browse/HDFS-12000
> Project: Hadoop HDFS
> Issue Type: Sub-task
> Components: ozone
> Affects Versions: HDFS-7240
> Reporter: Anu Engineer
> Assignee: Chen Liang
>
> The rest interface of ozone supports versioning of keys. This support comes
> from the containers and how chunks are managed to support this feature. This
> JIRA tracks that feature. Will post a detailed design doc so that we can talk
> about this feature.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
---------------------------------------------------------------------
To unsubscribe, e-mail: hdfs-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org
