[
https://issues.apache.org/jira/browse/TIKA-1764?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14946775#comment-14946775
]
Tim Allison commented on TIKA-1764:
-----------------------------------
Ha, I've been wanting to do this for a while.
I'm not sure of the history, but we appear to tend to avoid logging by Tika.
One challenge is that unless we specify an "id" field to grab from the
metadata, it isn't obvious how to link a given exception to a given input
document.
I've found it convenient in the RecursiveParserWrapper to "log" the exception
stack trace in the Metadata object.
Would that work?
> Provide information on failed document parsing in
> ParsingEmbeddedDocumentExtractor
> ----------------------------------------------------------------------------------
>
> Key: TIKA-1764
> URL: https://issues.apache.org/jira/browse/TIKA-1764
> Project: Tika
> Issue Type: Improvement
> Affects Versions: 1.5, 1.10
> Reporter: Odilo Oehmichen
> Original Estimate: 1h
> Remaining Estimate: 1h
>
> The {{ParsingEmbeddedDocumentExtractor}} delegates the parsing of documents
> to a {{Parser}}-instance.
> If this parser fails with a {{TikaException}} the extractor class returns
> silenty:
> {code}
> catch (TikaException e) {
> // TODO: can we log a warning somehow?
> // Could not parse the entry, just skip the content
> }
> {code}
> This behaviour makes it very hard to detect problems concerning parsing.
> As the {{TODO}} in the source already states, please a some logging of the
> exception here.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
