[jira] [Commented] (CAMEL-17232) AWS 2 S3 Body is null with includeBody=false (3.13.0 regression)

["Andrea Cosentino (Jira)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/CAMEL-17232?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17448976#comment-17448976 ] 

Andrea Cosentino commented on CAMEL-17232:
------------------------------------------

I don't think so, if includeBody is false, the body should be not set.

> AWS 2 S3 Body is null with includeBody=false (3.13.0 regression)
> ----------------------------------------------------------------
>
>                 Key: CAMEL-17232
>                 URL: https://issues.apache.org/jira/browse/CAMEL-17232
>             Project: Camel
>          Issue Type: Bug
>          Components: camel-aws2
>    Affects Versions: 3.13.0
>         Environment: Java: 17 Azul OpenJDK
> Quarkus: 2.5.0.Final
> Camel 3.13.0
>  
>            Reporter: Vladimir Konkov
>            Priority: Major
>              Labels: AWS
>
> According to docs:
> If false the S3Object *stream will be put raw into the body* and the headers will be set with the S3 object metadata. This option is strongly related to autocloseBody option. In case of setting includeBody to true because the S3Object stream will be consumed then it will also be closed, while in case of includeBody false then it will be up to the caller to close the S3Object stream. However setting autocloseBody to true when includeBody is false it will schedule to close the S3Object stream automatically on exchange completion.
>  
> This will broke all body streaming cases, so component becomes useless for large objects.
> Broken by commit:
> [https://github.com/apache/camel/commit/ad296097c48558ffdf938fd8646bbeb6e7fd6320]
>  
> Please, revert it.



--
This message was sent by Atlassian Jira
(v8.20.1#820001)