[
https://issues.apache.org/jira/browse/HADOOP-9582?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13671683#comment-13671683
]
Jason Lowe commented on HADOOP-9582:
------------------------------------
This would solve the problem for "hadoop fs" but since -conf is a
GenericOptionsParser thing, it doesn't address the many other places where
-conf could be specified and processed by GenericOptionsParser. Is the real
fix in a more central location like GenericOptionsParser or Configuration? If
we just target FsShell then we'll have to address this behavior in many places
and open the door to inconsistencies with missing configuration files based on
who's using GenericOptionsParser.
> 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, 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
