[
https://issues.apache.org/jira/browse/HADOOP-13079?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15269997#comment-15269997
]
Andrew Wang commented on HADOOP-13079:
--------------------------------------
FWIW I think FreeBSD and OpenBSD default to printing "?" rather than the
control character:
http://www.freebsd.org/cgi/man.cgi?ls
http://man.openbsd.org/OpenBSD-current/man1/ls.1
{quote}
-q Force printing of non-graphic characters in file names as the
character `?'; this is the default when output is to a terminal.
{quote}
Allen, do you have some counter-examples where someone coming from a NIXy
background would be confused by -q as default? IIRC OSX uses a FreeBSD
userspace, so it seems like for the majority of Hadoop users, -q is already the
expectation.
John, do you mind setting the target version? If we have compatibility
concerns, maybe this only targets Hadoop 3.
> Add -q to fs -ls to print non-printable characters
> --------------------------------------------------
>
> Key: HADOOP-13079
> URL: https://issues.apache.org/jira/browse/HADOOP-13079
> Project: Hadoop Common
> Issue Type: Bug
> Reporter: John Zhuge
> Assignee: John Zhuge
> Labels: supportability
>
> Add option {{-q}} to "hdfs dfs -ls" to print non-printable characters as "?".
> Non-printable characters are defined by
> [isprint(3)|http://linux.die.net/man/3/isprint] according to the current
> locale.
> Default to {{-q}} behavior on terminal; otherwise, print raw characters. See
> the difference in these 2 command lines:
> * {{hadoop fs -ls /dir}}
> * {{hadoop fs -ls /dir | od -c}}
> In C, {{isatty(STDOUT_FILENO)}} is used to find out whether the output is a
> terminal. Since Java doesn't have {{isatty}}, I will use JNI to call C
> {{isatty()}} because the closest test {{System.console() == null}} does not
> work in some cases.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]