[
https://issues.apache.org/jira/browse/MAPREDUCE-1641?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12858057#action_12858057
]
Dick King commented on MAPREDUCE-1641:
--------------------------------------
We will _not_ allow this file duplication as proposed in 16/Apr/10 11:41AM.
However, we will not throw an {{IllegalArgumentException}} . We will throw an
{{InvalidJobconfException}} instead. A consequence of this is that the check
cannot be performed as you add individual files or blocks of files to the
cache; the interface is wrong. We perform the check for conflicts between
{{mapred.cache.files}} and {{mapred.cache.archives}} when the user finally
submits the offending {{JobConf}} .
In particular, I plan to make a new class {{DistributedCache.DuplicatedURI
extends InvalidJobConfException}} and throw _that_ .
> Job submission should fail if same uri is added for mapred.cache.files and
> mapred.cache.archives
> ------------------------------------------------------------------------------------------------
>
> Key: MAPREDUCE-1641
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-1641
> Project: Hadoop Map/Reduce
> Issue Type: Bug
> Components: distributed-cache
> Reporter: Amareshwari Sriramadasu
> Assignee: Dick King
> Fix For: 0.22.0
>
>
> The behavior of mapred.cache.files and mapred.cache.archives is different
> during localization in the following way:
> If a jar file is added to mapred.cache.files, it will be localized under
> TaskTracker under a unique path.
> If a jar file is added to mapred.cache.archives, it will be localized under a
> unique path in a directory named the jar file name, and will be unarchived
> under the same directory.
> If same jar file is passed for both the configurations, the behavior
> undefined. Thus the job submission should fail.
> Currently, since distributed cache processes files before archives, the jar
> file will be just localized and not unarchived.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
