[
https://issues.apache.org/jira/browse/HADOOP-3003?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12579869#action_12579869
]
Hadoop QA commented on HADOOP-3003:
-----------------------------------
-1 overall. Here are the results of testing the latest attachment
http://issues.apache.org/jira/secure/attachment/12377835/3003_20080313.patch
against trunk revision 619744.
@author +1. The patch does not contain any @author tags.
tests included +1. The patch appears to include 6 new or modified tests.
javadoc +1. The javadoc tool did not generate any warning messages.
javac +1. The applied patch does not generate any new javac compiler
warnings.
release audit +1. The applied patch does not generate any new release
audit warnings.
findbugs +1. The patch does not introduce any new Findbugs warnings.
core tests -1. The patch failed core unit tests.
contrib tests -1. The patch failed contrib unit tests.
Test results:
http://hudson.zones.apache.org/hudson/job/Hadoop-Patch/1985/testReport/
Findbugs warnings:
http://hudson.zones.apache.org/hudson/job/Hadoop-Patch/1985/artifact/trunk/build/test/findbugs/newPatchFindbugsWarnings.html
Checkstyle results:
http://hudson.zones.apache.org/hudson/job/Hadoop-Patch/1985/artifact/trunk/build/test/checkstyle-errors.html
Console output:
http://hudson.zones.apache.org/hudson/job/Hadoop-Patch/1985/console
This message is automatically generated.
> FileSystem cache key should be updated after a FileSystem object is created
> ---------------------------------------------------------------------------
>
> Key: HADOOP-3003
> URL: https://issues.apache.org/jira/browse/HADOOP-3003
> Project: Hadoop Core
> Issue Type: Bug
> Components: fs
> Affects Versions: 0.16.2, 0.17.0
> Reporter: Tsz Wo (Nicholas), SZE
> Assignee: Tsz Wo (Nicholas), SZE
> Fix For: 0.16.2, 0.17.0
>
> Attachments: 3003_20080311.patch, 3003_20080313.patch
>
>
> In FileSystem.get(uri, conf), it first creates a cache key from the uri and
> the conf and then lookups the corresponding FileSystem object in the cache.
> If the object is not found, it initializes a FileSystem object and put it to
> the cache with the key. However, during FileSystem creation, the conf might
> be modified. In such case, the key should be updated before putting it to
> the cache.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
