[
https://issues.apache.org/jira/browse/HDFS-11604?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15951891#comment-15951891
]
Kai Zheng commented on HDFS-11604:
----------------------------------
Some comments:
* We can use the name {{ec_policy_sample.xml}} instead. This sample file could
be put into Hadoop conf folder.
* We need a header as comment to list the system policies so that users won't
redefine them here.
* Can we add some comments for some parts to specify some formats, like for
{{cellsize}}, only {{k}}, {{m}} are allowed after a positive number.
* Can we use the real codecs and schemas available for now? I mean,
{{rs-legacy}}, {{rs}} and {{xor}}. {{HH}} ones aren't available to HDFS yet.
For RS family, we can have 3 + 2, 6 + 3 and 10 + 4 schemas.
> 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
>
>
> 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]
