[
https://issues.apache.org/jira/browse/HDFS-7859?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14495556#comment-14495556
]
Kai Zheng commented on HDFS-7859:
---------------------------------
bq.Using schema name as ID
As we would not make it heavy so don't have some field like {{description}} for
an {{ECSchema}}, a friendly name like {{RS-6-3}} would make it more sense in
the way rather than an number ID. Users should be clearly understand the schema
before using it to create any zone. The name will help with identifying that.
bq.We don't even need the xml file.
Yeah, if we would do that thru command to define a schema by specifying the
schema parameters, it should also be OK. I don't have strongly preference about
that. Any file format or even not using file would also work I guess. We talked
about this in the meetup, looks like XML file was synced.
> Erasure Coding: Persist EC schemas in NameNode
> ----------------------------------------------
>
> Key: HDFS-7859
> URL: https://issues.apache.org/jira/browse/HDFS-7859
> Project: Hadoop HDFS
> Issue Type: Sub-task
> Reporter: Kai Zheng
> Assignee: Xinwei Qin
> Attachments: HDFS-7859.001.patch
>
>
> In meetup discussion with [~zhz] and [~jingzhao], it's suggested that we
> persist EC schemas in NameNode centrally and reliably, so that EC zones can
> reference them by name efficiently.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
