[
https://issues.apache.org/jira/browse/HADOOP-13335?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15363835#comment-15363835
]
Siddharth Seth commented on HADOOP-13335:
-----------------------------------------
bq. There are no HDFS_* vars that change how the client operates. ...
Not yet - until someone feels the need to have hdfs used as a separate command
to do something other than filesystem operations. (Really hope there's no hdfs
jar command)
bq. I'm not sure there is more clarity required. If a user wants/needs YARN_*,
then they need to use 'yarn jar'.
Again - I don't see the difference between hadoop jar and yarn jar other than a
different set of variables being set and respected by the different commands.
Stepping back - should the YARN_* parameters exist?, and should yarn jar exist?
If I understand you correctly, I think you're trying to get rid of some of this.
If 'yarn jar' is something that we think is confusing, or something we
potentially want to get rid off - I'd say it's better to not print any warning
at all - and leave hadoop jar as is?
The hive binary could unset YARN_OPTS / YARN_CLIENT_OPTS - and leave them
intact for the session/shell from where the hive binary was invoked.
That said, the hive jira linked to this one proposes moving to using 'yarn jar'
- and I believe this is mainly because of the WARNING. It would be good for
users / downstream projects to know how this should be handled. Will yarn jar
survive or not.
cc [~vinodkv] since this discussion has quite a bit to do with yarn, and to
potentially get more context on yarn jar and the YARN_* variables.
> Add an option to suppress the 'use yarn jar' warning or remove it
> -----------------------------------------------------------------
>
> Key: HADOOP-13335
> URL: https://issues.apache.org/jira/browse/HADOOP-13335
> Project: Hadoop Common
> Issue Type: Improvement
> Affects Versions: 2.7.0
> Reporter: Siddharth Seth
> Assignee: Siddharth Seth
> Attachments: HADOOP-13335.01.patch, HADOOP-13335.02.patch,
> HADOOP-13335.02_branch-2.patch, HADOOP-13335.03.patch,
> HADOOP-13335.03_branch-2.patch, HADOOP-13335.04.patch
>
>
> https://issues.apache.org/jira/browse/HADOOP-11257 added a 'deprecation'
> warning for 'hadoop jar'.
> hadoop jar is used for a lot more that starting jobs. As an example - hive
> uses it to start all it's services (HiveServer2, the hive client, beeline
> etc).
> Using 'yarn jar' for to start these services / tools doesn't make a lot of
> sense - there's no relation to yarn other than requiring the classpath to
> include yarn libraries.
> I'd propose reverting the changes where this message is printed if YARN
> variables are set (leave it in the help message), or adding a mechanism which
> would allow users to suppress this WARNING.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
