Andrea Cosentino created CAMEL-17110:
----------------------------------------
Summary: Camel-Kamelets: While using AWS S3 source noticed files
were deleted before being consumed at all
Key: CAMEL-17110
URL: https://issues.apache.org/jira/browse/CAMEL-17110
Project: Camel
Issue Type: Bug
Affects Versions: 3.11.3
Reporter: Andrea Cosentino
{code:java}
- route:
from:
uri: "kamelet:aws-s3-source"
parameters:
bucketNameOrArn: "camel-kafka-connector"
accessKey: "access"
secretKey: "secret"
region: "eu-west-1"
steps:
- to:
uri: "kamelet:kafka-not-secured-sink"
parameters:
brokers: "localhost:9092"
topic: "s3-source-topic"
{code}
In the log, if you enabled trace you may notice something like:
{code:java}
10:14:24.476 [Camel (AWS-S3-To-Kafka) thread #11 -
KafkaProducer[s3-source-topic]] TRACE o.a.c.c.aws2.s3.AWS2S3Consumer - Deleted
object from bucket camel-kafka-connector with key jkXzIEbaYyKMTMwGpNHL.txt...
10:14:24.491 [Camel (AWS-S3-To-Kafka) thread #0 -
aws2-s3://camel-kafka-connector] TRACE s.a.awssdk.auth.signer.Aws4Signer - AWS4
Canonical Request: GET
/jkXzIEbaYyKMTMwGpNHL.txt
10:14:24.582 [Camel (AWS-S3-To-Kafka) thread #0 -
aws2-s3://camel-kafka-connector] DEBUG software.amazon.awssdk.request -
Received error response:
software.amazon.awssdk.services.s3.model.NoSuchKeyException: The specified key
does not exist.
{code}
While, the get should happens before the deletions. This is happening only when
using Kamelets. It looks like the exchange completed before the get operation
has been done.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
