You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@tika.apache.org by "Julien Massiera (Jira)" <ji...@apache.org> on 2021/05/03 09:37:00 UTC

[jira] [Commented] (TIKA-3372) Fix writelimit in recursiveparserhandler

    [ https://issues.apache.org/jira/browse/TIKA-3372?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17338281#comment-17338281 ] 

Julien Massiera commented on TIKA-3372:
---------------------------------------

[~tallison] the fix works ! 

So for the bunch of \n at the beginning there is nothing to do ? Because with the unpack endpoint for instance, the text content does not contain all the \n

> 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)