hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Xiaoyu Yao (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HDFS-11920) Ozone : add key partition
Date Mon, 31 Jul 2017 22:53:00 GMT

    [ https://issues.apache.org/jira/browse/HDFS-11920?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16108115#comment-16108115

Xiaoyu Yao commented on HDFS-11920:

Thanks [~vagarychen] for updating the patch. Agree that we can leave the delete part to the
DeleteKey feature. 
+1 given the two Jenkins failures are known issues. 

> Ozone : add key partition
> -------------------------
>                 Key: HDFS-11920
>                 URL: https://issues.apache.org/jira/browse/HDFS-11920
>             Project: Hadoop HDFS
>          Issue Type: Sub-task
>            Reporter: Chen Liang
>            Assignee: Chen Liang
>         Attachments: HDFS-11920-HDFS-7240.001.patch, HDFS-11920-HDFS-7240.002.patch,
HDFS-11920-HDFS-7240.003.patch, HDFS-11920-HDFS-7240.004.patch, HDFS-11920-HDFS-7240.005.patch,
HDFS-11920-HDFS-7240.006.patch, HDFS-11920-HDFS-7240.007.patch, HDFS-11920-HDFS-7240.008.patch,
HDFS-11920-HDFS-7240.009.patch, HDFS-11920-HDFS-7240.010.patch
> Currently, each key corresponds to one single SCM block, and putKey/getKey writes/reads
to this single SCM block. This works fine for keys with reasonably small data size. However
if the data is too huge, (e.g. not even fits into a single container), then we need to be
able to partition the key data into multiple blocks, each in one container. This JIRA changes
the key-related classes to support this.

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