[
https://issues.apache.org/jira/browse/TIKA-1948?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15238389#comment-15238389
]
Hudson commented on TIKA-1948:
------------------------------
FAILURE: Integrated in tika-trunk-jdk1.7 #951 (See
[https://builds.apache.org/job/tika-trunk-jdk1.7/951/])
TIKA-1948 -- handle per page IOExceptions more robustly in PDFParser (tallison:
rev b4404c33f641d14507c5a13cc0b0f5e7c2cffab1)
* tika-parsers/src/test/resources/test-documents/testPDF_bad_page_303226.pdf
* tika-parsers/src/main/java/org/apache/tika/parser/pdf/PDFParserConfig.java
* tika-parsers/src/test/java/org/apache/tika/parser/pdf/PDFParserTest.java
*
tika-parsers/src/main/resources/org/apache/tika/parser/pdf/PDFParser.properties
* tika-parsers/src/main/java/org/apache/tika/parser/pdf/PDF2XHTML.java
> Catch exceptions per page in PDFParser
> --------------------------------------
>
> Key: TIKA-1948
> URL: https://issues.apache.org/jira/browse/TIKA-1948
> Project: Tika
> Issue Type: Improvement
> Reporter: Tim Allison
> Assignee: Tim Allison
> Priority: Minor
> Fix For: 2.0, 1.13
>
>
> In a discussion with [~tilman] somewhere(???), I think he observed that we
> weren't doing a try/catch for each page. If there's an exception in an early
> page, it might still be possible to extract text from later pages in a
> problematic PDF.
> With very minimal modifications we could add a try/catch per page, store the
> caught exceptions, and then throw the first caught exception after the parse
> finishes.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
