[
https://issues.apache.org/jira/browse/TIKA-3372?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17333168#comment-17333168
]
Julien Massiera commented on TIKA-3372:
---------------------------------------
Concerning the behavior you describe [~tallison], what does it cost to gather
metadata of an object ? Does it require to entirely parse the file/object ?
One of the goals I have in mind with the limit is to save time and resources
consumption, if gathering metadata is a trivial process then I don't see any
reason not to. We could also have a parameter allowing us to decide gathering
or not metadata of ignored 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, [~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)
