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

Posted to dev@tika.apache.org by "Tim Allison (Jira)" <ji...@apache.org> on 2021/09/08 15:49:00 UTC

[jira] [Resolved] (TIKA-3546) Side effects of setting WriteOutContentHandler write limit as -1 are unknown

     [ https://issues.apache.org/jira/browse/TIKA-3546?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Tim Allison resolved TIKA-3546.
-------------------------------
    Resolution: Not A Problem

> Side effects of setting WriteOutContentHandler write limit as -1 are unknown
> ----------------------------------------------------------------------------
>
>                 Key: TIKA-3546
>                 URL: https://issues.apache.org/jira/browse/TIKA-3546
>             Project: Tika
>          Issue Type: Improvement
>          Components: core
>            Reporter: Yash Mehta
>            Priority: Minor
>
> WriteOutContentHandler has a parameterized constructor which can be used to specify the writeLimit. The default seems to be 100,000 characters. Setting this to -1 signifies no writing limit. I want to understand the side effects of keeping it as -1, whether it can cause any memory or performance issues.
>  
> I also want to understand the reason why this write limit was introduced in the first place, any use-case or user scenario due to which this parameter was introduced.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)