[ https://issues.apache.org/jira/browse/TIKA-1074?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13584194#comment-13584194 ]
Ray Gauss II commented on TIKA-1074: ------------------------------------ bq. But it's a little weird throw TikaExc in response to an interrupt (ie, code above will be trying to catch an IE) ... I think it's cleaner to set the interrupt bit and let the next place that waits see the interrupt bit and throw IE? That's what I found in my investigation for TIKA-775 / TIKA-1059 as well. > 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 > Assignee: Michael McCandless > Fix For: 1.4 > > Attachments: TIKA-1074.patch, TIKA-1074.patch > > > 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