[
https://issues.apache.org/jira/browse/HADOOP-7575?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13105691#comment-13105691
]
Jonathan Eagles commented on HADOOP-7575:
-----------------------------------------
Thanks for the quick feedback Sid.
Hope this can help clear things up.
You are right in that it is not strictly required. However, I added the
FILENAME to limit the interactions between the three runs of each test. With
the change, each test will be run for RELATIVE, ABSOLUTE, and QUALIFIED paths.
When a test failure occurs, I was hoping this would help debugging to
understand which of the test runs is actually having the failure.
Here is an example of the directories created from running test0
build/test/temp/tmp1/RELATIVE4479762554581247692.tmp
/hadoop/trunk/hadoop-common-project/hadoop-common/build/test/temp/tmp1/ABSOLUTE5682530493698547015.tmp
/hadoop/trunk/hadoop-common-project/hadoop-common/build/test/temp/tmp1/QUALIFIED8300568269421645153.tmp
Previously RELATIVE was always set to block, so keeping FILENAME changing only
the file name is consistent with the previous behavior. If there is a better
way I am very much open to ideas here.
> Support fully qualified paths as part of LocalDirAllocator
> ----------------------------------------------------------
>
> Key: HADOOP-7575
> URL: https://issues.apache.org/jira/browse/HADOOP-7575
> Project: Hadoop Common
> Issue Type: Bug
> Components: fs
> Affects Versions: 0.23.0
> Reporter: Jonathan Eagles
> Assignee: Jonathan Eagles
> Priority: Minor
> Fix For: 0.23.0
>
> Attachments: HADOOP-7575-trunk-v1.patch, HADOOP-7575-trunk-v3.patch,
> HADOOP-7575-trunk-v4.patch, HADOOP-7575-trunk-v5.patch,
> HADOOP-7575-trunk-v8.patch
>
>
> Contexts with configuration path strings using fully qualified paths (e.g.
> file:///tmp instead of /tmp) mistakenly creates a directory named 'file:' and
> sub-directories in the current local file system working directory.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
