[
https://issues.apache.org/jira/browse/CAMEL-9507?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15131263#comment-15131263
]
ASF GitHub Bot commented on CAMEL-9507:
---------------------------------------
GitHub user drsquidop opened a pull request:
https://github.com/apache/camel/pull/825
CAMEL-9507 Add includeBody option to camel-aws S3 consumer
For your consideration:
CAMEL-9507 Add includeBody option to camel-aws S3 consumer
https://issues.apache.org/jira/browse/CAMEL-9507
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/drsquidop/camel CAMEL-9507
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/camel/pull/825.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #825
----
commit c93456bdf04299835dc20d6855120dfd7dcc1895
Author: Doug Tung <[email protected]>
Date: 2016-02-03T19:45:54Z
CAMEL-9507 Add includeBody option to camel-aws S3 consumer
----
> Support suppressing body from aws-s3 consumer
> ---------------------------------------------
>
> Key: CAMEL-9507
> URL: https://issues.apache.org/jira/browse/CAMEL-9507
> Project: Camel
> Issue Type: New Feature
> Components: camel-aws
> Affects Versions: 2.16.1
> Reporter: Doug Tung
>
> Add a configuration option to suppress the downloading of the s3 object for
> the aws-s3 consumer. Just return the metadata.
> Sometimes, you may want to use the claimcheck pattern with S3, where you care
> about a new object but will not actually download it in Camel. An example of
> this is the Redshift COPY command. When a file arrives in S3, we can import
> it into Redshift.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)