[
https://issues.apache.org/jira/browse/HDFS-8129?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14519230#comment-14519230
]
Uma Maheswara Rao G commented on HDFS-8129:
-------------------------------------------
Actually Nicholas quoted above that, for the classes already inside erasurecode
package, it may be good enough to keep as is ( ECXXX). We can discuss further
if others does not agree on it. That was the reason I did not picked up that
classes into my list before.
> 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
>
> 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)
