Mailing-List: contact hdfs-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: hdfs-issues@hadoop.apache.org
Date: Sat, 11 Apr 2015 04:33:13 +0000 (UTC)
From: "Uma Maheswara Rao G (JIRA)" <jira@apache.org>
To: hdfs-issues@hadoop.apache.org
Message-ID: <JIRA.12820272.1428726771000.62014.1428726793055@Atlassian.JIRA>
In-Reply-To: <JIRA.12820272.1428726771000@Atlassian.JIRA>
References: <JIRA.12820272.1428726771000@Atlassian.JIRA>
 <JIRA.12820272.1428726771732@arcas>
Subject: [jira] [Created] (HDFS-8129) Maintain consistent naming for Erasure
 Coding related classes - EC/EarasureCode
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

Uma Maheswara Rao G created HDFS-8129:
-----------------------------------------

             Summary: Maintain consistent naming for Erasure Coding related classes - EC/EarasureCode
                 Key: HDFS-8129
                 URL: https://issues.apache.org/jira/browse/HDFS-8129
             Project: Hadoop HDFS
          Issue Type: Sub-task
            Reporter: 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)