[
https://issues.apache.org/jira/browse/HADOOP-9582?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13664341#comment-13664341
]
Steve Loughran commented on HADOOP-9582:
----------------------------------------
My current (YARN-117) fork of Hadoop trunk has an extra test in Configuration
-it doesn't load empty files. This is the patch from HADOOP-9453, adding a
{{file.length() > 0}} to the criteria, and stopping the XML parser failing on
an empty file.
Should your -conf code reject empty files too? Today that triggers the XML
parser failure -it's hard to see why we'd want to permit it once HADOOP-9453
gets checked in
> Non-existent file to "hadoop fs -conf" doesn't throw error
> ----------------------------------------------------------
>
> Key: HADOOP-9582
> URL: https://issues.apache.org/jira/browse/HADOOP-9582
> Project: Hadoop Common
> Issue Type: Bug
> Components: conf
> Affects Versions: 3.0.0, 0.23.7, 2.0.4-alpha
> Reporter: Ashwin Shankar
> Attachments: HADOOP-9582.txt, HADOOP-9582.txt
>
>
> When we run :
> hadoop fs -conf BAD_FILE -ls /
> we expect hadoop to throw an error,but it doesn't.
--
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
