[
https://issues.apache.org/jira/browse/HDFS-7866?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14494953#comment-14494953
]
Tsz Wo Nicholas Sze commented on HDFS-7866:
-------------------------------------------
[~drankye], [~vinayrpet] I think we need a design for EC schema to specify what
operations are supported; see [this
comment|https://issues.apache.org/jira/browse/HDFS-7859?focusedCommentId=14494933&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-14494933]
in HDFS-7859. Also, we only support one schema (6,3)-Reed-Solomon in the
first phase HDFS-7285. I think we should focus on finishing a complete, working
basic EC feature and get HDFS-7285 merged to trunk. How about deferring this
work to HDFS-8031? Sorry for commenting on this late and thanks for all the
good works.
> 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: Kai Zheng
> Attachments: HDFS-7866-v1.patch, HDFS-7866-v2.patch,
> HDFS-7866-v3.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)
