You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tika.apache.org by "Tilman Hausherr (Jira)" <ji...@apache.org> on 2025/10/25 14:54:00 UTC

[jira] [Updated] (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 ]

Tilman Hausherr updated TIKA-3552:
----------------------------------
    Component/s: tika-pipes

> Improve robustness of S3 fetcher and emitter
> --------------------------------------------
>
>                 Key: TIKA-3552
>                 URL: https://issues.apache.org/jira/browse/TIKA-3552
>             Project: Tika
>          Issue Type: Task
>          Components: tika-pipes
>            Reporter: Tim Allison
>            Priority: Major
>              Labels: aws, aws-s3
>             Fix For: 2.2.0
>
>
> 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.20.10#820010)