[
https://issues.apache.org/jira/browse/MAPREDUCE-1623?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tom White updated MAPREDUCE-1623:
---------------------------------
Attachment: MAPREDUCE-1623.patch
New patch which
* Leaves o.a.h.mapreduce.jobhistory as Private Unstable.
* Makes o.a.h.util Private.
* Makes mapreduce.filecache Private and moves the DistributedCache class
javadoc back to o.a.h.filecache.DistributedCache. In doing this I noticed that
the methods for o.a.h.filecache.DistributedCache have no javadoc, since they
are inherited from o.a.h.mapreduce.filecache.DistributedCache which is now
Private. I suggest sorting out the DistributedCache migration path in another
JIRA, since this one is pretty unwieldly already.
* Makes the mapreduce.lib packages Evolving.
> Apply audience and stability annotations to classes in mapred package
> ---------------------------------------------------------------------
>
> Key: MAPREDUCE-1623
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-1623
> Project: Hadoop Map/Reduce
> Issue Type: Sub-task
> Components: documentation
> Reporter: Tom White
> Assignee: Tom White
> Attachments: M1623-1.patch, MAPREDUCE-1623.patch,
> MAPREDUCE-1623.patch, MAPREDUCE-1623.patch, MAPREDUCE-1623.patch,
> MAPREDUCE-1623.patch
>
>
> There are lots of implementation classes in org.apache.hadoop.mapred which
> makes it difficult to see the user-level MapReduce API classes in the
> Javadoc. (See
> http://hadoop.apache.org/common/docs/r0.20.2/api/org/apache/hadoop/mapred/package-summary.html
> for example.) By marking these implementation classes with the
> InterfaceAudience.Private annotation we can exclude them from user Javadoc
> (using HADOOP-6658).
> Later work will move the implementation classes into o.a.h.mapreduce.server
> and related packages (see MAPREDUCE-561), but applying the annotations is a
> good first step.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
