You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@camel.apache.org by "Claus Ibsen (Jira)" <ji...@apache.org> on 2024/07/12 15:50:00 UTC
[jira] [Comment Edited] (CAMEL-20971) camel - aws - S3 getObject consumer does not accept dynamic keyname
[ https://issues.apache.org/jira/browse/CAMEL-20971?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17865530#comment-17865530 ]
Claus Ibsen edited comment on CAMEL-20971 at 7/12/24 3:49 PM:
--------------------------------------------------------------
Because the key can be dynamic you want to know what the actual value is, so have to add PRODUCED_KEY header in the output that stores this information.
was (Author: davsclaus):
Because the key can be dynamic you want to know what the actual value is, so have to add PRODUCED_KEY header that stores this information.
> camel - aws - S3 getObject consumer does not accept dynamic keyname
> -------------------------------------------------------------------
>
> Key: CAMEL-20971
> URL: https://issues.apache.org/jira/browse/CAMEL-20971
> Project: Camel
> Issue Type: New Feature
> Components: camel-aws
> Affects Versions: 4.6.0
> Environment: Camel 4.6.0
> Localstack 3.0.2
> Reporter: Mark Wimpory
> Assignee: Claus Ibsen
> Priority: Minor
> Fix For: 4.8.0
>
> Attachments: WranglerSQSS3RouteBuilder.java
>
>
> I have spent some time trying to build a route that will read a message from SQS and then based on the content of the message read a file from S3. This is a fairly typical triggering mechanism for S3 and we use it a lot. So when a file arrives in S3 we trigger an SQS message that will process said file.
> With the keyname as a constant this works fine and I can retrieve a stream from S3. However whenever I switch the keyname to a variable value I get a 'key not found' error.
> I will attach a route class as a reproducer. Its worth noting that I have tried several approaches which will be commented out in the reproducer.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)