You are viewing a plain text version of this content. The canonical link for it is here.
Posted to common-issues@hadoop.apache.org by "Alejandro Abdelnur (JIRA)" <ji...@apache.org> on 2012/05/02 20:30:52 UTC
[jira] [Commented] (HADOOP-8214) make hadoop script recognize a
full set of deprecated commands
[ https://issues.apache.org/jira/browse/HADOOP-8214?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13266794#comment-13266794 ]
Alejandro Abdelnur commented on HADOOP-8214:
--------------------------------------------
+1
> make hadoop script recognize a full set of deprecated commands
> --------------------------------------------------------------
>
> Key: HADOOP-8214
> URL: https://issues.apache.org/jira/browse/HADOOP-8214
> Project: Hadoop Common
> Issue Type: Improvement
> Components: scripts
> Affects Versions: 0.23.1
> Reporter: Roman Shaposhnik
> Assignee: Roman Shaposhnik
> Fix For: 0.23.2
>
> Attachments: HADOOP-8214.patch.txt
>
>
> bin/hadoop launcher script does a nice job of recognizing deprecated usage and vectoring users towards the proper command line tools (hdfs, mapred). It would be nice if we can take care of the following deprecated commands that don't get the same special treatment:
> {noformat}
> oiv apply the offline fsimage viewer to an fsimage
> dfsgroups get the groups which users belong to on the Name Node
> mrgroups get the groups which users belong to on the Job Tracker
> mradmin run a Map-Reduce admin client
> jobtracker run the MapReduce job Tracker node
> tasktracker run a MapReduce task Tracker node
> {noformat}
> Here's what I propos to do with them:
> # oiv -- issue DEPRECATED warning and run hdfs oiv
> # dfsgroups -- issue DEPRECATED warning and run hdfs groups
> # mrgroups -- issue DEPRECATED warning and run mapred groups
> # mradmin -- issue DEPRECATED warning and run yarn rmadmin
> # jobtracker -- issue DEPRECATED warning and do nothing
> # tasktracker-- issue DEPRECATED warning and do nothing
> Thoughts?
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira