You are viewing a plain text version of this content. The canonical link for it is here.

Posted to common-dev@hadoop.apache.org by "Amareshwari Sriramadasu (JIRA)" <ji...@apache.org> on 2008/08/21 06:40:44 UTC

[jira] Commented: (HADOOP-3982) Ability to add libjars through non-commnad line path

    [ https://issues.apache.org/jira/browse/HADOOP-3982?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12624254#action_12624254 ] 

Amareshwari Sriramadasu commented on HADOOP-3982:
-------------------------------------------------

>From 0.18, -libjars is available for applications implementing Tool.  And using the static commandLineConfig is deprecated in 0.18. So, it will be removed in 0.19. Applications have to implement Tool to use -libjars from 0.19. HADOOP-3417 and HADOOP-3743 brought this behavior.

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