hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "J.Andreina (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HDFS-8853) Erasure Coding: Provide ECSchema validation when creating ECZone
Date Thu, 20 Aug 2015 09:31:46 GMT

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

J.Andreina commented on HDFS-8853:
----------------------------------

Thanks [~zhz]  . 
Sorry for the delay in updating the patch. Please review.

bq. In the long term, it might be better for the client to pass a String to NN instead of
the actual policy/schema.

Here do you mean , to pass only the policy name which creating the zone.?

> Erasure Coding: Provide ECSchema validation when creating ECZone
> ----------------------------------------------------------------
>
>                 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
>         Attachments: HDFS-8853-HDFS-7285-01.patch, HDFS-8853-HDFS-7285-merge-02.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)

Mime
View raw message