[
https://issues.apache.org/jira/browse/HADOOP-2914?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12721778#action_12721778
]
Tom White commented on HADOOP-2914:
-----------------------------------
+1
> My current thinking on APIs (for a future JIRA) is that users should access
> DistributedCache through Job.addToCache(URI, flags) and
> Context.getCachedFiles(). But there's some more work to get there.
I imagine this would be done as a part of moving DistributedCache from the
filecache package to the mapreduce package (or a subpackage, see HADOOP-398).
> extend DistributedCache to work locally (LocalJobRunner)
> --------------------------------------------------------
>
> Key: HADOOP-2914
> URL: https://issues.apache.org/jira/browse/HADOOP-2914
> Project: Hadoop Core
> Issue Type: Improvement
> Components: mapred
> Reporter: sam rash
> Assignee: Philip Zeyliger
> Priority: Minor
> Attachments: HADOOP-2914-v1-full.patch,
> HADOOP-2914-v1-since-4041.patch, HADOOP-2914-v2.patch, HADOOP-2914-v3.patch
>
>
> The DistributedCache does not work locally when using the outlined recipe at
> http://hadoop.apache.org/core/docs/r0.16.0/api/org/apache/hadoop/filecache/DistributedCache.html
>
> Ideally, LocalJobRunner would take care of populating the JobConf and copying
> remote files to the local file sytem (http, assume hdfs = default fs = local
> fs when doing local development.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
