You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tika.apache.org by "Christian Reuschling (JIRA)" <ji...@apache.org> on 2014/06/17 14:17:01 UTC
[jira] [Updated] (TIKA-1341) double invocation of
handler.endDocument() in PDFParser
[ https://issues.apache.org/jira/browse/TIKA-1341?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Christian Reuschling updated TIKA-1341:
---------------------------------------
Fix Version/s: (was: 1.4)
(was: 1.3)
> double invocation of handler.endDocument() in PDFParser
> -------------------------------------------------------
>
> Key: TIKA-1341
> URL: https://issues.apache.org/jira/browse/TIKA-1341
> Project: Tika
> Issue Type: Bug
> Components: parser
> Affects Versions: 1.5, 1.6
> Environment: suse linux 64bit, oracle java 7
> Reporter: Christian Reuschling
> Priority: Critical
> Labels: easyfix
> Original Estimate: 10m
> Remaining Estimate: 10m
>
> I currently migrate to Tika 1.5, and fall into this behaviour, which leads to double entries in my database for one pdf file as I work directly with the handler.
> Here are the two calls:
> First call is in PDF2HTML, line 197: handler.endDocument();
> this is part of the PDF2XHTML.process(pdfDocument, handler, context, metadata, localConfig);
> invocation from PDFParser, line 143.
> The second call is then directly in PDFParser, line 151: handler.endDocument();
> Must stay at Tika 1.4 for now - still thanks for good work!
--
This message was sent by Atlassian JIRA
(v6.2#6252)