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 "Tsz Wo Nicholas Sze (JIRA)" <ji...@apache.org> on 2015/04/17 22:22:59 UTC
[jira] [Commented] (HDFS-8129) Maintain consistent naming for
Erasure Coding related classes - EC/ErasureCode
[ https://issues.apache.org/jira/browse/HDFS-8129?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14500592#comment-14500592 ]
Tsz Wo Nicholas Sze commented on HDFS-8129:
-------------------------------------------
ErasureCoding* sounds good. For the classes are already in the erasurecode package, EcXxx is good enough.
> Maintain consistent naming for Erasure Coding related classes - EC/ErasureCode
> ------------------------------------------------------------------------------
>
> 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)