You are viewing a plain text version of this content. The canonical link for it is here.
Posted to hdfs-issues@hadoop.apache.org by "Chen Liang (JIRA)" <ji...@apache.org> on 2017/12/21 00:50:01 UTC
[jira] [Created] (HDFS-12954) Ozone: Container : Add key versioning
support-3
Chen Liang created HDFS-12954:
---------------------------------
Summary: Ozone: Container : Add key versioning support-3
Key: HDFS-12954
URL: https://issues.apache.org/jira/browse/HDFS-12954
Project: Hadoop HDFS
Issue Type: Sub-task
Components: ozone
Affects Versions: HDFS-7240
Reporter: Chen Liang
Assignee: Chen Liang
A new version of a key is effectively overwriting some consecutive range of bytes in the entire key offset range. For each version, we need to keep exactly what the range is in order for the IO vector to work.
Currently, since we only write from the start (offset = 0), so offset range of a version is only up to the key data size field when the version gets committed. But currently we only keep one single key data size variable.(see {{KeyManagerImpl#commitKey}}). We need to know the corresponding key data size for each version. This JIRA is to the tracking of offset range for each version.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
---------------------------------------------------------------------
To unsubscribe, e-mail: hdfs-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-help@hadoop.apache.org