[
https://issues.apache.org/jira/browse/HADOOP-3982?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12624263#action_12624263
]
Amareshwari Sriramadasu commented on HADOOP-3982:
-------------------------------------------------
https://issues.apache.org/jira/browse/HADOOP-3743?focusedCommentId=12613250#action_12613250
says that GenericOptionsParser is the proper place to add options. Since the
static configuration will get removed after sometime, is it required to be
public now?
Till the time user apps are moved to implementing Tool, users could set the
values for the options tmpfiles, tmparchives and tmpjars in the configuration
they use to submit jobs (that's what the three arguments, -files, -archives and
-jars, do).
Thoughts?
> Ability to add libjars through non-commnad line path
> -----------------------------------------------------
>
> Key: HADOOP-3982
> URL: https://issues.apache.org/jira/browse/HADOOP-3982
> Project: Hadoop Core
> Issue Type: Improvement
> Affects Versions: 0.17.2
> Reporter: Prasad Chakka
> Assignee: Prasad Chakka
> Fix For: 0.19.0
>
> Attachments: hadoop-trunk.patch
>
>
> -libjars options is available only if the job has been submitted through
> JobShell class. Since the function 'setCommnadLineConfig' is a protected
> function, non mapred classes can't take advantage of this functionality. By
> making this function public, other classes that submit jobs can utilize this
> functionality.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
