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 "Prasad Chakka (JIRA)" <ji...@apache.org> on 2008/08/20 23:00:45 UTC
[jira] Created: (HADOOP-3982) Ability to add libjars through
non-commnad line path
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
-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.
[jira] Commented: (HADOOP-3982) Ability to add libjars through
non-commnad line path
Posted by "Prasad Chakka (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-3982?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12624264#action_12624264 ]
Prasad Chakka commented on HADOOP-3982:
---------------------------------------
Got it. We can work with JobConf itself without touching the libjars or commandLineConfig
> 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.
[jira] Updated: (HADOOP-3982) Ability to add libjars through
non-commnad line path
Posted by "Prasad Chakka (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-3982?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Prasad Chakka updated HADOOP-3982:
----------------------------------
Fix Version/s: 0.19.0
Status: Patch Available (was: Open)
> 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
> 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.
[jira] Commented: (HADOOP-3982) Ability to add libjars through
non-commnad line path
Posted by "Amareshwari Sriramadasu (JIRA)" <ji...@apache.org>.
[ 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.
[jira] Updated: (HADOOP-3982) Ability to add libjars through
non-commnad line path
Posted by "Prasad Chakka (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-3982?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Prasad Chakka updated HADOOP-3982:
----------------------------------
Resolution: Invalid
Release Note: There is a work around that is different from 17 version
Status: Resolved (was: Patch Available)
> 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.
[jira] Commented: (HADOOP-3982) Ability to add libjars through
non-commnad line path
Posted by "Joydeep Sen Sarma (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-3982?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12624257#action_12624257 ]
Joydeep Sen Sarma commented on HADOOP-3982:
-------------------------------------------
Amaresh - can you clarify - is there an objection to providing a public API call that allows addition of jar files to jobclient? If so - why?
Not everything is a Tool. We are embedding the invocation of map-reduce job inside an application. That application may or may not be a tool.
> 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.
[jira] Commented: (HADOOP-3982) Ability to add libjars through
non-commnad line path
Posted by "Amareshwari Sriramadasu (JIRA)" <ji...@apache.org>.
[ 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.
[jira] Assigned: (HADOOP-3982) Ability to add libjars through
non-commnad line path
Posted by "dhruba borthakur (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-3982?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
dhruba borthakur reassigned HADOOP-3982:
----------------------------------------
Assignee: Prasad Chakka
> 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.
[jira] Updated: (HADOOP-3982) Ability to add libjars through
non-commnad line path
Posted by "Prasad Chakka (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-3982?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Prasad Chakka updated HADOOP-3982:
----------------------------------
Attachment: hadoop-trunk.patch
> 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
> 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.