[
https://issues.apache.org/jira/browse/TIKA-3695?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17509315#comment-17509315
]
Julien Massiera commented on TIKA-3695:
---------------------------------------
I think that the minimum is to count the key lengths in the current max yes.
Otherwise, as an example, in the Tika server connector I did for ManifodCF, I
have three parameters :
* maxKeyLength : max bytes for a metadata key
* maxValueLength: max bytes per value addition (not counting the key)
* maxTotalMetadata: max bytes for the total amount of metadata (keys + values)
For our case, if the maxEstimatedBytes in Tika represents the maxTotalMetadata
that counts the key lengths + all the values of the total of metadata it is
enough. The other parameters would be a valuable bonus though !
> LimitingMetadataFilter
> ----------------------
>
> Key: TIKA-3695
> URL: https://issues.apache.org/jira/browse/TIKA-3695
> Project: Tika
> Issue Type: New Feature
> Components: metadata
> Affects Versions: 1.28.1, 2.3.0
> Reporter: Julien Massiera
> Priority: Major
> Fix For: 2.4.0
>
> Attachments: huge-title.docx, tika-config.xml
>
>
> Some files may contain abnormally big metadata (several MB, be it for the
> metadata values, the metadata names, but also for the total amount of
> metadata) that can be problematic concerning the memory consumption.
> It would be great to develop a new LimitingMetadataFilter so that we can
> filter out the metadata according to different bytes limits (on metadata
> names, metadata values and global amount of metadata)
>
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
