[
https://issues.apache.org/jira/browse/HDFS-4720?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13637526#comment-13637526
]
Yu Li commented on HDFS-4720:
-----------------------------
Here is the result of test-patch in sun jdk 1.6u21:
======================================
{color:red}-1 overall{color}.
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:red}-1 tests included{color}. The patch doesn't appear to include
any new or modified tests.
Please justify why no new tests are needed for this
patch.
Also please list what manual steps were performed to
verify this patch.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 javadoc{color}. The javadoc tool did not generate any
warning messages.
{color:green}+1 eclipse:eclipse{color}. The patch built with
eclipse:eclipse.
{color:green}+1 findbugs{color}. The patch does not introduce any new
Findbugs (version 2.0.1) warnings.
{color:red}-1 release audit{color}. The applied patch generated 1280
release audit warnings.
======================================
Existing test cases like TestJsonUtil and TestWebHDFS already covered the case,
so no need to supply more test cases.
> Misleading warning message in WebhdfsFileSystem when trying to check whether
> path exist using webhdfs url
> ---------------------------------------------------------------------------------------------------------
>
> Key: HDFS-4720
> URL: https://issues.apache.org/jira/browse/HDFS-4720
> Project: Hadoop HDFS
> Issue Type: Bug
> Components: webhdfs
> Affects Versions: 1.1.1, 1.1.2
> Reporter: Yu Li
> Assignee: Yu Li
> Priority: Minor
> Attachments: HDFS-4720-trunk.patch
>
>
> When we trying to check whether the target path exists in HDFS through
> webhdfs, if the given path to check doesn't exist, we will always observe
> warning message like:
> ===========================================================
> 13/04/21 04:38:01 WARN web.WebHdfsFileSystem: Original exception is
> org.apache.hadoop.ipc.RemoteException: user = biadmin, proxyUser = null, path
> = /testWebhdfs
> at
> org.apache.hadoop.hdfs.web.JsonUtil.toRemoteException(JsonUtil.java:114)
> at
> org.apache.hadoop.hdfs.web.WebHdfsFileSystem.validateResponse(WebHdfsFileSystem.java:294)
> at
> org.apache.hadoop.hdfs.web.WebHdfsFileSystem.access$500(WebHdfsFileSystem.java:103)
> at
> org.apache.hadoop.hdfs.web.WebHdfsFileSystem$Runner.getResponse(WebHdfsFileSystem.java:552)
> at
> org.apache.hadoop.hdfs.web.WebHdfsFileSystem$Runner.run(WebHdfsFileSystem.java:473)
> at
> org.apache.hadoop.hdfs.web.WebHdfsFileSystem.run(WebHdfsFileSystem.java:404)
> at
> org.apache.hadoop.hdfs.web.WebHdfsFileSystem.getHdfsFileStatus(WebHdfsFileSystem.java:573)
> at
> org.apache.hadoop.hdfs.web.WebHdfsFileSystem.getFileStatus(WebHdfsFileSystem.java:584)
> at org.apache.hadoop.fs.FileSystem.exists(FileSystem.java:768)
> ===========================================================
> while actually FileNotFoundException should be expected when the operation is
> GETFILESTATUS and target path doesn't exist. The fact that RemoteException
> didn't include the real exception class(FileNotFoundException) in its
> toString method even make the message more misleading, since from the message
> user won't know what the warning is about
--
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
