You are viewing a plain text version of this content. The canonical link for it is here.
Posted to mapreduce-issues@hadoop.apache.org by "Alejandro Abdelnur (Commented) (JIRA)" <ji...@apache.org> on 2011/12/16 02:17:31 UTC
[jira] [Commented] (MAPREDUCE-950) Clean up unsymmetrical Job-API
w.r.t DistributedCache
[ https://issues.apache.org/jira/browse/MAPREDUCE-950?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13170659#comment-13170659 ]
Alejandro Abdelnur commented on MAPREDUCE-950:
----------------------------------------------
Can we get MAPREDUCE-1744 in 0.23 as a stop-gap until MAPREDUCE-950 takes care in a more comprehensive way? OOZIE-638 requires this, else Oozie has edge failures when interacting with a cluster with security ON, depending on what HDFS operation was performed first (and if a FS handle is available in the cache)
> Clean up unsymmetrical Job-API w.r.t DistributedCache
> -----------------------------------------------------
>
> Key: MAPREDUCE-950
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-950
> Project: Hadoop Map/Reduce
> Issue Type: Bug
> Components: distributed-cache
> Reporter: Vinod Kumar Vavilapalli
> Priority: Critical
> Fix For: 0.23.1
>
>
> MAPREDUCE-898 cleans up user facing APIs in DistributedCache by adding them to Job/JobContext. There are still some unsymmetric APIs. For e.g. getArchiveClassPaths() return Path objects while the corresponding setter API addCacheArchive() adds a URI. Same is the case with a missing setArchivesToClassPath()/setFilesToClassPathj() similar to setCacheArchives().
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira