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/14 14:41:00 UTC

[jira] [Resolved] (TIKA-3552) Improve robustness of S3 fetcher and emitter

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

Tim Allison resolved TIKA-3552.
-------------------------------
    Fix Version/s: 2.1.1
       Resolution: Fixed

> Improve robustness of S3 fetcher and emitter
> --------------------------------------------
>
>                 Key: TIKA-3552
>                 URL: https://issues.apache.org/jira/browse/TIKA-3552
>             Project: Tika
>          Issue Type: Task
>            Reporter: Tim Allison
>            Priority: Major
>             Fix For: 2.1.1
>
>
> We should allow users to set the maxConnections for both.  
> For the emitter, if there is an underlying file, we should use that in the putObject call; in practice, I was getting a number of inputstream.reset exceptions during aws client's uploading of the stream, specifically when it was digesting the stream before upload.  Those exceptions went away when I used the client to upload the underlying file.



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