[
https://issues.apache.org/jira/browse/HDFS-8074?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14484928#comment-14484928
]
Uma Maheswara Rao G edited comment on HDFS-8074 at 4/8/15 8:26 AM:
-------------------------------------------------------------------
Yeah, But I thought ECSchemanager can load configs from XML. When instantiating
ECSchemaManager, we can load required configs from edschema-def.xml file. If
you are also thinking the similar change then we can incorporate here itself.
May be ECSchemaManager can take config from its Ctor. BTW, I have no concern if
we want to handle the improvements in followups.
was (Author: umamaheswararao):
Yeah, But I thought ECSchemanager can load configs from XML. When instantiating
ECSchemaManager, we can load required configs from edschema-def.xml file. If
you are also thinking the similar change then we can incorporate here itself.
May be ECSchemaManager can take config from its Ctor.
> Define a system-wide default EC schema
> --------------------------------------
>
> Key: HDFS-8074
> URL: https://issues.apache.org/jira/browse/HDFS-8074
> Project: Hadoop HDFS
> Issue Type: Sub-task
> Reporter: Kai Zheng
> Assignee: Kai Zheng
> Attachments: HDFS-8074-v1.patch, HDFS-8074-v2.patch,
> HDFS-8074-v3.patch
>
>
> It's good to have a system default EC schema first with fixed values before
> we support more schemas. This makes sense to resolve some dependencies before
> HDFS-7866 can be done in whole. The default system schema is also needed
> anyhow essentially when admin just wants to use it.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
