[ https://issues.apache.org/jira/browse/TIKA-1074?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13571288#comment-13571288
]
Michael McCandless commented on TIKA-1074:
------------------------------------------
TIKA-1079 is another example where if we recorded/logged an exc and moved on we could have
parsed the rest of the document ...
> Extraction should continue if an exception is hit visiting an embedded document
> -------------------------------------------------------------------------------
>
> Key: TIKA-1074
> URL: https://issues.apache.org/jira/browse/TIKA-1074
> Project: Tika
> Issue Type: Improvement
> Components: parser
> Reporter: Michael McCandless
> Fix For: 1.4
>
>
> Spinoff from TIKA-1072.
> In that issue, a problematic document (still not sure if document is corrupt, or possible
POI bug) caused an exception when visiting the embedded documents.
> If I change Tika to suppress that exception, the rest of the document extracts fine.
> So somehow I think we should be more robust here, and maybe log the exception, or save/record
the exception(s) somewhere so after parsing the app could decide what to do about them ...
--
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
|