[
https://issues.apache.org/jira/browse/TIKA-3695?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17510813#comment-17510813
]
Hudson commented on TIKA-3695:
------------------------------
SUCCESS: Integrated in Jenkins build Tika » tika-main-jdk8 #498 (See
[https://ci-builds.apache.org/job/Tika/job/tika-main-jdk8/498/])
TIKA-3695 -- fix serialization in tika-bundle forkparser test (tallison:
[https://github.com/apache/tika/commit/2a0f51ef0f281239b98fbc0b160cb194e54ceac2])
* (edit)
tika-core/src/main/java/org/apache/tika/metadata/writefilter/MetadataWriteFilter.java
* (edit) tika-core/src/main/java/org/apache/tika/metadata/Metadata.java
* (edit) tika-bundles/tika-bundle-standard/pom.xml
* (edit)
tika-core/src/main/java/org/apache/tika/metadata/writefilter/StandardWriteFilter.java
> 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)
