[
https://issues.apache.org/jira/browse/HDFS-7859?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14497306#comment-14497306
]
Kai Zheng commented on HDFS-7859:
---------------------------------
[~szetszwo],
bq.Since we don't not yet support add/delete/update/rename schema operations,
we don't need to persist anything in NN at this moment. We will support some of
these schema operations down the road. We may persist schemas at that time.
Sound good?
Please note it's not true "we don't need to persist anything in NN at this
moment.". We had already persisted some hard-coded values that should be
covered by a schema in the image. Without this, we will definitely need to
revisit the image format change some time later. As I said above, it's flexible
enough in the schema definition and if we persist the whole schema object in
image, we would not likely need to change the image later. Please note this
issue blocks many subsequent issues and I thought we still have enough time for
them right before the merge happening.
> 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)
