hadoop-common-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Junping Du (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HADOOP-9447) Configuration to include name of failing file/resource when wrapping an XML parser exception
Date Fri, 07 Jun 2013 09:44:20 GMT

    [ https://issues.apache.org/jira/browse/HADOOP-9447?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13677925#comment-13677925
] 

Junping Du commented on HADOOP-9447:
------------------------------------

That's a good point for this case. Sorry. I just thought the re-usability before, but haven't
found place to reuse it. Trouble-shooting is also not a good reason for this case. Luke, do
you buy in this reason? :)
btw, I would more concern on swallowing exceptions as showing in fix of 2.1. In most cases,
RuntimeException shouldn't be just logged (without re-throwing it) as it should stands for
serious and un-recoverable issue. Isn't it?  
                
> Configuration to include name of failing file/resource when wrapping an XML parser exception
> --------------------------------------------------------------------------------------------
>
>                 Key: HADOOP-9447
>                 URL: https://issues.apache.org/jira/browse/HADOOP-9447
>             Project: Hadoop Common
>          Issue Type: Improvement
>          Components: conf
>    Affects Versions: 3.0.0
>            Reporter: Steve Loughran
>            Priority: Trivial
>         Attachments: HADOOP-9447-2.patch, HADOOP-9447.patch, HADOOP-9447-v2.1.patch,
HADOOP-9447-v3.patch, HADOOP-9447-v4.patch
>
>
> Currently, when there is an error parsing an XML file, the name of the file at fault
is logged, but not included in the (wrapped) XML exception. If that same file/resource name
were included in the text of the wrapped exception, people would be able to find out which
file was causing problems

--
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

Mime
View raw message