[
https://issues.apache.org/jira/browse/TIKA-3372?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tim Allison updated TIKA-3372:
------------------------------
Description: On the dev list, [~jmssiera] 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. (was: On the dev list, Julien Massiera 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.)
> 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, [~jmssiera] 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)
