hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Kai Sasaki (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HDFS-8136) Client gets and uses EC schema when reads and writes a stripping file
Date Mon, 20 Apr 2015 04:39:00 GMT

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

Kai Sasaki commented on HDFS-8136:
----------------------------------

Thank you for comment. {{TestDFSStripedOutputStream}} has also the methods whose names does
not start with small letter. Can I also fix it in this JIRA or It's better to open other JIRA?

> Client gets and uses EC schema when reads and writes a stripping file
> ---------------------------------------------------------------------
>
>                 Key: HDFS-8136
>                 URL: https://issues.apache.org/jira/browse/HDFS-8136
>             Project: Hadoop HDFS
>          Issue Type: Sub-task
>    Affects Versions: HDFS-7285
>            Reporter: Kai Zheng
>            Assignee: Kai Sasaki
>         Attachments: HDFS-8136.1.patch, HDFS-8136.2.patch
>
>
> Discussed with [~umamaheswararao] and [~vinayrpet], in client when reading and writing
a stripping file, it can invoke a separate call to NameNode to request the EC schema associated
with the EC zone where the file is in. Then the schema can be used to guide the reading and
writing. Currently it uses hard-coded values.
> Optionally, as an optimization consideration, client may cache schema info per file or
per zone or per schema name. We could add schema name in {{HdfsFileStatus}} for that.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message