[ 
https://issues.apache.org/jira/browse/MAPREDUCE-1623?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12860822#action_12860822
 ] 

Amareshwari Sriramadasu commented on MAPREDUCE-1623:
----------------------------------------------------

bq. I'm a bit confused about what happened here. In 0.20 there was only 
o.a.h.filecache.DistributedCache, which was actually in Core. It's been 
deprecated in trunk in favour of o.a.h.filecache.mapreduce.DistributedCache, 
but this has been deprecated too - in favour of methods on Job. 
Let me clear some confusion here. As Tom said,  In 0.20 there was only 
o.a.h.filecache.DistributedCache, which was actually in Core. It's been 
deprecated in trunk in favour of o.a.h.filecache.mapreduce.DistributedCache, 
but this has been deprecated too - in favour of methods on Job. Here, 
o.a.h.mapreduce.filecache is changed to have only framework code and client 
facing apis are moved to Job. 

bq. So, yes, mapreduce.filecache package should be Private, and the deprecation 
message on o.a.h.filecache.DistributedCache should direct users to Job.
+1

bq. It looks like most of the javadoc for mapreduce.filecache can be moved back 
to o.a.h.filecache.DistributedCache.
Chris, the use of new api for distributed cache is documented in forrest. But, 
I think we can move the javadoc for the use of old api to 
o.a.h.filecache.DistributedCache.

> 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
>
>
> 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.

Reply via email to