Apache
/
hadoop
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

HADOOP-10896. Update compatibility doc to capture visibility of un-annotated classes/ methods. (kasha) 

git-svn-id: https://svn.apache.org/repos/asf/hadoop/common/branches/branch-2@1613544 13f79535-47bb-0310-9956-ffa450edef68
This commit is contained in:
Karthik Kambatla 2014-07-26 00:49:12 +00:00
parent c039bccb92
commit 775897ee02
2 changed files with 9 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

3
hadoop-common-project/hadoop-common/CHANGES.txt
View File

@ -212,6 +212,9 @@ Release 2.5.0 - UNRELEASED
HADOOP-10782. Fix typo in DataChecksum class. (Jingguo Yao via suresh) HADOOP-10782. Fix typo in DataChecksum class. (Jingguo Yao via suresh)
HADOOP-10896. Update compatibility doc to capture visibility of
un-annotated classes/ methods. (kasha)
OPTIMIZATIONS OPTIMIZATIONS
HADOOP-10674. Improve PureJavaCrc32 performance and use java.util.zip.CRC32 HADOOP-10674. Improve PureJavaCrc32 performance and use java.util.zip.CRC32

9
hadoop-common-project/hadoop-common/src/site/apt/Compatibility.apt.vm
View File

@ -72,10 +72,13 @@ Apache Hadoop Compatibility
* Private-Stable APIs can change across major releases, * Private-Stable APIs can change across major releases,
but not within a major release. but not within a major release.
* Classes not annotated are implicitly "Private". Class members not
annotated inherit the annotations of the enclosing class.
* Note: APIs generated from the proto files need to be compatible for * Note: APIs generated from the proto files need to be compatible for
rolling-upgrades. See the section on wire-compatibility for more details. The rolling-upgrades. See the section on wire-compatibility for more details.
compatibility policies for APIs and wire-communication need to go The compatibility policies for APIs and wire-communication need to go
hand-in-hand to address this. hand-in-hand to address this.
** Semantic compatibility ** Semantic compatibility