[
https://issues.apache.org/jira/browse/HADOOP-13595?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16111150#comment-16111150
]
Allen Wittenauer edited comment on HADOOP-13595 at 8/2/17 4:00 PM:
-------------------------------------------------------------------
Argh. Actually, it's not getting reset because there is no fork, built-in being
called (see the column printer code), and the $() call doesn't count. I should
add that to the unit test.
It kind of sucks that IFS getting set like this is situational. :(
was (Author: aw):
Argh. Actually, it's not getting reset because there is no fork, built-in being
called (see the column printer code), and the $() call doesn't count. I should
add that to the unit test.
> Rework hadoop_usage to be broken up by clients/daemons/etc.
> -----------------------------------------------------------
>
> Key: HADOOP-13595
> URL: https://issues.apache.org/jira/browse/HADOOP-13595
> Project: Hadoop Common
> Issue Type: Improvement
> Components: scripts
> Affects Versions: 3.0.0-alpha2
> Reporter: Allen Wittenauer
> Assignee: Allen Wittenauer
> Priority: Blocker
> Attachments: HADOOP-13595.00.patch, HADOOP-13595.01.patch,
> HADOOP-13595.02.patch, HADOOP-13595.03.patch, HADOOP-13595.04.patch,
> HADOOP-13595.05.patch
>
>
> Part of the feedback from HADOOP-13341 was that it wasn't obvious what was a
> client and what was a daemon. Reworking the hadoop_usage output so that it
> is obvious helps fix this issue.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
---------------------------------------------------------------------
To unsubscribe, e-mail: common-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: common-issues-h...@hadoop.apache.org
