[ https://issues.apache.org/jira/browse/HADOOP-7487?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13587083#comment-13587083 ]
Hudson commented on HADOOP-7487: -------------------------------- Integrated in Hadoop-Hdfs-trunk #1328 (See [https://builds.apache.org/job/Hadoop-Hdfs-trunk/1328/]) HADOOP-7487. DF should throw a more reasonable exception when mount cannot be determined. Contributed by Andrew Wang. (Revision 1449992) Result = FAILURE atm : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1449992 Files : * /hadoop/common/trunk/hadoop-common-project/hadoop-common/CHANGES.txt * /hadoop/common/trunk/hadoop-common-project/hadoop-common/src/main/java/org/apache/hadoop/fs/DF.java * /hadoop/common/trunk/hadoop-common-project/hadoop-common/src/test/java/org/apache/hadoop/fs/TestDFVariations.java > DF should throw a more reasonable exception when mount cannot be determined > --------------------------------------------------------------------------- > > Key: HADOOP-7487 > URL: https://issues.apache.org/jira/browse/HADOOP-7487 > Project: Hadoop Common > Issue Type: Bug > Components: fs > Affects Versions: 0.23.0, 3.0.0, 2.0.3-alpha > Reporter: Todd Lipcon > Assignee: Andrew Wang > Labels: noob > Fix For: 2.0.4-beta > > Attachments: hadoop-7487-1.patch, hadoop-7487-2.patch, > hadoop-7487-3.patch > > > Currently, when using the DF class to determine the mount corresponding to a > given directory, it will throw the generic exception "Expecting a line not > the end of stream" if it can't determine the mount (for example if the > directory doesn't exist). > This error message should be improved in several ways: > # If the dir to check doesn't exist, we can see that before even execing df, > and throw a better exception (or behave better by chopping path components > until it exists) > # Rather than parsing the lines out of df's stdout, collect the whole output, > and then parse. So, if df returns a non-zero exit code, we can avoid trying > to parse the empty result > # If there's a success exit code, and we still can't parse it (eg > incompatible OS), we should include the unparseable line in the exception > message. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira