hadoop-common-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Owen O'Malley (JIRA)" <j...@apache.org>
Subject [jira] Updated: (HADOOP-292) hadoop dfs commands should not output superfluous data to stdout
Date Fri, 09 Jun 2006 02:14:30 GMT
     [ http://issues.apache.org/jira/browse/HADOOP-292?page=all ]

Owen O'Malley updated HADOOP-292:
---------------------------------

    Attachment: stderr-log.patch

This patch renames the "stdout" log4j appender to "console" and sends the log events to stderr
instead of stdout. This _partially_ fixes Yoram's problem.

> hadoop dfs commands should not output superfluous data to stdout
> ----------------------------------------------------------------
>
>          Key: HADOOP-292
>          URL: http://issues.apache.org/jira/browse/HADOOP-292
>      Project: Hadoop
>         Type: Bug

>   Components: dfs
>     Reporter: Yoram Arnon
>     Priority: Minor
>  Attachments: stderr-log.patch
>
> running a command such as hadoop dfs -ls /data
> produces output such as the following:
> 06/06/08 17:42:32 INFO conf.Configuration: parsing jar:file: /hadoop/hadoop-0.4-dev/hadoop-0.4-dev.jar!/hadoop-default.xml
> 06/06/08 17:42:32 INFO conf.Configuration: parsing file:hadoop/hadoop-site.xml
> 06/06/08 17:42:32 INFO dfs.DistributedFileSystem: No FS indicated, using default:kry1200:8020
> 06/06/08 17:42:32 INFO ipc.Client: Client connection to 172.30.111.134:8020: starting
> Found 2 items
> /data/a <dir>
> /data/b     <dir>
> the first few lines shouldn't be there.
> it's especially annoying when running -cat into a file or into some post processing program,
but in general, the output should be clean.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira


Mime
View raw message