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

Kai Zheng commented on HDFS-11604:
----------------------------------

Quick comments:
* {{PolicyLoader}} would be good to be {{ECPolicyLoader}}, as various policy 
concepts in Hadoop;
* The template {{ec_policy_sample.xml}} file would be good to be here: 
{{hadoop-hdfs-project/hadoop-hdfs/resources}};
* Can we move the policy parser/loader utility into this package in the client 
module: {{hadoop-hdfs-project/hadoop-hdfs-client/o.a.h.hdfs.util}}
* A minor: "Load predefined ec policies from configuration file." => "Load user 
defined ec policies from a XML configuration file."
* Minor: please avoid star/* imports.

> Define and parse erasure code codecs, schemas and policies
> ----------------------------------------------------------
>
>                 Key: HDFS-11604
>                 URL: https://issues.apache.org/jira/browse/HDFS-11604
>             Project: Hadoop HDFS
>          Issue Type: Sub-task
>          Components: erasure-coding
>            Reporter: Kai Zheng
>            Assignee: Lin Zeng
>             Fix For: 3.0.0-alpha3
>
>         Attachments: ec-config-sample.xml, ec-policy-config-sample-v2.xml, 
> HDFS-11604-v1.patch, HDFS-11604-v2.patch, HDFS-11604-v3.patch, 
> HDFS-11604-v4.patch
>
>
> According to recent discussions with [~andrew.wang] in HDFS-7337, it would be 
> good to support allowing users to define their own erasure code codecs, 
> schemas and policies via an XML file. The XML file can be passed to a CLI cmd 
> to parse and send to NameNode to persist and maintain.
> Open this task to define the XML format providing a default sample file to 
> put in the configuration folder for users' reference, and implement the 
> necessary parser utility.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to