[ https://issues.apache.org/jira/browse/HBASE-13300?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15763255#comment-15763255 ]
Anoop Sam John commented on HBASE-13300: ---------------------------------------- These are the places where we have timeStamp usage in method names and those are not private interface. (Public exposed or limited public ) org.apache.hadoop.hbase.client.Get.setTimeStamp(long) org.apache.hadoop.hbase.client.Mutation.getTimeStamp() org.apache.hadoop.hbase.client.Scan.setTimeStamp(long) org.apache.hadoop.hbase.coprocessor.BaseRegionObserver.prePrepareTimeStampForDeleteVersion(ObserverContext<RegionCoprocessorEnvironment>, Mutation, Cell, byte[], Get) org.apache.hadoop.hbase.coprocessor.RegionObserver.prePrepareTimeStampForDeleteVersion(ObserverContext<RegionCoprocessorEnvironment>, Mutation, Cell, byte[], Get) org.apache.hadoop.hbase.regionserver.RegionMergeTransaction.getTimeStamp() org.apache.hadoop.hbase.regionserver.RegionmergeTransactionImpl.getTimeStamp() org.apache.hadoop.hbase.regionserver.SplitTransaction.JournalEntry.getTimeStamp() org.apache.hadoop.hbase.regionserver.StoreFile.getModificationTimeStamp() > Fix casing in getTimeStamp() and setTimestamp() for Mutations > ------------------------------------------------------------- > > Key: HBASE-13300 > URL: https://issues.apache.org/jira/browse/HBASE-13300 > Project: HBase > Issue Type: Bug > Components: API > Affects Versions: 1.0.0 > Reporter: Lars George > Assignee: Jan Hentschel > Attachments: HBASE-13300.master.001.patch, > HBASE-13300.master.002.patch, HBASE-13300.xlsx > > > For some reason we have two ways of writing this method. It should be > consistent. -- This message was sent by Atlassian JIRA (v6.3.4#6332)