You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@camel.apache.org by "Luca Burgazzoli (Jira)" <ji...@apache.org> on 2021/02/11 11:06:00 UTC

[jira] [Assigned] (CAMEL-16185) aws s3: improve multipart support

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

Luca Burgazzoli reassigned CAMEL-16185:
---------------------------------------

    Assignee: Andrea Cosentino

> aws s3: improve multipart support
> ---------------------------------
>
>                 Key: CAMEL-16185
>                 URL: https://issues.apache.org/jira/browse/CAMEL-16185
>             Project: Camel
>          Issue Type: Improvement
>          Components: camel-aws-s3, camel-aws2, camel-aws2-s3
>            Reporter: Luca Burgazzoli
>            Assignee: Andrea Cosentino
>            Priority: Minor
>
> AWS S3 support multipart upload and as today we are using such functionality in the camel-aws3-s3 component to split a message body into chunks of a configurable size and upload them as parts to S3 but it would be nice to have more flexibility as example to be able to treat individual exchanges as chunks.
> In fact it is about using S3 as a sort of aggregation repository.
> As example, assuming we want to implement a workflow like:
> - get records from a database
> - filter and transform records
> - aggregate records 
> - send the result to s3
> That would require to set-up a local aggregation repository which is ok but increase the resources required to run the integration as well as the moving parts. By leveraging multipart uploads from S3 we could avoid the local aggregation repository.



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