[
https://issues.apache.org/jira/browse/HDFS-7859?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15242483#comment-15242483
]
Kai Zheng commented on HDFS-7859:
---------------------------------
bq. IIUC, persistence is more necessary when we supports custom schemas, isn't
it?
I thought you're right. For the builtin schema and policies, IIRC, there was a
consideration that we still need to persist the schema and policy to indicate
the software upgrades (so the builtin ones may be changed).
bq. Do we have any plan to implement HDFS-7337?
I thought many considerations originally targeted for the issue have already
been implemented elsewhere, therefore the only thing left is custom codec and
schema support. I don't think there is a strong requirement for this feature
but we can implement it perhaps in phase II I guess.
> Erasure Coding: Persist erasure coding policies 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
> Labels: BB2015-05-TBR
> Attachments: HDFS-7859-HDFS-7285.002.patch,
> HDFS-7859-HDFS-7285.002.patch, HDFS-7859-HDFS-7285.003.patch,
> HDFS-7859.001.patch, HDFS-7859.002.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)
