[
https://issues.apache.org/jira/browse/TIKA-3372?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17337587#comment-17337587
]
Hudson commented on TIKA-3372:
------------------------------
SUCCESS: Integrated in Jenkins build Tika ยป tika-branch1x-jdk8 #123 (See
[https://ci-builds.apache.org/job/Tika/job/tika-branch1x-jdk8/123/])
TIKA-3372 -- fix write limit handling in the PDFParser (tallison:
[https://github.com/apache/tika/commit/2f80958c5e2264dd4b9007f331d50d1012cc8fa0])
* (edit)
tika-server/src/test/java/org/apache/tika/server/RecursiveMetadataResourceTest.java
* (edit)
tika-core/src/main/java/org/apache/tika/parser/RecursiveParserWrapper.java
* (edit) tika-server/src/test/java/org/apache/tika/server/TikaResourceTest.java
* (edit)
tika-parsers/src/main/java/org/apache/tika/parser/pdf/AbstractPDF2XHTML.java
* (edit) tika-parsers/src/main/java/org/apache/tika/parser/pdf/PDF2XHTML.java
> Fix writelimit in recursiveparserhandler
> ----------------------------------------
>
> Key: TIKA-3372
> URL: https://issues.apache.org/jira/browse/TIKA-3372
> Project: Tika
> Issue Type: Task
> Reporter: Tim Allison
> Priority: Major
>
> On the dev list, [~julienFL] noted surprising behavior with the new write
> limit in the /rmeta handler. I wasn't able to replicate it, but there is
> clearly a bug in how the write limiting is working. The upshot is that we're
> still effectively write limiting per object not for the full container doc
> and embedded objects.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
