hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Chen Liang (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (HDFS-12954) Ozone: Container : Add key versioning support-3
Date Thu, 21 Dec 2017 23:05:00 GMT

     [ https://issues.apache.org/jira/browse/HDFS-12954?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel

Chen Liang updated HDFS-12954:
    Attachment: HDFS-12954-HDFS-7240.001.patch

> 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
>         Attachments: HDFS-12954-HDFS-7240.001.patch
> 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

To unsubscribe, e-mail: hdfs-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-help@hadoop.apache.org

View raw message