Mailing-List: contact common-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: common-issues@hadoop.apache.org
Date: Mon, 1 Apr 2013 21:43:16 +0000 (UTC)
From: "Steve Loughran (JIRA)" <jira@apache.org>
To: common-issues@hadoop.apache.org
Message-ID: <JIRA.12640122.1364830340857.87607.1364852596091@arcas>
In-Reply-To: <JIRA.12640122.1364830340857@arcas>
References: <JIRA.12640122.1364830340857@arcas>
Subject: [jira] [Updated] (HADOOP-9447) Configuration to include name of
 failing file/resource when wrapping an XML parser exception
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


     [ https://issues.apache.org/jira/browse/HADOOP-9447?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Steve Loughran updated HADOOP-9447:
-----------------------------------

    Status: Open  (was: Patch Available)
    
> 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.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