You are viewing a plain text version of this content. The canonical link for it is here.
Posted to hdfs-issues@hadoop.apache.org by "Allen Wittenauer (JIRA)" <ji...@apache.org> on 2014/07/17 23:26:04 UTC
[jira] [Commented] (HDFS-2364) metaSave API is using Printwriter,
It will eat all the IOExceptions.
[ https://issues.apache.org/jira/browse/HDFS-2364?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14065576#comment-14065576 ]
Allen Wittenauer commented on HDFS-2364:
----------------------------------------
Ping!
> metaSave API is using Printwriter, It will eat all the IOExceptions.
> --------------------------------------------------------------------
>
> Key: HDFS-2364
> URL: https://issues.apache.org/jira/browse/HDFS-2364
> Project: Hadoop HDFS
> Issue Type: Sub-task
> Components: namenode
> Reporter: Uma Maheswara Rao G
> Assignee: Uma Maheswara Rao G
>
> It is important to note that
> PrintStream and PrintWriter do not throw IOExceptions! IOException is a
> non-Runtime exception, which means that your code must catch them or declare it
> can throw them.
> The creators of Java realized that System.out and System.err would be very
> heavily used, and did not want to force inclusion of exception handling every time
> you wanted to write System.out.println(4).
> Therefore, PrintStream and PrintWriter catch their own exceptions and set an
> error flag. If you are using one of these classes for real output in your program
> (not merely using System.out.println()) you should call checkError() to see
> if an error has occurred.
> Because of this behavior, PrintStream and PrintWriter are not well suited for
> use other than System.out and System.err!
> Ref: http://www.cs.usfca.edu/~parrt/doc/java/JavaIO-notes.pdf
--
This message was sent by Atlassian JIRA
(v6.2#6252)