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 "J.Andreina (JIRA)" <ji...@apache.org> on 2015/09/11 06:08:46 UTC
[jira] [Commented] (HDFS-8853) Erasure Coding: Provide ECSchema
validation when setting EC policy
[ https://issues.apache.org/jira/browse/HDFS-8853?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14740135#comment-14740135 ]
J.Andreina commented on HDFS-8853:
----------------------------------
Thanks [~zhz] for the commit .
> Erasure Coding: Provide ECSchema validation when setting EC policy
> ------------------------------------------------------------------
>
> Key: HDFS-8853
> URL: https://issues.apache.org/jira/browse/HDFS-8853
> Project: Hadoop HDFS
> Issue Type: Sub-task
> Reporter: Rakesh R
> Assignee: J.Andreina
> Fix For: HDFS-7285
>
> Attachments: HDFS-8853-HDFS-7285-01.patch, HDFS-8853-HDFS-7285-05.patch, HDFS-8853-HDFS-7285-06.patch, HDFS-8853-HDFS-7285-merge-02.patch, HDFS-8853-HDFS-7285-merge-03.patch, HDFS-8853-HDFS-7285-merge-04.patch
>
>
> Presently the {{DFS#createErasureCodingZone(path, ecSchema, cellSize)}} doesn't have any validation that the given {{ecSchema}} is available in {{ErasureCodingSchemaManager#activeSchemas}} list. Now, if it doesn't exists then will create the ECZone with {{null}} schema. IMHO we could improve this by doing necessary basic sanity checks.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)