[
https://issues.apache.org/jira/browse/HADOOP-8437?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13462682#comment-13462682
]
Harsh J commented on HADOOP-8437:
---------------------------------
Ok so its cause of my earlier comment:
{code}
+ for (int i = 0; i < 256; i++) {
+ invalidPath.append("A");
+ }
{code}
This creates a condition where the filename request is > max allowed filename
length on some FS-es. Since thats not a nice way to do it (it may begin
'passing' on some FSes), lets instead play with permissions or something?
> getLocalPathForWrite is not throwing any expection for invalid paths
> --------------------------------------------------------------------
>
> Key: HADOOP-8437
> URL: https://issues.apache.org/jira/browse/HADOOP-8437
> Project: Hadoop Common
> Issue Type: Bug
> Components: fs
> Affects Versions: 2.0.0-alpha
> Reporter: Brahma Reddy Battula
> Assignee: Brahma Reddy Battula
> Attachments: HADOOP-8437_1.patch, HADOOP-8437.patch
>
>
> call dirAllocator.getLocalPathForWrite ( "/InvalidPath", conf );
> Here it will not thrown any exception but earlier version it used throw.
--
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
