[
https://issues.apache.org/jira/browse/CAMEL-9507?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15130731#comment-15130731
]
Doug Tung edited comment on CAMEL-9507 at 2/4/16 11:31 PM:
-----------------------------------------------------------
Hi Claus,
I will put in a PR today. Its very simple change and we have been using it
with no issues for a bit now on our end. I had held off because I was
thinking a more seamless strategy for integration testing would be nice.
But, perhaps this is overkill.
was (Author: dwtung):
Hi Claus,
I will put in a PR today. Its very simple change and we have been using it
with no issues for a bit now on our end. I had held off because I was
thinking a more seamless strategy for integration testing would be nice.
But, perhaps this is overkill.
Doug Tung
Internet Systems Group, Inc.
2801 Ocean Park Blvd., #248
Santa Monica, CA 90405
310-845-6474
[email protected]
> 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)
