[
https://issues.apache.org/jira/browse/HADOOP-13335?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15365652#comment-15365652
]
Siddharth Seth commented on HADOOP-13335:
-----------------------------------------
bq. There have been a ton of removals all over the place in trunk already. S3,
hftp, ... lots and lots of places. Bear in mind that the last opportunity
Hadoop had to remove content was over five years ago.
Good to know.
bq. Once again: they do not. I'm not sure how many more and different ways I
can state this point. The rest of that discussion is pretty much moot since the
first opportunity to make them function the same will be 4.x, easily years off.
And once again - the only difference is the additional YARN_* environment
variables added on. You seem to agree that having these additional variables is
unnecessary and confusing, and they should eventually be removed (maybe in
4.x). If the intent is to deprecate the (yarn jar) command - I don't see the
point of pointing users towards this when they invoke hadoop jar.
Another way of looking at this: if someone has set the YARN_* options - they
would do this intentionally, and would be aware of the yarn jar command. If
they use hadoop jar after this point for something else - they know exactly
what they're doing, and hadoop should not try pointing them back at yarn jar.
bq. yarn-config.sh and hadoop-config.sh in a way that should be mostly
conflict-free
Right there is another problem. "Mostly conflict-free" is not a great API, and
adds more confusion.
bq. Deprecation warnings have always been added to the output throughout the
history of Hadoop. Expect a lot more to show up in trunk.
Is this particular case supposed to be a deprecation warning ?
Most system will also have a mechanism to suppress deprecation messages; we
should add such an option to the scripts in trunk.
Is there some place that the public API for the hadoop scripts is documented ?
The only place I have seen references along with documentation is within the
scripts itself, and in 'usage' output.
> 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: common-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: common-issues-h...@hadoop.apache.org
