You are viewing a plain text version of this content. The canonical link for it is here.
Posted to hdfs-issues@hadoop.apache.org by "Vinayakumar B (JIRA)" <ji...@apache.org> on 2015/04/15 08:41:59 UTC
[jira] [Resolved] (HDFS-8123) Erasure Coding: Better to move EC
related proto messages to a separate erasurecoding proto file
[ https://issues.apache.org/jira/browse/HDFS-8123?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Vinayakumar B resolved HDFS-8123.
---------------------------------
Resolution: Fixed
Fix Version/s: HDFS-7285
Hadoop Flags: Reviewed
committed to branch
Thanks [~rakeshr] for the contribution.
Thanks [~drankye] for the review.
> Erasure Coding: Better to move EC related proto messages to a separate erasurecoding proto file
> -----------------------------------------------------------------------------------------------
>
> Key: HDFS-8123
> URL: https://issues.apache.org/jira/browse/HDFS-8123
> Project: Hadoop HDFS
> Issue Type: Sub-task
> Reporter: Rakesh R
> Assignee: Rakesh R
> Fix For: HDFS-7285
>
> Attachments: HDFS-8123-001.patch, HDFS-8123-002.patch, HDFS-8123-003.patch, HDFS-8123-004.patch, HDFS-8123-005.patch
>
>
> While reviewing the code I've noticed EC related proto messages are getting added into {{hdfs.proto}}. IMHO, for better maintainability of the erasure code feature, its good to move this to a separate {{erasurecode.proto}} file.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)