[
https://issues.apache.org/jira/browse/HDFS-8129?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Uma Maheswara Rao G resolved HDFS-8129.
---------------------------------------
Resolution: Fixed
Fix Version/s: HDFS-7285
Hadoop Flags: Reviewed
Committed to branch!
> Erasure Coding: Maintain consistent naming for Erasure Coding related classes
> - EC/ErasureCoding
> ------------------------------------------------------------------------------------------------
>
> Key: HDFS-8129
> URL: https://issues.apache.org/jira/browse/HDFS-8129
> Project: Hadoop HDFS
> Issue Type: Sub-task
> Reporter: Uma Maheswara Rao G
> Assignee: Uma Maheswara Rao G
> Priority: Minor
> Fix For: HDFS-7285
>
> Attachments: HDFS-8129-0.patch, HDFS-8129-1.patch
>
>
> Currently I see some classes named as ErasureCode* and some are with EC*
> I feel we should maintain consistent naming across project. This jira to
> correct the places where we named differently to be a unique.
> And also to discuss which naming we can follow from now onwards when we
> create new classes.
> ErasureCoding* should be fine IMO. Lets discuss what others feel.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
