[
https://issues.apache.org/jira/browse/HADOOP-13335?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15363161#comment-15363161
]
Siddharth Seth commented on HADOOP-13335:
-----------------------------------------
bq. But hive doesn't call yarn, it uses hadoop. hadoop does not import
yarn-config.sh, which is where yarn configuration parameters are expected to be
located. YARN_USER_CLASSPATH is not handled or likely defined at all. So none
of those settings will be defined.
Hive does not use 'yarn' at the moment (and hopefully will not need to). The
problem comes in when YARN_CLIENT_OPTS / YARN_OPTS are defined on a shell where
hive is invoked (for beeline / the cli for example). That ends up displaying
the 'use yarn jar' message which is confusing.
> 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
> Attachments: HADOOP-13335.01.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]
