[
https://issues.apache.org/jira/browse/HDFS-7866?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15075037#comment-15075037
]
Walter Su commented on HDFS-7866:
---------------------------------
To [~drankye],
[There|https://issues.apache.org/jira/browse/HDFS-8833?focusedCommentId=14658978&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-14658978]
is a discussion about whether to hard-code policy or not.
I think hard-coding will do. But there is {{ECSchema.extraOptions}}. I don't
know if your original idea is to make it configurable?
> Erasure coding: NameNode manages EC schemas
> -------------------------------------------
>
> Key: HDFS-7866
> URL: https://issues.apache.org/jira/browse/HDFS-7866
> Project: Hadoop HDFS
> Issue Type: Sub-task
> Reporter: Kai Zheng
> Assignee: Rui Li
> Attachments: HDFS-7866-v1.patch, HDFS-7866-v2.patch,
> HDFS-7866-v3.patch, HDFS-7866.4.patch, HDFS-7866.5.patch, HDFS-7866.6.patch,
> HDFS-7866.7.patch
>
>
> This is to extend NameNode to load, list and sync predefine EC schemas in
> authorized and controlled approach. The provided facilities will be used to
> implement DFSAdmin commands so admin can list available EC schemas, then
> could choose some of them for target EC zones.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
