[
https://issues.apache.org/jira/browse/TIKA-2849?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16816667#comment-16816667
]
Tim Allison commented on TIKA-2849:
-----------------------------------
On the TIKA-2849 branch, I also included an example of how to configure the
ZipContainerDetector to read more or less of a zip stream by setting
{{markLimit}} via a {{tika-config.xml}} file as we do for our encoding
detectors:
https://github.com/apache/tika/blob/1e08fb1e54653954a71c71a68218bcdf7a7a3afb/tika-parsers/src/test/java/org/apache/tika/parser/pkg/ZipContainerDetectorTest.java#L85
and
https://github.com/apache/tika/blob/TIKA-2849/tika-parsers/src/test/resources/org/apache/tika/parser/pkg/tika-config.xml
> TikaInputStream copies the input stream locally
> -----------------------------------------------
>
> Key: TIKA-2849
> URL: https://issues.apache.org/jira/browse/TIKA-2849
> Project: Tika
> Issue Type: Bug
> Affects Versions: 1.20
> Reporter: Boris Petrov
> Assignee: Tim Allison
> Priority: Major
>
> When doing "tika.detect(stream, name)" and the stream is a "TikaInputStream",
> execution gets to "TikaInputStream#getPath" which does a "Files.copy(in,
> path, REPLACE_EXISTING);" which is very, very bad. This input stream could
> be, as in our case, an input stream from a network file which is tens or
> hundreds of gigabytes large. Copying it locally is a huge waste of resources
> to say the least. Why does it do that and can I make it not do it? Or is this
> something that has to be fixed in Tika?
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
