hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Kai Sasaki (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (HDFS-10021) CLONE - Erasure Coding: Maintain consistent naming for Erasure Coding related classes - EC/ErasureCoding
Date Tue, 15 Mar 2016 09:09:34 GMT

     [ https://issues.apache.org/jira/browse/HDFS-10021?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Kai Sasaki resolved HDFS-10021.
-------------------------------
    Resolution: Invalid

> CLONE - Erasure Coding: Maintain consistent naming for Erasure Coding related classes
- EC/ErasureCoding
> --------------------------------------------------------------------------------------------------------
>
>                 Key: HDFS-10021
>                 URL: https://issues.apache.org/jira/browse/HDFS-10021
>             Project: Hadoop HDFS
>          Issue Type: Sub-task
>            Reporter: dragon
>            Assignee: Uma Maheswara Rao G
>            Priority: Minor
>             Fix For: HDFS-7285
>
>
> 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)

Mime
View raw message