[jira] [Resolved] (CAMEL-20469) Camel-AWS-Bedrock: Support Amazon Titan Text G1 Lite Model
[ https://issues.apache.org/jira/browse/CAMEL-20469?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Cosentino resolved CAMEL-20469. -- Resolution: Fixed > Camel-AWS-Bedrock: Support Amazon Titan Text G1 Lite Model > -- > > Key: CAMEL-20469 > URL: https://issues.apache.org/jira/browse/CAMEL-20469 > Project: Camel > Issue Type: Sub-task >Reporter: Andrea Cosentino >Assignee: Andrea Cosentino >Priority: Major > Fix For: 4.5.0 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (CAMEL-20469) Camel-AWS-Bedrock: Support Amazon Titan Text G1 Lite Model
Andrea Cosentino created CAMEL-20469: Summary: Camel-AWS-Bedrock: Support Amazon Titan Text G1 Lite Model Key: CAMEL-20469 URL: https://issues.apache.org/jira/browse/CAMEL-20469 Project: Camel Issue Type: Sub-task Reporter: Andrea Cosentino Assignee: Andrea Cosentino Fix For: 4.5.0 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (CAMEL-20468) Camel-AWS-Bedrock: Support available models
Andrea Cosentino created CAMEL-20468: Summary: Camel-AWS-Bedrock: Support available models Key: CAMEL-20468 URL: https://issues.apache.org/jira/browse/CAMEL-20468 Project: Camel Issue Type: New Feature Reporter: Andrea Cosentino Assignee: Andrea Cosentino Fix For: 4.5.0 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (CAMEL-20467) Camel AWS Bedrock: Create Spring Boot starter
Andrea Cosentino created CAMEL-20467: Summary: Camel AWS Bedrock: Create Spring Boot starter Key: CAMEL-20467 URL: https://issues.apache.org/jira/browse/CAMEL-20467 Project: Camel Issue Type: New Feature Reporter: Andrea Cosentino Assignee: Andrea Cosentino Fix For: 4.5.0 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (CAMEL-20095) Create a component for OpenAI
[ https://issues.apache.org/jira/browse/CAMEL-20095?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17821126#comment-17821126 ] Andrea Cosentino commented on CAMEL-20095: -- What's the status of this? > Create a component for OpenAI > - > > Key: CAMEL-20095 > URL: https://issues.apache.org/jira/browse/CAMEL-20095 > Project: Camel > Issue Type: New Feature >Reporter: Zineb Bendhiba >Assignee: Zineb Bendhiba >Priority: Major > Attachments: telegram-openAPI.mp4 > > > Investigate on the Java library langchain4j, to create a component that can > integrate to OpenAI, HugginFace and more via langchain > > This is the link to the project : [https://github.com/langchain4j/langchain4j] > > the attached video is a first POC playing with Camel telegram and OpenAI > > [^telegram-openAPI.mp4] -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (CAMEL-20463) Create an AWS Bedrock Runtime component
Andrea Cosentino created CAMEL-20463: Summary: Create an AWS Bedrock Runtime component Key: CAMEL-20463 URL: https://issues.apache.org/jira/browse/CAMEL-20463 Project: Camel Issue Type: New Feature Reporter: Andrea Cosentino Assignee: Andrea Cosentino Fix For: 4.5.0 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (CAMEL-20451) Azure Eventhubs CloudEvent transformer
[ https://issues.apache.org/jira/browse/CAMEL-20451?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Cosentino resolved CAMEL-20451. -- Resolution: Fixed > Azure Eventhubs CloudEvent transformer > -- > > Key: CAMEL-20451 > URL: https://issues.apache.org/jira/browse/CAMEL-20451 > Project: Camel > Issue Type: Sub-task >Reporter: Andrea Cosentino >Assignee: Andrea Cosentino >Priority: Major > Fix For: 4.5.0 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (CAMEL-20453) Azure CosmosDB CloudEvent transformer
[ https://issues.apache.org/jira/browse/CAMEL-20453?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Cosentino resolved CAMEL-20453. -- Resolution: Fixed > Azure CosmosDB CloudEvent transformer > - > > Key: CAMEL-20453 > URL: https://issues.apache.org/jira/browse/CAMEL-20453 > Project: Camel > Issue Type: Sub-task >Reporter: Andrea Cosentino >Assignee: Andrea Cosentino >Priority: Major > Fix For: 4.5.0 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (CAMEL-20450) Azure Servicebus CloudEvent transformer
[ https://issues.apache.org/jira/browse/CAMEL-20450?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Cosentino resolved CAMEL-20450. -- Resolution: Fixed > Azure Servicebus CloudEvent transformer > --- > > Key: CAMEL-20450 > URL: https://issues.apache.org/jira/browse/CAMEL-20450 > Project: Camel > Issue Type: Sub-task >Reporter: Andrea Cosentino >Assignee: Andrea Cosentino >Priority: Major > Fix For: 4.5.0 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (CAMEL-20453) Azure CosmosDB CloudEvent transformer
Andrea Cosentino created CAMEL-20453: Summary: Azure CosmosDB CloudEvent transformer Key: CAMEL-20453 URL: https://issues.apache.org/jira/browse/CAMEL-20453 Project: Camel Issue Type: Sub-task Reporter: Andrea Cosentino Assignee: Andrea Cosentino Fix For: 4.5.0 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (CAMEL-20452) Azure Storage Datalake CloudEvent transformer
Andrea Cosentino created CAMEL-20452: Summary: Azure Storage Datalake CloudEvent transformer Key: CAMEL-20452 URL: https://issues.apache.org/jira/browse/CAMEL-20452 Project: Camel Issue Type: Sub-task Reporter: Andrea Cosentino Assignee: Andrea Cosentino Fix For: 4.5.0 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (CAMEL-20451) Azure Eventhubs CloudEvent transformer
Andrea Cosentino created CAMEL-20451: Summary: Azure Eventhubs CloudEvent transformer Key: CAMEL-20451 URL: https://issues.apache.org/jira/browse/CAMEL-20451 Project: Camel Issue Type: Sub-task Reporter: Andrea Cosentino Assignee: Andrea Cosentino Fix For: 4.5.0 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (CAMEL-20450) Azure Servicebus CloudEvent transformer
Andrea Cosentino created CAMEL-20450: Summary: Azure Servicebus CloudEvent transformer Key: CAMEL-20450 URL: https://issues.apache.org/jira/browse/CAMEL-20450 Project: Camel Issue Type: Sub-task Reporter: Andrea Cosentino Assignee: Andrea Cosentino Fix For: 4.5.0 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (CAMEL-20449) Azure Storage Files CloudEvent transformer
[ https://issues.apache.org/jira/browse/CAMEL-20449?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Cosentino resolved CAMEL-20449. -- Resolution: Fixed > Azure Storage Files CloudEvent transformer > -- > > Key: CAMEL-20449 > URL: https://issues.apache.org/jira/browse/CAMEL-20449 > Project: Camel > Issue Type: Sub-task >Reporter: Andrea Cosentino >Assignee: Andrea Cosentino >Priority: Major > Fix For: 4.5.0 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (CAMEL-20449) Azure Storage Files CloudEvent transformer
[ https://issues.apache.org/jira/browse/CAMEL-20449?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Cosentino updated CAMEL-20449: - Summary: Azure Storage Files CloudEvent transformer (was: Azure Storage File CloudEvent transformer) > Azure Storage Files CloudEvent transformer > -- > > Key: CAMEL-20449 > URL: https://issues.apache.org/jira/browse/CAMEL-20449 > Project: Camel > Issue Type: Sub-task >Reporter: Andrea Cosentino >Assignee: Andrea Cosentino >Priority: Major > Fix For: 4.5.0 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (CAMEL-20449) Azure Storage File CloudEvent transformer
Andrea Cosentino created CAMEL-20449: Summary: Azure Storage File CloudEvent transformer Key: CAMEL-20449 URL: https://issues.apache.org/jira/browse/CAMEL-20449 Project: Camel Issue Type: Sub-task Reporter: Andrea Cosentino Assignee: Andrea Cosentino Fix For: 4.5.0 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (CAMEL-18276) azure-service-bus component does not support session
[ https://issues.apache.org/jira/browse/CAMEL-18276?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Cosentino updated CAMEL-18276: - Fix Version/s: 4.5.0 (was: 4.x) > azure-service-bus component does not support session > > > Key: CAMEL-18276 > URL: https://issues.apache.org/jira/browse/CAMEL-18276 > Project: Camel > Issue Type: New Feature > Components: camel-azure >Affects Versions: 3.18.0 >Reporter: Jean-Benoît >Assignee: Andrea Cosentino >Priority: Minor > Fix For: 4.5.0 > > > Hello, > From what I could tell, the azure-servicebus component does not support > sessions. Any chance this can be added in an upcoming release? -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (CAMEL-18276) azure-service-bus component does not support session
[ https://issues.apache.org/jira/browse/CAMEL-18276?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Cosentino reassigned CAMEL-18276: Assignee: Andrea Cosentino > azure-service-bus component does not support session > > > Key: CAMEL-18276 > URL: https://issues.apache.org/jira/browse/CAMEL-18276 > Project: Camel > Issue Type: New Feature > Components: camel-azure >Affects Versions: 3.18.0 >Reporter: Jean-Benoît >Assignee: Andrea Cosentino >Priority: Minor > Fix For: 4.x > > > Hello, > From what I could tell, the azure-servicebus component does not support > sessions. Any chance this can be added in an upcoming release? -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (CAMEL-20444) Camel-Azure-Servicebus: Support setting of CorrelationId on producer
[ https://issues.apache.org/jira/browse/CAMEL-20444?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Cosentino resolved CAMEL-20444. -- Resolution: Fixed > Camel-Azure-Servicebus: Support setting of CorrelationId on producer > - > > Key: CAMEL-20444 > URL: https://issues.apache.org/jira/browse/CAMEL-20444 > Project: Camel > Issue Type: Bug > Components: camel-azure >Affects Versions: 4.0.4, 4.4.0 >Reporter: Andrea Cosentino >Assignee: Andrea Cosentino >Priority: Major > Fix For: 4.4.1, 4.5.0, 4.0.5 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (CAMEL-20444) Camel-Azure-Servicebus: Support setting of CorrelationId on producer
[ https://issues.apache.org/jira/browse/CAMEL-20444?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Cosentino updated CAMEL-20444: - Fix Version/s: 4.0.5 > Camel-Azure-Servicebus: Support setting of CorrelationId on producer > - > > Key: CAMEL-20444 > URL: https://issues.apache.org/jira/browse/CAMEL-20444 > Project: Camel > Issue Type: Bug > Components: camel-azure >Affects Versions: 4.0.4, 4.4.0 >Reporter: Andrea Cosentino >Assignee: Andrea Cosentino >Priority: Major > Fix For: 4.4.1, 4.5.0, 4.0.5 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (CAMEL-20444) Camel-Azure-Servicebus: Support setting of CorrelationId on producer
[ https://issues.apache.org/jira/browse/CAMEL-20444?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Cosentino updated CAMEL-20444: - Fix Version/s: (was: 4.0.5) > Camel-Azure-Servicebus: Support setting of CorrelationId on producer > - > > Key: CAMEL-20444 > URL: https://issues.apache.org/jira/browse/CAMEL-20444 > Project: Camel > Issue Type: Bug >Affects Versions: 4.0.4, 4.4.0 >Reporter: Andrea Cosentino >Priority: Major > Fix For: 4.4.1, 4.5.0 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (CAMEL-20444) Camel-Azure-Servicebus: Support setting of CorrelationId on producer
[ https://issues.apache.org/jira/browse/CAMEL-20444?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Cosentino updated CAMEL-20444: - Fix Version/s: 4.0.5 > Camel-Azure-Servicebus: Support setting of CorrelationId on producer > - > > Key: CAMEL-20444 > URL: https://issues.apache.org/jira/browse/CAMEL-20444 > Project: Camel > Issue Type: Bug >Affects Versions: 4.0.4, 4.4.0 >Reporter: Andrea Cosentino >Assignee: Andrea Cosentino >Priority: Major > Fix For: 4.4.1, 4.5.0, 4.0.5 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (CAMEL-20444) Camel-Azure-Servicebus: Support setting of CorrelationId on producer
[ https://issues.apache.org/jira/browse/CAMEL-20444?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Cosentino reassigned CAMEL-20444: Assignee: Andrea Cosentino > Camel-Azure-Servicebus: Support setting of CorrelationId on producer > - > > Key: CAMEL-20444 > URL: https://issues.apache.org/jira/browse/CAMEL-20444 > Project: Camel > Issue Type: Bug >Affects Versions: 4.0.4, 4.4.0 >Reporter: Andrea Cosentino >Assignee: Andrea Cosentino >Priority: Major > Fix For: 4.4.1, 4.5.0 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (CAMEL-20444) Camel-Azure-Servicebus: Support setting of CorrelationId on producer
Andrea Cosentino created CAMEL-20444: Summary: Camel-Azure-Servicebus: Support setting of CorrelationId on producer Key: CAMEL-20444 URL: https://issues.apache.org/jira/browse/CAMEL-20444 Project: Camel Issue Type: New Feature Affects Versions: 4.4.0, 4.0.4 Reporter: Andrea Cosentino Fix For: 4.0.5, 4.4.1, 4.5.0 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (CAMEL-20444) Camel-Azure-Servicebus: Support setting of CorrelationId on producer
[ https://issues.apache.org/jira/browse/CAMEL-20444?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Cosentino updated CAMEL-20444: - Issue Type: Bug (was: New Feature) > Camel-Azure-Servicebus: Support setting of CorrelationId on producer > - > > Key: CAMEL-20444 > URL: https://issues.apache.org/jira/browse/CAMEL-20444 > Project: Camel > Issue Type: Bug >Affects Versions: 4.0.4, 4.4.0 >Reporter: Andrea Cosentino >Priority: Major > Fix For: 4.4.1, 4.5.0, 4.0.5 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (CAMEL-20417) AWS DDBStreams CloudEvent Transformer
[ https://issues.apache.org/jira/browse/CAMEL-20417?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Cosentino resolved CAMEL-20417. -- Resolution: Fixed > AWS DDBStreams CloudEvent Transformer > - > > Key: CAMEL-20417 > URL: https://issues.apache.org/jira/browse/CAMEL-20417 > Project: Camel > Issue Type: Sub-task >Reporter: Andrea Cosentino >Assignee: Andrea Cosentino >Priority: Major > Fix For: 4.5.0 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (CAMEL-20416) AWS Kinesis CloudEvent Transformer
[ https://issues.apache.org/jira/browse/CAMEL-20416?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Cosentino resolved CAMEL-20416. -- Resolution: Fixed > AWS Kinesis CloudEvent Transformer > -- > > Key: CAMEL-20416 > URL: https://issues.apache.org/jira/browse/CAMEL-20416 > Project: Camel > Issue Type: Sub-task >Reporter: Andrea Cosentino >Assignee: Andrea Cosentino >Priority: Major > Fix For: 4.5.0 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (CAMEL-20428) Kafka Batch Consumer: Some common headers in the batch exchanges should be copied also to the original exchange
Andrea Cosentino created CAMEL-20428: Summary: Kafka Batch Consumer: Some common headers in the batch exchanges should be copied also to the original exchange Key: CAMEL-20428 URL: https://issues.apache.org/jira/browse/CAMEL-20428 Project: Camel Issue Type: Improvement Reporter: Andrea Cosentino Assignee: Andrea Cosentino In this way we could for example bring the kafka.TOPIC header value from the batch exchange and store it as variable, before splitting and re-use it in the logic after the split. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (CAMEL-20424) YAML DSL: Split doesn't seem to be correctly interpreted
[
https://issues.apache.org/jira/browse/CAMEL-20424?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrea Cosentino resolved CAMEL-20424.
--
Resolution: Won't Fix
> YAML DSL: Split doesn't seem to be correctly interpreted
> -
>
> Key: CAMEL-20424
> URL: https://issues.apache.org/jira/browse/CAMEL-20424
> Project: Camel
> Issue Type: Bug
>Reporter: Andrea Cosentino
>Priority: Major
>
> Suppose you have something like
> {code:java}
> - route:
> id: "kafka-to-log"
> from:
> uri: "kamelet:kafka-batch-not-secured-source"
> parameters:
> bootstrapServers: "localhost:9092"
> topic: "test-topic"
> consumerGroup: 'my-group'
> batchSize: 10
> pollTimeout: 4
> maxPollIntervalMs: 6
> autoCommitEnable: false
> allowManualCommit: true
> steps:
> - split: {}
> steps:
> - to: "kamelet:log-sink"
> - to:
> uri: "kamelet:kafka-batch-manual-commit-action"
> {code}
> This seems to be correct from a syntax perspective, but it will fail with:
> {code:java}
> Unsupported field: body
> in file:kafka-batch-log.yaml, line 40, column 19:
> body: {}
> {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (CAMEL-20424) YAML DSL: Split doesn't seem to be correctly interpreted
[
https://issues.apache.org/jira/browse/CAMEL-20424?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17817688#comment-17817688
]
Andrea Cosentino commented on CAMEL-20424:
--
Nevermind
it was
{code:java}
split:
simple: "${body}"
{code}
My bad.
> YAML DSL: Split doesn't seem to be correctly interpreted
> -
>
> Key: CAMEL-20424
> URL: https://issues.apache.org/jira/browse/CAMEL-20424
> Project: Camel
> Issue Type: Bug
>Reporter: Andrea Cosentino
>Priority: Major
>
> Suppose you have something like
> {code:java}
> - route:
> id: "kafka-to-log"
> from:
> uri: "kamelet:kafka-batch-not-secured-source"
> parameters:
> bootstrapServers: "localhost:9092"
> topic: "test-topic"
> consumerGroup: 'my-group'
> batchSize: 10
> pollTimeout: 4
> maxPollIntervalMs: 6
> autoCommitEnable: false
> allowManualCommit: true
> steps:
> - split: {}
> steps:
> - to: "kamelet:log-sink"
> - to:
> uri: "kamelet:kafka-batch-manual-commit-action"
> {code}
> This seems to be correct from a syntax perspective, but it will fail with:
> {code:java}
> Unsupported field: body
> in file:kafka-batch-log.yaml, line 40, column 19:
> body: {}
> {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Created] (CAMEL-20424) YAML DSL: Split doesn't seem to be correctly interpreted
Andrea Cosentino created CAMEL-20424:
Summary: YAML DSL: Split doesn't seem to be correctly interpreted
Key: CAMEL-20424
URL: https://issues.apache.org/jira/browse/CAMEL-20424
Project: Camel
Issue Type: Bug
Reporter: Andrea Cosentino
Suppose you have something like
{code:java}
- route:
id: "kafka-to-log"
from:
uri: "kamelet:kafka-batch-not-secured-source"
parameters:
bootstrapServers: "localhost:9092"
topic: "test-topic"
consumerGroup: 'my-group'
batchSize: 10
pollTimeout: 4
maxPollIntervalMs: 6
autoCommitEnable: false
allowManualCommit: true
steps:
- split: {}
steps:
- to: "kamelet:log-sink"
- to:
uri: "kamelet:kafka-batch-manual-commit-action"
{code}
This seems to be correct from a syntax perspective, but it will fail with:
{code:java}
Unsupported field: body
in file:kafka-batch-log.yaml, line 40, column 19:
body: {}
{code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Resolved] (CAMEL-20423) AWS STS Component: Provide a way of setting the duration of AssumeRoleRequest through header
[ https://issues.apache.org/jira/browse/CAMEL-20423?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Cosentino resolved CAMEL-20423. -- Resolution: Fixed > AWS STS Component: Provide a way of setting the duration of AssumeRoleRequest > through header > > > Key: CAMEL-20423 > URL: https://issues.apache.org/jira/browse/CAMEL-20423 > Project: Camel > Issue Type: New Feature >Reporter: Andrea Cosentino >Assignee: Andrea Cosentino >Priority: Major > Fix For: 4.5.0 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (CAMEL-20423) AWS STS Component: Provide a way of setting the duration of AssumeRoleRequest through header
Andrea Cosentino created CAMEL-20423: Summary: AWS STS Component: Provide a way of setting the duration of AssumeRoleRequest through header Key: CAMEL-20423 URL: https://issues.apache.org/jira/browse/CAMEL-20423 Project: Camel Issue Type: New Feature Reporter: Andrea Cosentino Assignee: Andrea Cosentino Fix For: 4.5.0 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (CAMEL-20415) AWS Cloudtrail CloudEvent transformer
[ https://issues.apache.org/jira/browse/CAMEL-20415?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Cosentino resolved CAMEL-20415. -- Resolution: Fixed > AWS Cloudtrail CloudEvent transformer > - > > Key: CAMEL-20415 > URL: https://issues.apache.org/jira/browse/CAMEL-20415 > Project: Camel > Issue Type: Sub-task >Reporter: Andrea Cosentino >Assignee: Andrea Cosentino >Priority: Major > Fix For: 4.5.0 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (CAMEL-20417) AWS DDBStreams CloudEvent Transformer
Andrea Cosentino created CAMEL-20417: Summary: AWS DDBStreams CloudEvent Transformer Key: CAMEL-20417 URL: https://issues.apache.org/jira/browse/CAMEL-20417 Project: Camel Issue Type: Sub-task Reporter: Andrea Cosentino Assignee: Andrea Cosentino Fix For: 4.5.0 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (CAMEL-20416) AWS Kinesis CloudEvent Transformer
Andrea Cosentino created CAMEL-20416: Summary: AWS Kinesis CloudEvent Transformer Key: CAMEL-20416 URL: https://issues.apache.org/jira/browse/CAMEL-20416 Project: Camel Issue Type: Sub-task Reporter: Andrea Cosentino Assignee: Andrea Cosentino Fix For: 4.5.0 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (CAMEL-20414) Add CloudEvent Transformers to cloud oriented component
[ https://issues.apache.org/jira/browse/CAMEL-20414?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Cosentino reassigned CAMEL-20414: Assignee: Andrea Cosentino > Add CloudEvent Transformers to cloud oriented component > --- > > Key: CAMEL-20414 > URL: https://issues.apache.org/jira/browse/CAMEL-20414 > Project: Camel > Issue Type: Task >Reporter: Andrea Cosentino >Assignee: Andrea Cosentino >Priority: Major > Fix For: 4.5.0 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (CAMEL-20414) Add CloudEvent Transformers to cloud oriented component
Andrea Cosentino created CAMEL-20414: Summary: Add CloudEvent Transformers to cloud oriented component Key: CAMEL-20414 URL: https://issues.apache.org/jira/browse/CAMEL-20414 Project: Camel Issue Type: Task Reporter: Andrea Cosentino Fix For: 4.5.0 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (CAMEL-20415) AWS Cloudtrail CloudEvent transformer
Andrea Cosentino created CAMEL-20415: Summary: AWS Cloudtrail CloudEvent transformer Key: CAMEL-20415 URL: https://issues.apache.org/jira/browse/CAMEL-20415 Project: Camel Issue Type: Sub-task Reporter: Andrea Cosentino Assignee: Andrea Cosentino Fix For: 4.5.0 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (CAMEL-20116) Upgrade to Jackson BOM 2.16.0
[ https://issues.apache.org/jira/browse/CAMEL-20116?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Cosentino updated CAMEL-20116: - Fix Version/s: 4.4.0 (was: 4.5.0) > Upgrade to Jackson BOM 2.16.0 > - > > Key: CAMEL-20116 > URL: https://issues.apache.org/jira/browse/CAMEL-20116 > Project: Camel > Issue Type: Dependency upgrade > Components: camel-jackson >Reporter: Andrea Cosentino >Assignee: Andrea Cosentino >Priority: Major > Fix For: 4.4.0 > > > Let's see if everything works. > https://github.com/FasterXML/jackson/wiki/Jackson-Release-2.16#full-change-list -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (CAMEL-20116) Upgrade to Jackson BOM 2.16.0
[ https://issues.apache.org/jira/browse/CAMEL-20116?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17817050#comment-17817050 ] Andrea Cosentino commented on CAMEL-20116: -- This has been done through dependabot on Jan 11 with 8fe6d1141b302bc8d9bb1d67303812186e3be383 > Upgrade to Jackson BOM 2.16.0 > - > > Key: CAMEL-20116 > URL: https://issues.apache.org/jira/browse/CAMEL-20116 > Project: Camel > Issue Type: Dependency upgrade > Components: camel-jackson >Reporter: Andrea Cosentino >Assignee: Andrea Cosentino >Priority: Major > Fix For: 4.5.0 > > > Let's see if everything works. > https://github.com/FasterXML/jackson/wiki/Jackson-Release-2.16#full-change-list -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (CAMEL-20116) Upgrade to Jackson BOM 2.16.0
[ https://issues.apache.org/jira/browse/CAMEL-20116?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Cosentino resolved CAMEL-20116. -- Resolution: Fixed > Upgrade to Jackson BOM 2.16.0 > - > > Key: CAMEL-20116 > URL: https://issues.apache.org/jira/browse/CAMEL-20116 > Project: Camel > Issue Type: Dependency upgrade > Components: camel-jackson >Reporter: Andrea Cosentino >Assignee: Andrea Cosentino >Priority: Major > Fix For: 4.4.0 > > > Let's see if everything works. > https://github.com/FasterXML/jackson/wiki/Jackson-Release-2.16#full-change-list -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (CAMEL-20355) Throttle EIP: milliseconds not available anymore
[
https://issues.apache.org/jira/browse/CAMEL-20355?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17816071#comment-17816071
]
Andrea Cosentino commented on CAMEL-20355:
--
Yes, it could be reverted at this point and maybe we could add another one with
the newer implementation.
> Throttle EIP: milliseconds not available anymore
>
>
> Key: CAMEL-20355
> URL: https://issues.apache.org/jira/browse/CAMEL-20355
> Project: Camel
> Issue Type: Improvement
> Components: camel-k, camel-kamelet, documentation
>Affects Versions: 4.3.0
>Reporter: Raymond
>Assignee: Otavio Rodolfo Piske
>Priority: Minor
> Fix For: 4.4.0
>
>
> Recently, the Throttle EIP was changed. For example, in this issue:
> https://issues.apache.org/jira/browse/CAMEL-16099
> Now the option "{*}timePeriodMillis{*}" isn't available anymore:
> [https://camel.apache.org/components/next/eips/throttle-eip.html]
> This is also documented in the migration guide:
> [https://camel.apache.org/manual/camel-4x-upgrade-guide-4_3.html]
> However:
> 1. The option is still there in the examples of the latest documentation
> 2. The option is still there in the Kamelet catalog (4.3.0):
> [https://github.com/apache/camel-kamelets/blob/main/kamelets/throttle-action.kamelet.yaml]
> When loading the throttle from the Kamelet catalog, I got the following
> message:
> {code:java}
> could not load: kamelets/throttle-action.kamelet.yaml. Reason: Field:
> timePeriodMillis has already been configured as an expression
> in throttle-action.kamelet.yaml, line 67, column 29:
> timePeriodMillis: "{{timePeriod}}" {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Resolved] (CAMEL-20281) Camel-AWS Components: Make it possible to use AwsSessionCredentials to support temporary credentials
[ https://issues.apache.org/jira/browse/CAMEL-20281?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Cosentino resolved CAMEL-20281. -- Resolution: Fixed > Camel-AWS Components: Make it possible to use AwsSessionCredentials to > support temporary credentials > > > Key: CAMEL-20281 > URL: https://issues.apache.org/jira/browse/CAMEL-20281 > Project: Camel > Issue Type: Improvement > Components: camel-aws >Reporter: Andrea Cosentino >Assignee: Andrea Cosentino >Priority: Major > Fix For: 4.4.0 > > > This is really well explained through this: > https://repost.aws/knowledge-center/iam-assume-role-cli > Essentially it could be the case, we want a user to be able to do some > operations and having temporary credentials. As of today, we don't offer a > way of creating AWS sessions credentials and I think it's a good use case. > So the idea is introducing another option useSessionsCredentials and improve > the client factories we have. That way a user would be able to use this > kamelet correctly for example: > https://github.com/apache/camel-kamelets/blob/main/kamelets/aws-sts-assume-role-action.kamelet.yaml -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (CAMEL-20281) Camel-AWS Components: Make it possible to use AwsSessionCredentials to support temporary credentials
[ https://issues.apache.org/jira/browse/CAMEL-20281?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17816056#comment-17816056 ] Andrea Cosentino commented on CAMEL-20281: -- Completed, I'll add documentation on how to use it, but for the release we are fine. > Camel-AWS Components: Make it possible to use AwsSessionCredentials to > support temporary credentials > > > Key: CAMEL-20281 > URL: https://issues.apache.org/jira/browse/CAMEL-20281 > Project: Camel > Issue Type: Improvement > Components: camel-aws >Reporter: Andrea Cosentino >Assignee: Andrea Cosentino >Priority: Major > Fix For: 4.4.0 > > > This is really well explained through this: > https://repost.aws/knowledge-center/iam-assume-role-cli > Essentially it could be the case, we want a user to be able to do some > operations and having temporary credentials. As of today, we don't offer a > way of creating AWS sessions credentials and I think it's a good use case. > So the idea is introducing another option useSessionsCredentials and improve > the client factories we have. That way a user would be able to use this > kamelet correctly for example: > https://github.com/apache/camel-kamelets/blob/main/kamelets/aws-sts-assume-role-action.kamelet.yaml -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (CAMEL-20281) Camel-AWS Components: Make it possible to use AwsSessionCredentials to support temporary credentials
[ https://issues.apache.org/jira/browse/CAMEL-20281?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Cosentino updated CAMEL-20281: - Fix Version/s: 4.4.0 (was: 4.x) > Camel-AWS Components: Make it possible to use AwsSessionCredentials to > support temporary credentials > > > Key: CAMEL-20281 > URL: https://issues.apache.org/jira/browse/CAMEL-20281 > Project: Camel > Issue Type: Improvement > Components: camel-aws >Reporter: Andrea Cosentino >Assignee: Andrea Cosentino >Priority: Major > Fix For: 4.4.0 > > > This is really well explained through this: > https://repost.aws/knowledge-center/iam-assume-role-cli > Essentially it could be the case, we want a user to be able to do some > operations and having temporary credentials. As of today, we don't offer a > way of creating AWS sessions credentials and I think it's a good use case. > So the idea is introducing another option useSessionsCredentials and improve > the client factories we have. That way a user would be able to use this > kamelet correctly for example: > https://github.com/apache/camel-kamelets/blob/main/kamelets/aws-sts-assume-role-action.kamelet.yaml -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (CAMEL-20272) Camel-Azure components: Support SAS Authentication where is still not supported
[ https://issues.apache.org/jira/browse/CAMEL-20272?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Cosentino updated CAMEL-20272: - Fix Version/s: 4.5.0 (was: 4.4.0) > Camel-Azure components: Support SAS Authentication where is still not > supported > --- > > Key: CAMEL-20272 > URL: https://issues.apache.org/jira/browse/CAMEL-20272 > Project: Camel > Issue Type: Improvement > Components: camel-azure >Reporter: Andrea Cosentino >Assignee: Andrea Cosentino >Priority: Major > Fix For: 4.5.0 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (CAMEL-20116) Upgrade to Jackson BOM 2.16.0
[ https://issues.apache.org/jira/browse/CAMEL-20116?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Cosentino updated CAMEL-20116: - Fix Version/s: 4.5.0 (was: 4.x) > Upgrade to Jackson BOM 2.16.0 > - > > Key: CAMEL-20116 > URL: https://issues.apache.org/jira/browse/CAMEL-20116 > Project: Camel > Issue Type: Dependency upgrade > Components: camel-jackson >Reporter: Andrea Cosentino >Assignee: Andrea Cosentino >Priority: Major > Fix For: 4.5.0 > > > Let's see if everything works. > https://github.com/FasterXML/jackson/wiki/Jackson-Release-2.16#full-change-list -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (CAMEL-20383) camel CI: investigate consolidating Jenkinsfiles
[ https://issues.apache.org/jira/browse/CAMEL-20383?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17813109#comment-17813109 ] Andrea Cosentino commented on CAMEL-20383: -- As suggested by [~zregvart] we should look at https://www.jenkins.io/doc/book/pipeline/syntax/#declarative-matrix > camel CI: investigate consolidating Jenkinsfiles > - > > Key: CAMEL-20383 > URL: https://issues.apache.org/jira/browse/CAMEL-20383 > Project: Camel > Issue Type: Task > Components: ci >Reporter: Otavio Rodolfo Piske >Priority: Major > Labels: help-wanted > > As we have been adding more jobs to our CI (including different JDKs versions > + different JDKs versions on different platforms). We might end up with a lot > of duplication and noise on the CI code. > We should investigate a way to consolidate all these CI automation in a > single file (or create reusable code) so it's easier to add/remove > environments. > Ideally, we should do that before duplication becomes a maintenance problem. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (CAMEL-20380) Kafka Batch Consumer: doesn't honor the poll timeout set
Andrea Cosentino created CAMEL-20380: Summary: Kafka Batch Consumer: doesn't honor the poll timeout set Key: CAMEL-20380 URL: https://issues.apache.org/jira/browse/CAMEL-20380 Project: Camel Issue Type: Bug Components: camel-kafka Reporter: Andrea Cosentino Assignee: Otavio Rodolfo Piske As far as I see from some tests done on Camel-Kamelets, the poll timeout is not honored while batching. At least from my experiments, if you set a batch of 10 messages and poll timeout of 5000 ms, if you send one single message, it will be immediately sent to next step in the route, without waiting for poll timeout to end. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (CAMEL-20283) camel-elasticsearch - Deprecate
[ https://issues.apache.org/jira/browse/CAMEL-20283?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17811254#comment-17811254 ] Andrea Cosentino commented on CAMEL-20283: -- The other camel-elasticsearch-rest-client is based on https://search.maven.org/artifact/org.elasticsearch.client/elasticsearch-rest-client/8.12.0/jar and it's still ASF 2. So I don't think we have something to do. > camel-elasticsearch - Deprecate > --- > > Key: CAMEL-20283 > URL: https://issues.apache.org/jira/browse/CAMEL-20283 > Project: Camel > Issue Type: Task > Components: camel-elasticsearch >Reporter: Claus Ibsen >Assignee: Claus Ibsen >Priority: Major > Fix For: 4.4.0 > > > We should deprecate camel-elasticsearch as we have the new component that > does not have a license problem > See more at: https://issues.apache.org/jira/browse/CAMEL-15853 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (CAMEL-20283) camel-elasticsearch - Deprecate
[ https://issues.apache.org/jira/browse/CAMEL-20283?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17811252#comment-17811252 ] Andrea Cosentino commented on CAMEL-20283: -- https://search.maven.org/artifact/co.elastic.clients/elasticsearch-java/8.12.0/jar > camel-elasticsearch - Deprecate > --- > > Key: CAMEL-20283 > URL: https://issues.apache.org/jira/browse/CAMEL-20283 > Project: Camel > Issue Type: Task > Components: camel-elasticsearch >Reporter: Claus Ibsen >Assignee: Claus Ibsen >Priority: Major > Fix For: 4.4.0 > > > We should deprecate camel-elasticsearch as we have the new component that > does not have a license problem > See more at: https://issues.apache.org/jira/browse/CAMEL-15853 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (CAMEL-20283) camel-elasticsearch - Deprecate
[ https://issues.apache.org/jira/browse/CAMEL-20283?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17811251#comment-17811251 ] Andrea Cosentino commented on CAMEL-20283: -- I think this has been already done, the elasticsearch component we have is based on Java client ES 8 which is ASF 2. > camel-elasticsearch - Deprecate > --- > > Key: CAMEL-20283 > URL: https://issues.apache.org/jira/browse/CAMEL-20283 > Project: Camel > Issue Type: Task > Components: camel-elasticsearch >Reporter: Claus Ibsen >Assignee: Claus Ibsen >Priority: Major > Fix For: 4.4.0 > > > We should deprecate camel-elasticsearch as we have the new component that > does not have a license problem > See more at: https://issues.apache.org/jira/browse/CAMEL-15853 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (CAMEL-20336) Add a WebAssembly component and language
[ https://issues.apache.org/jira/browse/CAMEL-20336?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Cosentino resolved CAMEL-20336. -- Resolution: Fixed > Add a WebAssembly component and language > > > Key: CAMEL-20336 > URL: https://issues.apache.org/jira/browse/CAMEL-20336 > Project: Camel > Issue Type: New Feature >Reporter: Luca Burgazzoli >Assignee: Luca Burgazzoli >Priority: Minor > Fix For: 4.4.0 > > > I made a little > [POC|https://lburgazzoli.github.io/posts/2024-01-14_apache_camel_meets_wasm_part_1/] > to create a WebAssembly component and I think it would be nice to include it > in the official camel repo -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (CAMEL-20366) Dependabot: Define some exclusions in the yaml configuration
Andrea Cosentino created CAMEL-20366: Summary: Dependabot: Define some exclusions in the yaml configuration Key: CAMEL-20366 URL: https://issues.apache.org/jira/browse/CAMEL-20366 Project: Camel Issue Type: Task Reporter: Andrea Cosentino Assignee: Andrea Cosentino Fix For: 4.4.0 We need to add some exclusions to the dependabot configuration files and improve the list in the future. For example Vertx is a fundamental block of Quarkus and we should try to be in sync, while for example log4j should be kept in sync with Spring Boot Dependencies until we it aligns. At least for the beginning it would be important to add this exclusions. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (CAMEL-20362) Camel-Netty-HTTP: Headers validation should be enabled by default
[ https://issues.apache.org/jira/browse/CAMEL-20362?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Cosentino resolved CAMEL-20362. -- Resolution: Fixed > Camel-Netty-HTTP: Headers validation should be enabled by default > - > > Key: CAMEL-20362 > URL: https://issues.apache.org/jira/browse/CAMEL-20362 > Project: Camel > Issue Type: Bug > Components: camel-netty-http >Reporter: Andrea Cosentino >Assignee: Andrea Cosentino >Priority: Major > Fix For: 4.0.4, 4.4.0 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (CAMEL-20362) Camel-Netty-HTTP: Headers validation should be enabled by default
Andrea Cosentino created CAMEL-20362: Summary: Camel-Netty-HTTP: Headers validation should be enabled by default Key: CAMEL-20362 URL: https://issues.apache.org/jira/browse/CAMEL-20362 Project: Camel Issue Type: Bug Components: camel-netty-http Reporter: Andrea Cosentino Assignee: Andrea Cosentino Fix For: 4.0.4, 4.4.0 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (CAMEL-20357) camel-core - throttle EIP doesn't work as expected when it's in a loopDoWhile
[
https://issues.apache.org/jira/browse/CAMEL-20357?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17810204#comment-17810204
]
Andrea Cosentino commented on CAMEL-20357:
--
We usually consider major more important issues. This is a particular case but
it's not invalidating the possibility of using camel. If we mark everything as
major/critical there won't be a real priority list.
> camel-core - throttle EIP doesn't work as expected when it's in a loopDoWhile
> -
>
> Key: CAMEL-20357
> URL: https://issues.apache.org/jira/browse/CAMEL-20357
> Project: Camel
> Issue Type: Bug
> Components: camel-core
>Affects Versions: 4.3.0
>Reporter: Papa John
>Priority: Minor
>
> I just upgraded my project to Apache Camel 4.3.0, and my code stop to work as
> expected.
> It seems there was some changes to the `throttle EIP` – it's now throttling
> based on the number of concurrent exchanges.
> My route uses a {{`{*}loopDoWhile{*}`}} to loop an exchange over and over, so
> in a sense, the concurrent exchange should always be zero (and the inflight
> exchange is actually zero).
> However, my loop will stop when it reached the max number of concurrent
> exchanges I set for the thottler.
> For example, in the following code, the loop will stop at 10th iteration. It
> seems the new changes didn't put loop DSL into consideration...
> {code:java}
> import org.apache.camel.builder.RouteBuilder;public class Test extends
> RouteBuilder { @Override
> public void configure() throws Exception { // Write your routes
> here, for example:
> from("timer:java?delay=1000&repeatCount=1")
> .loopDoWhile(constant(true)).breakOnShutdown()
> .throttle(10)
> .setBody()
> .simple("Hello Camel from ${routeId}")
> .log("${body}");
> }
> } {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (CAMEL-8249) camel-keycloak - A security component
[ https://issues.apache.org/jira/browse/CAMEL-8249?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17809872#comment-17809872 ] Andrea Cosentino commented on CAMEL-8249: - In my opinion camel-keycloak should work in the same way as Camel-Spring-security does. This means leveraging Keycloak to allow execution of routes. Once we have that, we can think about supporting operations like read, create etc. But the original aim of the component should be authentication/authorization of routes execution. > camel-keycloak - A security component > - > > Key: CAMEL-8249 > URL: https://issues.apache.org/jira/browse/CAMEL-8249 > Project: Camel > Issue Type: New Feature >Reporter: Claus Ibsen >Priority: Major > Fix For: Future > > > We should have a camel-keycloak component that integrates with keycloak > https://www.keycloak.org/ > For example similar to as camel-spring-security > http://camel.apache.org/security > https://camel.apache.org/components/next/others/spring-security.html -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (CAMEL-20344) camel-spring-boot - Upgrade to 3.2.2
[ https://issues.apache.org/jira/browse/CAMEL-20344?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Cosentino resolved CAMEL-20344. -- Resolution: Fixed > camel-spring-boot - Upgrade to 3.2.2 > > > Key: CAMEL-20344 > URL: https://issues.apache.org/jira/browse/CAMEL-20344 > Project: Camel > Issue Type: Dependency upgrade > Components: camel-spring-boot >Reporter: Claus Ibsen >Assignee: Andrea Cosentino >Priority: Major > Fix For: 4.4.0 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (CAMEL-20344) camel-spring-boot - Upgrade to 3.2.2
[ https://issues.apache.org/jira/browse/CAMEL-20344?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Cosentino reassigned CAMEL-20344: Assignee: Andrea Cosentino > camel-spring-boot - Upgrade to 3.2.2 > > > Key: CAMEL-20344 > URL: https://issues.apache.org/jira/browse/CAMEL-20344 > Project: Camel > Issue Type: Dependency upgrade > Components: camel-spring-boot >Reporter: Claus Ibsen >Assignee: Andrea Cosentino >Priority: Major > Fix For: 4.4.0 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (CAMEL-20355) Throttle EIP: milliseconds not available anymore
[
https://issues.apache.org/jira/browse/CAMEL-20355?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17809404#comment-17809404
]
Andrea Cosentino commented on CAMEL-20355:
--
https://github.com/apache/camel-kamelets/issues/1842
> Throttle EIP: milliseconds not available anymore
>
>
> Key: CAMEL-20355
> URL: https://issues.apache.org/jira/browse/CAMEL-20355
> Project: Camel
> Issue Type: Bug
> Components: camel-k, camel-kamelet, documentation
>Affects Versions: 4.3.0
>Reporter: Raymond
>Priority: Minor
>
> Recently, the Throttle EIP was changed. For example, in this issue:
> https://issues.apache.org/jira/browse/CAMEL-16099
> Now the option "{*}timePeriodMillis{*}" isn't available anymore:
> [https://camel.apache.org/components/next/eips/throttle-eip.html]
> This is also documented in the migration guide:
> [https://camel.apache.org/manual/camel-4x-upgrade-guide-4_3.html]
> However:
> 1. The option is still there in the examples of the latest documentation
> 2. The option is still there in the Kamelet catalog (4.3.0):
> [https://github.com/apache/camel-kamelets/blob/main/kamelets/throttle-action.kamelet.yaml]
> When loading the throttle from the Kamelet catalog, I got the following
> message:
> {code:java}
> could not load: kamelets/throttle-action.kamelet.yaml. Reason: Field:
> timePeriodMillis has already been configured as an expression
> in throttle-action.kamelet.yaml, line 67, column 29:
> timePeriodMillis: "{{timePeriod}}" {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Comment Edited] (CAMEL-20281) Camel-AWS Components: Make it possible to use AwsSessionCredentials to support temporary credentials
[ https://issues.apache.org/jira/browse/CAMEL-20281?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17807707#comment-17807707 ] Andrea Cosentino edited comment on CAMEL-20281 at 1/22/24 11:51 AM: AWS S3 - Done AWS SQS - Done AWS SNS - Done AWS SES - Done was (Author: ancosen): AWS S3 - Done. > Camel-AWS Components: Make it possible to use AwsSessionCredentials to > support temporary credentials > > > Key: CAMEL-20281 > URL: https://issues.apache.org/jira/browse/CAMEL-20281 > Project: Camel > Issue Type: Improvement > Components: camel-aws >Reporter: Andrea Cosentino >Assignee: Andrea Cosentino >Priority: Major > Fix For: 4.x > > > This is really well explained through this: > https://repost.aws/knowledge-center/iam-assume-role-cli > Essentially it could be the case, we want a user to be able to do some > operations and having temporary credentials. As of today, we don't offer a > way of creating AWS sessions credentials and I think it's a good use case. > So the idea is introducing another option useSessionsCredentials and improve > the client factories we have. That way a user would be able to use this > kamelet correctly for example: > https://github.com/apache/camel-kamelets/blob/main/kamelets/aws-sts-assume-role-action.kamelet.yaml -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (CAMEL-20047) camel-langchain4j - Camel AI assisted
[ https://issues.apache.org/jira/browse/CAMEL-20047?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17808186#comment-17808186 ] Andrea Cosentino commented on CAMEL-20047: -- Maybe sync with [~zbendhiba] on https://issues.apache.org/jira/browse/CAMEL-20095 because I think it's the same. > camel-langchain4j - Camel AI assisted > - > > Key: CAMEL-20047 > URL: https://issues.apache.org/jira/browse/CAMEL-20047 > Project: Camel > Issue Type: New Feature >Reporter: Claus Ibsen >Assignee: Peter Palaga >Priority: Major > Fix For: 4.x > > > Research this tweet > https://x.com/rbrtwnklr/status/1716066425322799517?s=20 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Work started] (CAMEL-19241) Adding a Kafka Batch Consumer
[ https://issues.apache.org/jira/browse/CAMEL-19241?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on CAMEL-19241 started by Andrea Cosentino. > Adding a Kafka Batch Consumer > - > > Key: CAMEL-19241 > URL: https://issues.apache.org/jira/browse/CAMEL-19241 > Project: Camel > Issue Type: New Feature > Components: camel-kafka >Reporter: Andrea Cosentino >Assignee: Andrea Cosentino >Priority: Major > Fix For: 4.4.0 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (CAMEL-20281) Camel-AWS Components: Make it possible to use AwsSessionCredentials to support temporary credentials
[ https://issues.apache.org/jira/browse/CAMEL-20281?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17807707#comment-17807707 ] Andrea Cosentino commented on CAMEL-20281: -- AWS S3 - Done. > Camel-AWS Components: Make it possible to use AwsSessionCredentials to > support temporary credentials > > > Key: CAMEL-20281 > URL: https://issues.apache.org/jira/browse/CAMEL-20281 > Project: Camel > Issue Type: Improvement > Components: camel-aws >Reporter: Andrea Cosentino >Assignee: Andrea Cosentino >Priority: Major > Fix For: 4.x > > > This is really well explained through this: > https://repost.aws/knowledge-center/iam-assume-role-cli > Essentially it could be the case, we want a user to be able to do some > operations and having temporary credentials. As of today, we don't offer a > way of creating AWS sessions credentials and I think it's a good use case. > So the idea is introducing another option useSessionsCredentials and improve > the client factories we have. That way a user would be able to use this > kamelet correctly for example: > https://github.com/apache/camel-kamelets/blob/main/kamelets/aws-sts-assume-role-action.kamelet.yaml -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (CAMEL-20306) Camel-CassandraQL: Add ObjectInputFilter String pattern parameter in CassandraAggregationRepository to be used in unmarshall operations
[ https://issues.apache.org/jira/browse/CAMEL-20306?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Cosentino resolved CAMEL-20306. -- Resolution: Fixed > Camel-CassandraQL: Add ObjectInputFilter String pattern parameter in > CassandraAggregationRepository to be used in unmarshall operations > --- > > Key: CAMEL-20306 > URL: https://issues.apache.org/jira/browse/CAMEL-20306 > Project: Camel > Issue Type: Improvement > Components: camel-cassandraql >Reporter: Andrea Cosentino >Assignee: Andrea Cosentino >Priority: Major > Fix For: 3.21.4, 3.x, 4.0.4, 4.4.0, 3.22.1 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (CAMEL-18276) azure-service-bus component does not support session
[ https://issues.apache.org/jira/browse/CAMEL-18276?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Cosentino updated CAMEL-18276: - Fix Version/s: 4.x (was: Future) > azure-service-bus component does not support session > > > Key: CAMEL-18276 > URL: https://issues.apache.org/jira/browse/CAMEL-18276 > Project: Camel > Issue Type: New Feature > Components: camel-azure >Affects Versions: 3.18.0 >Reporter: Jean-Benoît >Priority: Minor > Fix For: 4.x > > > Hello, > From what I could tell, the azure-servicebus component does not support > sessions. Any chance this can be added in an upcoming release? -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (CAMEL-20306) Camel-CassandraQL: Add ObjectInputFilter String pattern parameter in CassandraAggregationRepository to be used in unmarshall operations
[ https://issues.apache.org/jira/browse/CAMEL-20306?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Cosentino updated CAMEL-20306: - Fix Version/s: 3.22.1 > Camel-CassandraQL: Add ObjectInputFilter String pattern parameter in > CassandraAggregationRepository to be used in unmarshall operations > --- > > Key: CAMEL-20306 > URL: https://issues.apache.org/jira/browse/CAMEL-20306 > Project: Camel > Issue Type: Improvement > Components: camel-cassandraql >Reporter: Andrea Cosentino >Assignee: Andrea Cosentino >Priority: Major > Fix For: 3.21.4, 3.x, 4.0.4, 4.4.0, 3.22.1 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (CAMEL-20303) Camel-Sql: Add ObjectInputFilter String pattern parameter in JdbcAggregationRepository to be used in unmarshall operations
[ https://issues.apache.org/jira/browse/CAMEL-20303?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Cosentino updated CAMEL-20303: - Fix Version/s: 3.22.1 > Camel-Sql: Add ObjectInputFilter String pattern parameter in > JdbcAggregationRepository to be used in unmarshall operations > -- > > Key: CAMEL-20303 > URL: https://issues.apache.org/jira/browse/CAMEL-20303 > Project: Camel > Issue Type: Improvement >Reporter: Andrea Cosentino >Assignee: Andrea Cosentino >Priority: Major > Fix For: 3.21.4, 3.x, 4.0.4, 4.4.0, 3.22.1 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (CAMEL-20218) KafkaIdempotentRepository cache incorrectly flagged as ready
[ https://issues.apache.org/jira/browse/CAMEL-20218?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17806143#comment-17806143 ] Andrea Cosentino commented on CAMEL-20218: -- Assigning issues is a permissions given to frequent and continuos contributors usually. We often grant that to contributors after some contributions. > KafkaIdempotentRepository cache incorrectly flagged as ready > > > Key: CAMEL-20218 > URL: https://issues.apache.org/jira/browse/CAMEL-20218 > Project: Camel > Issue Type: Bug > Components: camel-kafka >Affects Versions: 4.2.0 >Reporter: Andrea Tarocchi >Priority: Major > > This is a reopening of [#CAMEL-16181] -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (CAMEL-20334) AWS S3 cloudevents data type does not set proper data Content-Type
[
https://issues.apache.org/jira/browse/CAMEL-20334?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrea Cosentino resolved CAMEL-20334.
--
Resolution: Fixed
> AWS S3 cloudevents data type does not set proper data Content-Type
> --
>
> Key: CAMEL-20334
> URL: https://issues.apache.org/jira/browse/CAMEL-20334
> Project: Camel
> Issue Type: Bug
> Components: camel-aws2
>Affects Versions: 4.3.0
>Reporter: Christoph Deppisch
>Assignee: Andrea Cosentino
>Priority: Major
> Fix For: 4.4.0
>
>
> Having a {{Kamelet}} / {{{}Pipe{}}}, such as:
>
> apiVersion: camel.apache.org/v1kind: Pipemetadata: name:
> aws-s3-source-pipeannotations:
> trait.camel.apache.org/camel.runtime-version: 3.6.0spec: integration:
> dependencies:
> - "camel:cloudevents"source:ref: kind: KameletapiVersion:
> camel.apache.org/v1name: aws-s3-sourceproperties: ... some
> secretsdataTypes: out:scheme: aws2-s3format:
> application-cloudeventssink:dataTypes: in:scheme:
> httpformat: application-cloudeventsref: kind: BrokerapiVersion:
> eventing.knative.dev/v1name: kamelet
>
> I get the following exception from Quarkus Funqy, when trying to process the
> emitted Cloudevents:
> {noformat}
> 2024-01-11 16:09:51,563 ERROR [io.qua.ver.htt.run.QuarkusErrorHandler]
> (executor-thread-1) HTTP Request to / failed, error id:
> af846418-99ec-4a1a-a4af-ec9192906b2f-1:
> io.quarkus.funqy.runtime.ApplicationException: java.lang.RuntimeException:
> Don't know how to get event data (dataContentType: 'null', javaType:
> 'functions.Input').
> test-four-1-deployment-6b5d6c7f69-flk8p user-container at
> io.quarkus.funqy.runtime.FunctionInvoker.invoke(FunctionInvoker.java:136)
> test-four-1-deployment-6b5d6c7f69-flk8p user-container at
> io.quarkus.funqy.runtime.bindings.knative.events.VertxRequestHandler.dispatch(VertxRequestHandler.java:571){noformat}
> I see similar then I have a different (e.g. {{{}go{}}}) receiver that prints
> the request:
> {noformat}
> test-three-1-deployment-54dc897c99-2qgzk user-container Received request
> test-three-1-deployment-54dc897c99-2qgzk user-container POST / HTTP/1.1
> test-three.default.svc.cluster.local
> test-three-1-deployment-54dc897c99-2qgzk user-container Ce-Id:
> 8B49F74E586030C-0009
> test-three-1-deployment-54dc897c99-2qgzk user-container Ce-Specversion:
> 1.0
> test-three-1-deployment-54dc897c99-2qgzk user-container
> X-Forwarded-For: 10.244.0.23, 10.244.0.18
> test-three-1-deployment-54dc897c99-2qgzk user-container User-Agent:
> Go-http-client/1.1
> test-three-1-deployment-54dc897c99-2qgzk user-container Ce-Subject:
> IMG_3339.jpg
> test-three-1-deployment-54dc897c99-2qgzk user-container Ce-Time:
> 2024-01-11T15:08:42.013Z
> test-three-1-deployment-54dc897c99-2qgzk user-container Forwarded:
> for=10.244.0.23;proto=http
> test-three-1-deployment-54dc897c99-2qgzk user-container Prefer: reply
> test-three-1-deployment-54dc897c99-2qgzk user-container
> Accept-Encoding: gzip
> test-three-1-deployment-54dc897c99-2qgzk user-container Ce-Type:
> org.apache.camel.event.
> test-three-1-deployment-54dc897c99-2qgzk user-container X-Request-Id:
> 2946fb28-f697-4406-9e71-80fb30e3b99a
> test-three-1-deployment-54dc897c99-2qgzk user-container Content-Length:
> 883527
> test-three-1-deployment-54dc897c99-2qgzk user-container
> Ce-Knativearrivaltime: 2024-01-11T15:08:42.188499068Z
> test-three-1-deployment-54dc897c99-2qgzk user-container Ce-Source:
> .bucket.foobar
> test-three-1-deployment-54dc897c99-2qgzk user-container
> K-Proxy-Request: activator
> test-three-1-deployment-54dc897c99-2qgzk user-container Kn-Namespace:
> default
> test-three-1-deployment-54dc897c99-2qgzk user-container Traceparent:
> 00-7ce27116bb576a804f841c7892e8f245-d3e77ecd9906bffa-00
> test-three-1-deployment-54dc897c99-2qgzk user-container
> X-Forwarded-Proto: http{noformat}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Assigned] (CAMEL-20334) AWS S3 cloudevents data type does not set proper data Content-Type
[
https://issues.apache.org/jira/browse/CAMEL-20334?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrea Cosentino reassigned CAMEL-20334:
Assignee: Andrea Cosentino
> AWS S3 cloudevents data type does not set proper data Content-Type
> --
>
> Key: CAMEL-20334
> URL: https://issues.apache.org/jira/browse/CAMEL-20334
> Project: Camel
> Issue Type: Bug
> Components: camel-aws2
>Affects Versions: 4.3.0
>Reporter: Christoph Deppisch
>Assignee: Andrea Cosentino
>Priority: Major
> Fix For: 4.4.0
>
>
> Having a {{Kamelet}} / {{{}Pipe{}}}, such as:
>
> apiVersion: camel.apache.org/v1kind: Pipemetadata: name:
> aws-s3-source-pipeannotations:
> trait.camel.apache.org/camel.runtime-version: 3.6.0spec: integration:
> dependencies:
> - "camel:cloudevents"source:ref: kind: KameletapiVersion:
> camel.apache.org/v1name: aws-s3-sourceproperties: ... some
> secretsdataTypes: out:scheme: aws2-s3format:
> application-cloudeventssink:dataTypes: in:scheme:
> httpformat: application-cloudeventsref: kind: BrokerapiVersion:
> eventing.knative.dev/v1name: kamelet
>
> I get the following exception from Quarkus Funqy, when trying to process the
> emitted Cloudevents:
> {noformat}
> 2024-01-11 16:09:51,563 ERROR [io.qua.ver.htt.run.QuarkusErrorHandler]
> (executor-thread-1) HTTP Request to / failed, error id:
> af846418-99ec-4a1a-a4af-ec9192906b2f-1:
> io.quarkus.funqy.runtime.ApplicationException: java.lang.RuntimeException:
> Don't know how to get event data (dataContentType: 'null', javaType:
> 'functions.Input').
> test-four-1-deployment-6b5d6c7f69-flk8p user-container at
> io.quarkus.funqy.runtime.FunctionInvoker.invoke(FunctionInvoker.java:136)
> test-four-1-deployment-6b5d6c7f69-flk8p user-container at
> io.quarkus.funqy.runtime.bindings.knative.events.VertxRequestHandler.dispatch(VertxRequestHandler.java:571){noformat}
> I see similar then I have a different (e.g. {{{}go{}}}) receiver that prints
> the request:
> {noformat}
> test-three-1-deployment-54dc897c99-2qgzk user-container Received request
> test-three-1-deployment-54dc897c99-2qgzk user-container POST / HTTP/1.1
> test-three.default.svc.cluster.local
> test-three-1-deployment-54dc897c99-2qgzk user-container Ce-Id:
> 8B49F74E586030C-0009
> test-three-1-deployment-54dc897c99-2qgzk user-container Ce-Specversion:
> 1.0
> test-three-1-deployment-54dc897c99-2qgzk user-container
> X-Forwarded-For: 10.244.0.23, 10.244.0.18
> test-three-1-deployment-54dc897c99-2qgzk user-container User-Agent:
> Go-http-client/1.1
> test-three-1-deployment-54dc897c99-2qgzk user-container Ce-Subject:
> IMG_3339.jpg
> test-three-1-deployment-54dc897c99-2qgzk user-container Ce-Time:
> 2024-01-11T15:08:42.013Z
> test-three-1-deployment-54dc897c99-2qgzk user-container Forwarded:
> for=10.244.0.23;proto=http
> test-three-1-deployment-54dc897c99-2qgzk user-container Prefer: reply
> test-three-1-deployment-54dc897c99-2qgzk user-container
> Accept-Encoding: gzip
> test-three-1-deployment-54dc897c99-2qgzk user-container Ce-Type:
> org.apache.camel.event.
> test-three-1-deployment-54dc897c99-2qgzk user-container X-Request-Id:
> 2946fb28-f697-4406-9e71-80fb30e3b99a
> test-three-1-deployment-54dc897c99-2qgzk user-container Content-Length:
> 883527
> test-three-1-deployment-54dc897c99-2qgzk user-container
> Ce-Knativearrivaltime: 2024-01-11T15:08:42.188499068Z
> test-three-1-deployment-54dc897c99-2qgzk user-container Ce-Source:
> .bucket.foobar
> test-three-1-deployment-54dc897c99-2qgzk user-container
> K-Proxy-Request: activator
> test-three-1-deployment-54dc897c99-2qgzk user-container Kn-Namespace:
> default
> test-three-1-deployment-54dc897c99-2qgzk user-container Traceparent:
> 00-7ce27116bb576a804f841c7892e8f245-d3e77ecd9906bffa-00
> test-three-1-deployment-54dc897c99-2qgzk user-container
> X-Forwarded-Proto: http{noformat}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (CAMEL-20334) AWS S3 cloudevents data type does not set proper data Content-Type
[
https://issues.apache.org/jira/browse/CAMEL-20334?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrea Cosentino updated CAMEL-20334:
-
Fix Version/s: 4.4.0
> AWS S3 cloudevents data type does not set proper data Content-Type
> --
>
> Key: CAMEL-20334
> URL: https://issues.apache.org/jira/browse/CAMEL-20334
> Project: Camel
> Issue Type: Bug
> Components: camel-aws2
>Affects Versions: 4.3.0
>Reporter: Christoph Deppisch
>Priority: Major
> Fix For: 4.4.0
>
>
> Having a {{Kamelet}} / {{{}Pipe{}}}, such as:
>
> apiVersion: camel.apache.org/v1kind: Pipemetadata: name:
> aws-s3-source-pipeannotations:
> trait.camel.apache.org/camel.runtime-version: 3.6.0spec: integration:
> dependencies:
> - "camel:cloudevents"source:ref: kind: KameletapiVersion:
> camel.apache.org/v1name: aws-s3-sourceproperties: ... some
> secretsdataTypes: out:scheme: aws2-s3format:
> application-cloudeventssink:dataTypes: in:scheme:
> httpformat: application-cloudeventsref: kind: BrokerapiVersion:
> eventing.knative.dev/v1name: kamelet
>
> I get the following exception from Quarkus Funqy, when trying to process the
> emitted Cloudevents:
> {noformat}
> 2024-01-11 16:09:51,563 ERROR [io.qua.ver.htt.run.QuarkusErrorHandler]
> (executor-thread-1) HTTP Request to / failed, error id:
> af846418-99ec-4a1a-a4af-ec9192906b2f-1:
> io.quarkus.funqy.runtime.ApplicationException: java.lang.RuntimeException:
> Don't know how to get event data (dataContentType: 'null', javaType:
> 'functions.Input').
> test-four-1-deployment-6b5d6c7f69-flk8p user-container at
> io.quarkus.funqy.runtime.FunctionInvoker.invoke(FunctionInvoker.java:136)
> test-four-1-deployment-6b5d6c7f69-flk8p user-container at
> io.quarkus.funqy.runtime.bindings.knative.events.VertxRequestHandler.dispatch(VertxRequestHandler.java:571){noformat}
> I see similar then I have a different (e.g. {{{}go{}}}) receiver that prints
> the request:
> {noformat}
> test-three-1-deployment-54dc897c99-2qgzk user-container Received request
> test-three-1-deployment-54dc897c99-2qgzk user-container POST / HTTP/1.1
> test-three.default.svc.cluster.local
> test-three-1-deployment-54dc897c99-2qgzk user-container Ce-Id:
> 8B49F74E586030C-0009
> test-three-1-deployment-54dc897c99-2qgzk user-container Ce-Specversion:
> 1.0
> test-three-1-deployment-54dc897c99-2qgzk user-container
> X-Forwarded-For: 10.244.0.23, 10.244.0.18
> test-three-1-deployment-54dc897c99-2qgzk user-container User-Agent:
> Go-http-client/1.1
> test-three-1-deployment-54dc897c99-2qgzk user-container Ce-Subject:
> IMG_3339.jpg
> test-three-1-deployment-54dc897c99-2qgzk user-container Ce-Time:
> 2024-01-11T15:08:42.013Z
> test-three-1-deployment-54dc897c99-2qgzk user-container Forwarded:
> for=10.244.0.23;proto=http
> test-three-1-deployment-54dc897c99-2qgzk user-container Prefer: reply
> test-three-1-deployment-54dc897c99-2qgzk user-container
> Accept-Encoding: gzip
> test-three-1-deployment-54dc897c99-2qgzk user-container Ce-Type:
> org.apache.camel.event.
> test-three-1-deployment-54dc897c99-2qgzk user-container X-Request-Id:
> 2946fb28-f697-4406-9e71-80fb30e3b99a
> test-three-1-deployment-54dc897c99-2qgzk user-container Content-Length:
> 883527
> test-three-1-deployment-54dc897c99-2qgzk user-container
> Ce-Knativearrivaltime: 2024-01-11T15:08:42.188499068Z
> test-three-1-deployment-54dc897c99-2qgzk user-container Ce-Source:
> .bucket.foobar
> test-three-1-deployment-54dc897c99-2qgzk user-container
> K-Proxy-Request: activator
> test-three-1-deployment-54dc897c99-2qgzk user-container Kn-Namespace:
> default
> test-three-1-deployment-54dc897c99-2qgzk user-container Traceparent:
> 00-7ce27116bb576a804f841c7892e8f245-d3e77ecd9906bffa-00
> test-three-1-deployment-54dc897c99-2qgzk user-container
> X-Forwarded-Proto: http{noformat}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (CAMEL-20306) Camel-CassandraQL: Add ObjectInputFilter String pattern parameter in CassandraAggregationRepository to be used in unmarshall operations
[ https://issues.apache.org/jira/browse/CAMEL-20306?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Cosentino updated CAMEL-20306: - Fix Version/s: 3.21.4 3.x 4.0.4 > Camel-CassandraQL: Add ObjectInputFilter String pattern parameter in > CassandraAggregationRepository to be used in unmarshall operations > --- > > Key: CAMEL-20306 > URL: https://issues.apache.org/jira/browse/CAMEL-20306 > Project: Camel > Issue Type: Improvement > Components: camel-cassandraql >Reporter: Andrea Cosentino >Assignee: Andrea Cosentino >Priority: Major > Fix For: 3.21.4, 3.x, 4.0.4, 4.4.0 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (CAMEL-8249) camel-keycloak - A security component
[ https://issues.apache.org/jira/browse/CAMEL-8249?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17805430#comment-17805430 ] Andrea Cosentino commented on CAMEL-8249: - Updated. I don't know if [~vmanel] is working on that or not, but it is from May we don't have news about this issue. > camel-keycloak - A security component > - > > Key: CAMEL-8249 > URL: https://issues.apache.org/jira/browse/CAMEL-8249 > Project: Camel > Issue Type: New Feature >Reporter: Claus Ibsen >Priority: Major > Fix For: Future > > > We should have a camel-keycloak component that integrates with keycloak > https://www.keycloak.org/ > For example similar to as camel-spring-security > http://camel.apache.org/security > https://camel.apache.org/components/next/others/spring-security.html -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (CAMEL-8249) camel-keycloak - A security component
[ https://issues.apache.org/jira/browse/CAMEL-8249?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Cosentino updated CAMEL-8249: Description: We should have a camel-keycloak component that integrates with keycloak https://www.keycloak.org/ For example similar to as camel-spring-security http://camel.apache.org/security https://camel.apache.org/components/next/others/spring-security.html was: We should have a camel-keycloak component that integrates with keycloak http://keycloak.jboss.org/ For example similar to as camel-spring-security http://camel.apache.org/security http://camel.apache.org/spring-security.html > camel-keycloak - A security component > - > > Key: CAMEL-8249 > URL: https://issues.apache.org/jira/browse/CAMEL-8249 > Project: Camel > Issue Type: New Feature >Reporter: Claus Ibsen >Priority: Major > Fix For: Future > > > We should have a camel-keycloak component that integrates with keycloak > https://www.keycloak.org/ > For example similar to as camel-spring-security > http://camel.apache.org/security > https://camel.apache.org/components/next/others/spring-security.html -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (CAMEL-20095) Create a component for OpenAI
[ https://issues.apache.org/jira/browse/CAMEL-20095?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17805150#comment-17805150 ] Andrea Cosentino commented on CAMEL-20095: -- Yes, something like that... Langchain4j got multiple modules: https://github.com/langchain4j/langchain4j So it would maybe make sense to focus on one module at the time, for example adding the azure-open-ai one in camel-azure and maybe the chatgpt in the camel-ai middle folder. > Create a component for OpenAI > - > > Key: CAMEL-20095 > URL: https://issues.apache.org/jira/browse/CAMEL-20095 > Project: Camel > Issue Type: New Feature >Reporter: Zineb Bendhiba >Assignee: Zineb Bendhiba >Priority: Major > Attachments: telegram-openAPI.mp4 > > > Investigate on the Java library langchain4j, to create a component that can > integrate to OpenAI, HugginFace and more via langchain > > This is the link to the project : [https://github.com/langchain4j/langchain4j] > > the attached video is a first POC playing with Camel telegram and OpenAI > > [^telegram-openAPI.mp4] -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (CAMEL-20095) Create a component for OpenAI
[ https://issues.apache.org/jira/browse/CAMEL-20095?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17805133#comment-17805133 ] Andrea Cosentino commented on CAMEL-20095: -- [~zbendhiba] what component of langchain you're looking at now? > Create a component for OpenAI > - > > Key: CAMEL-20095 > URL: https://issues.apache.org/jira/browse/CAMEL-20095 > Project: Camel > Issue Type: New Feature >Reporter: Zineb Bendhiba >Assignee: Zineb Bendhiba >Priority: Major > Attachments: telegram-openAPI.mp4 > > > Investigate on the Java library langchain4j, to create a component that can > integrate to OpenAI, HugginFace and more via langchain > > This is the link to the project : [https://github.com/langchain4j/langchain4j] > > the attached video is a first POC playing with Camel telegram and OpenAI > > [^telegram-openAPI.mp4] -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Comment Edited] (CAMEL-20307) camel-quickfix -Queue Full
[
https://issues.apache.org/jira/browse/CAMEL-20307?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17805024#comment-17805024
]
Andrea Cosentino edited comment on CAMEL-20307 at 1/10/24 9:01 AM:
---
If you need help, please write on zulip chat or in the mailing list. The JIRA
issue tracker is for real issues and not for questions.
was (Author: ancosen):
If you need help, please write on zulip chat or in the mailing list. The JIRA
issue tracker is fore real issues.
> camel-quickfix -Queue Full
> --
>
> Key: CAMEL-20307
> URL: https://issues.apache.org/jira/browse/CAMEL-20307
> Project: Camel
> Issue Type: Bug
> Components: camel-quickfix
>Affects Versions: 2.25.2
> Environment: Jdk-1.8 and Linux environment
>Reporter: AjayPatil2611
>Priority: Blocker
> Fix For: 4.4.0
>
> Attachments: Queue Full.JPG, QuickFix-QueueFull.JPG
>
>
> Our application is connected to Fedissa Broker via a camel application. So
> whenever we place an order to Fedissa for multiple quantities (sometimes bulk
> orders), we are getting "{*}Queue Full{*}" error in camel application (PFA).
> Can you please help with this? Also note that we are using Seda and wireTap
> in the application to connect each internal endpoint in the routes.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Resolved] (CAMEL-20307) camel-quickfix -Queue Full
[ https://issues.apache.org/jira/browse/CAMEL-20307?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Cosentino resolved CAMEL-20307. -- Resolution: Invalid > camel-quickfix -Queue Full > -- > > Key: CAMEL-20307 > URL: https://issues.apache.org/jira/browse/CAMEL-20307 > Project: Camel > Issue Type: Bug > Components: camel-quickfix >Affects Versions: 2.25.2 > Environment: Jdk-1.8 and Linux environment >Reporter: AjayPatil2611 >Priority: Blocker > Fix For: 4.4.0 > > Attachments: Queue Full.JPG, QuickFix-QueueFull.JPG > > > Our application is connected to Fedissa Broker via a camel application. So > whenever we place an order to Fedissa for multiple quantities (sometimes bulk > orders), we are getting Queue Full in camel application. Can you please help > with this? Also note that we are using Seda and wireTap in the application to > connect each internal endpoint in the routes. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (CAMEL-20307) camel-quickfix -Queue Full
[ https://issues.apache.org/jira/browse/CAMEL-20307?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17805024#comment-17805024 ] Andrea Cosentino commented on CAMEL-20307: -- If you need help, please write on zulip chat or in the mailing list. The JIRA issue tracker is fore real issues. > camel-quickfix -Queue Full > -- > > Key: CAMEL-20307 > URL: https://issues.apache.org/jira/browse/CAMEL-20307 > Project: Camel > Issue Type: Bug > Components: camel-quickfix >Affects Versions: 2.25.2 > Environment: Jdk-1.8 and Linux environment >Reporter: AjayPatil2611 >Priority: Blocker > Fix For: 4.4.0 > > Attachments: Queue Full.JPG, QuickFix-QueueFull.JPG > > > Our application is connected to Fedissa Broker via a camel application. So > whenever we place an order to Fedissa for multiple quantities (sometimes bulk > orders), we are getting Queue Full in camel application. Can you please help > with this? Also note that we are using Seda and wireTap in the application to > connect each internal endpoint in the routes. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (CAMEL-20306) Camel-CassandraQL: Add ObjectInputFilter String pattern parameter in CassandraAggregationRepository to be used in unmarshall operations
Andrea Cosentino created CAMEL-20306: Summary: Camel-CassandraQL: Add ObjectInputFilter String pattern parameter in CassandraAggregationRepository to be used in unmarshall operations Key: CAMEL-20306 URL: https://issues.apache.org/jira/browse/CAMEL-20306 Project: Camel Issue Type: Improvement Components: camel-cassandraql Reporter: Andrea Cosentino Assignee: Andrea Cosentino Fix For: 4.4.0 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (CAMEL-20298) Enhancing JSONata Compatibility for Full Reference Port
[
https://issues.apache.org/jira/browse/CAMEL-20298?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrea Cosentino resolved CAMEL-20298.
--
Resolution: Fixed
> Enhancing JSONata Compatibility for Full Reference Port
> ---
>
> Key: CAMEL-20298
> URL: https://issues.apache.org/jira/browse/CAMEL-20298
> Project: Camel
> Issue Type: Improvement
>Affects Versions: 3.22.0, 4.0.3, 4.3.0
>Reporter: Otávio Prado
>Assignee: Andrea Cosentino
>Priority: Minor
> Fix For: 4.4.0
>
>
> When attempting to use the expression Email#$i[$i>0] in the Camel JSONata
> component the error is as follows:
> {code:java}
> line 4:19 at null: token recognition error at: '#', line 4:20 at
> [@23,106:107='$i',<47>,4:20]: mismatched input '$i' expecting {'.', ',',
> 'in', '?', '[', '{', '}', '~>', '*', '/', '+', '-', '%', '=', '!=', '<',
> '<=', '>', '>=', '&', '^', 'and', 'or'} {code}
> This error occurs because the IBM JSONata library does not fully implement
> the JSONata specification as defined in the reference implementation:
> [JSONata Reference Implementation|https://github.com/jsonata-js/jsonata].
> It prevents us from validating and ensuring compatibility with the JSONata
> specification, impacting the reliability and quality of our component.
> *Proposed Solution:* To address this issue, we need to either modify the IBM
> JSONata library to fully adhere to the JSONata specification or consider
> alternative libraries that provide full compatibility. We will evaluate the
> best course of action to ensure that our Camel JSONata component works
> seamlessly with JSONata expressions.
> *Additional Information:*
> * Affected Component: Camel JSONata
> * Current Library: IBM JSONata
> * JSONata Specification: [JSONata Reference
> Implementation|https://github.com/jsonata-js/jsonata]
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Assigned] (CAMEL-20298) Enhancing JSONata Compatibility for Full Reference Port
[
https://issues.apache.org/jira/browse/CAMEL-20298?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrea Cosentino reassigned CAMEL-20298:
Assignee: Andrea Cosentino
> Enhancing JSONata Compatibility for Full Reference Port
> ---
>
> Key: CAMEL-20298
> URL: https://issues.apache.org/jira/browse/CAMEL-20298
> Project: Camel
> Issue Type: Improvement
>Affects Versions: 3.22.0, 4.0.3, 4.3.0
>Reporter: Otávio Prado
>Assignee: Andrea Cosentino
>Priority: Minor
> Fix For: 4.4.0
>
>
> When attempting to use the expression Email#$i[$i>0] in the Camel JSONata
> component the error is as follows:
> {code:java}
> line 4:19 at null: token recognition error at: '#', line 4:20 at
> [@23,106:107='$i',<47>,4:20]: mismatched input '$i' expecting {'.', ',',
> 'in', '?', '[', '{', '}', '~>', '*', '/', '+', '-', '%', '=', '!=', '<',
> '<=', '>', '>=', '&', '^', 'and', 'or'} {code}
> This error occurs because the IBM JSONata library does not fully implement
> the JSONata specification as defined in the reference implementation:
> [JSONata Reference Implementation|https://github.com/jsonata-js/jsonata].
> It prevents us from validating and ensuring compatibility with the JSONata
> specification, impacting the reliability and quality of our component.
> *Proposed Solution:* To address this issue, we need to either modify the IBM
> JSONata library to fully adhere to the JSONata specification or consider
> alternative libraries that provide full compatibility. We will evaluate the
> best course of action to ensure that our Camel JSONata component works
> seamlessly with JSONata expressions.
> *Additional Information:*
> * Affected Component: Camel JSONata
> * Current Library: IBM JSONata
> * JSONata Specification: [JSONata Reference
> Implementation|https://github.com/jsonata-js/jsonata]
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Resolved] (CAMEL-20303) Camel-Sql: Add ObjectInputFilter String pattern parameter in JdbcAggregationRepository to be used in unmarshall operations
[ https://issues.apache.org/jira/browse/CAMEL-20303?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Cosentino resolved CAMEL-20303. -- Resolution: Fixed > Camel-Sql: Add ObjectInputFilter String pattern parameter in > JdbcAggregationRepository to be used in unmarshall operations > -- > > Key: CAMEL-20303 > URL: https://issues.apache.org/jira/browse/CAMEL-20303 > Project: Camel > Issue Type: Improvement >Reporter: Andrea Cosentino >Assignee: Andrea Cosentino >Priority: Major > Fix For: 3.21.4, 3.x, 4.0.4, 4.4.0 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (CAMEL-20303) Camel-Sql: Add ObjectInputFilter String pattern parameter in JdbcAggregationRepository to be used in unmarshall operations
[ https://issues.apache.org/jira/browse/CAMEL-20303?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Cosentino updated CAMEL-20303: - Fix Version/s: 4.0.4 > Camel-Sql: Add ObjectInputFilter String pattern parameter in > JdbcAggregationRepository to be used in unmarshall operations > -- > > Key: CAMEL-20303 > URL: https://issues.apache.org/jira/browse/CAMEL-20303 > Project: Camel > Issue Type: Improvement >Reporter: Andrea Cosentino >Assignee: Andrea Cosentino >Priority: Major > Fix For: 3.21.4, 3.x, 4.0.4, 4.4.0 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (CAMEL-20303) Camel-Sql: Add ObjectInputFilter String pattern parameter in JdbcAggregationRepository to be used in unmarshall operations
[ https://issues.apache.org/jira/browse/CAMEL-20303?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Cosentino updated CAMEL-20303: - Fix Version/s: 3.21.4 3.x > Camel-Sql: Add ObjectInputFilter String pattern parameter in > JdbcAggregationRepository to be used in unmarshall operations > -- > > Key: CAMEL-20303 > URL: https://issues.apache.org/jira/browse/CAMEL-20303 > Project: Camel > Issue Type: Improvement >Reporter: Andrea Cosentino >Assignee: Andrea Cosentino >Priority: Major > Fix For: 3.21.4, 3.x, 4.4.0 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (CAMEL-20303) Camel-Sql: Add ObjectInputFilter String pattern parameter in JdbcAggregationRepository to be used in unmarshall operations
Andrea Cosentino created CAMEL-20303: Summary: Camel-Sql: Add ObjectInputFilter String pattern parameter in JdbcAggregationRepository to be used in unmarshall operations Key: CAMEL-20303 URL: https://issues.apache.org/jira/browse/CAMEL-20303 Project: Camel Issue Type: Improvement Reporter: Andrea Cosentino Assignee: Andrea Cosentino Fix For: 4.4.0 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (CAMEL-20294) camel-facebook: review and/or deprecate
[ https://issues.apache.org/jira/browse/CAMEL-20294?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17804206#comment-17804206 ] Andrea Cosentino commented on CAMEL-20294: -- We should deprecate that, but we are going to still have it in Camel 4.4.0 if we deprecate it now, so it will be in LTS, which it's not good. > camel-facebook: review and/or deprecate > --- > > Key: CAMEL-20294 > URL: https://issues.apache.org/jira/browse/CAMEL-20294 > Project: Camel > Issue Type: Task > Components: camel-facebook >Reporter: Otavio Rodolfo Piske >Assignee: Otavio Rodolfo Piske >Priority: Major > Fix For: 4.4.0 > > > The [project|https://github.com/roundrop/facebook4j] supporting > camel-facebook seems unmaintained and there are no commits for 6 years and no > community activity either. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (CAMEL-20281) Camel-AWS Components: Make it possible to use AwsSessionCredentials to support temporary credentials
[ https://issues.apache.org/jira/browse/CAMEL-20281?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17799831#comment-17799831 ] Andrea Cosentino commented on CAMEL-20281: -- So you might think about a user with no permissions (beside assumeRole permission), obtaining access key, secret key and session token for a role, assuming the role and use the credentials. Once the credentials are expired, the cycle could go back from the beginning or stop. > Camel-AWS Components: Make it possible to use AwsSessionCredentials to > support temporary credentials > > > Key: CAMEL-20281 > URL: https://issues.apache.org/jira/browse/CAMEL-20281 > Project: Camel > Issue Type: Improvement > Components: camel-aws >Reporter: Andrea Cosentino >Assignee: Andrea Cosentino >Priority: Major > Fix For: 4.x > > > This is really well explained through this: > https://repost.aws/knowledge-center/iam-assume-role-cli > Essentially it could be the case, we want a user to be able to do some > operations and having temporary credentials. As of today, we don't offer a > way of creating AWS sessions credentials and I think it's a good use case. > So the idea is introducing another option useSessionsCredentials and improve > the client factories we have. That way a user would be able to use this > kamelet correctly for example: > https://github.com/apache/camel-kamelets/blob/main/kamelets/aws-sts-assume-role-action.kamelet.yaml -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (CAMEL-20281) Camel-AWS Components: Make it possible to use AwsSessionCredentials to support temporary credentials
Andrea Cosentino created CAMEL-20281: Summary: Camel-AWS Components: Make it possible to use AwsSessionCredentials to support temporary credentials Key: CAMEL-20281 URL: https://issues.apache.org/jira/browse/CAMEL-20281 Project: Camel Issue Type: Improvement Components: camel-aws Reporter: Andrea Cosentino Assignee: Andrea Cosentino Fix For: 4.x This is really well explained through this: https://repost.aws/knowledge-center/iam-assume-role-cli Essentially it could be the case, we want a user to be able to do some operations and having temporary credentials. As of today, we don't offer a way of creating AWS sessions credentials and I think it's a good use case. So the idea is introducing another option useSessionsCredentials and improve the client factories we have. That way a user would be able to use this kamelet correctly for example: https://github.com/apache/camel-kamelets/blob/main/kamelets/aws-sts-assume-role-action.kamelet.yaml -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (CAMEL-20279) Fix issue related to flaky test S3CreateDownloadLinkOperationIT
[
https://issues.apache.org/jira/browse/CAMEL-20279?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17799728#comment-17799728
]
Andrea Cosentino commented on CAMEL-20279:
--
Let's leave it open
> Fix issue related to flaky test S3CreateDownloadLinkOperationIT
> ---
>
> Key: CAMEL-20279
> URL: https://issues.apache.org/jira/browse/CAMEL-20279
> Project: Camel
> Issue Type: Task
> Components: camel-aws2
>Affects Versions: 4.3.0
>Reporter: Aurélien Pupier
>Priority: Major
>
> {noformat}
> [camel-aws2-s3] [ERROR]
> org.apache.camel.component.aws2.s3.integration.S3CreateDownloadLinkOperationIT
> -- Time elapsed: 60.31 s <<< ERROR!
> org.testcontainers.containers.ContainerLaunchException: Container startup
> failed for image localstack/localstack:3.0.2
> at
> org.testcontainers.containers.GenericContainer.doStart(GenericContainer.java:362)
> at
> org.testcontainers.containers.GenericContainer.start(GenericContainer.java:333)
> at
> org.apache.camel.test.infra.aws2.services.AWSLocalContainerService.initialize(AWSLocalContainerService.java:106)
> at
> org.apache.camel.test.infra.common.services.TestServiceUtil.tryInitialize(TestServiceUtil.java:43)
> at
> org.apache.camel.test.infra.common.services.TestService.beforeAll(TestService.java:50)
> at java.base/java.util.ArrayList.forEach(ArrayList.java:1511)
> Caused by: org.rnorth.ducttape.RetryCountExceededException: Retry limit hit
> with exception
> at
> org.rnorth.ducttape.unreliables.Unreliables.retryUntilSuccess(Unreliables.java:88)
> at
> org.testcontainers.containers.GenericContainer.doStart(GenericContainer.java:347)
> ... 5 more
> Caused by: org.testcontainers.containers.ContainerLaunchException: Could not
> create/start container
> at
> org.testcontainers.containers.GenericContainer.tryStart(GenericContainer.java:566)
> at
> org.testcontainers.containers.GenericContainer.lambda$doStart$0(GenericContainer.java:357)
> at
> org.rnorth.ducttape.unreliables.Unreliables.retryUntilSuccess(Unreliables.java:81)
> ... 6 more
> Caused by: java.lang.IllegalStateException: Wait strategy failed. Container
> exited with code 245
> at
> org.testcontainers.containers.GenericContainer.tryStart(GenericContainer.java:536)
> ... 8 more
> Caused by: org.testcontainers.containers.ContainerLaunchException: Timed out
> waiting for log output matching '.*Ready\.
> '
> at
> org.testcontainers.containers.wait.strategy.LogMessageWaitStrategy.waitUntilReady(LogMessageWaitStrategy.java:47)
> at
> org.testcontainers.containers.wait.strategy.AbstractWaitStrategy.waitUntilReady(AbstractWaitStrategy.java:52)
> at
> org.testcontainers.containers.GenericContainer.waitUntilContainerStarted(GenericContainer.java:912)
> at
> org.testcontainers.containers.GenericContainer.tryStart(GenericContainer.java:503)
> ... 8 more
> {noformat}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Reopened] (CAMEL-20279) Fix issue related to flaky test S3CreateDownloadLinkOperationIT
[
https://issues.apache.org/jira/browse/CAMEL-20279?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrea Cosentino reopened CAMEL-20279:
--
> Fix issue related to flaky test S3CreateDownloadLinkOperationIT
> ---
>
> Key: CAMEL-20279
> URL: https://issues.apache.org/jira/browse/CAMEL-20279
> Project: Camel
> Issue Type: Task
> Components: camel-aws2
>Affects Versions: 4.3.0
>Reporter: Aurélien Pupier
>Priority: Major
>
> {noformat}
> [camel-aws2-s3] [ERROR]
> org.apache.camel.component.aws2.s3.integration.S3CreateDownloadLinkOperationIT
> -- Time elapsed: 60.31 s <<< ERROR!
> org.testcontainers.containers.ContainerLaunchException: Container startup
> failed for image localstack/localstack:3.0.2
> at
> org.testcontainers.containers.GenericContainer.doStart(GenericContainer.java:362)
> at
> org.testcontainers.containers.GenericContainer.start(GenericContainer.java:333)
> at
> org.apache.camel.test.infra.aws2.services.AWSLocalContainerService.initialize(AWSLocalContainerService.java:106)
> at
> org.apache.camel.test.infra.common.services.TestServiceUtil.tryInitialize(TestServiceUtil.java:43)
> at
> org.apache.camel.test.infra.common.services.TestService.beforeAll(TestService.java:50)
> at java.base/java.util.ArrayList.forEach(ArrayList.java:1511)
> Caused by: org.rnorth.ducttape.RetryCountExceededException: Retry limit hit
> with exception
> at
> org.rnorth.ducttape.unreliables.Unreliables.retryUntilSuccess(Unreliables.java:88)
> at
> org.testcontainers.containers.GenericContainer.doStart(GenericContainer.java:347)
> ... 5 more
> Caused by: org.testcontainers.containers.ContainerLaunchException: Could not
> create/start container
> at
> org.testcontainers.containers.GenericContainer.tryStart(GenericContainer.java:566)
> at
> org.testcontainers.containers.GenericContainer.lambda$doStart$0(GenericContainer.java:357)
> at
> org.rnorth.ducttape.unreliables.Unreliables.retryUntilSuccess(Unreliables.java:81)
> ... 6 more
> Caused by: java.lang.IllegalStateException: Wait strategy failed. Container
> exited with code 245
> at
> org.testcontainers.containers.GenericContainer.tryStart(GenericContainer.java:536)
> ... 8 more
> Caused by: org.testcontainers.containers.ContainerLaunchException: Timed out
> waiting for log output matching '.*Ready\.
> '
> at
> org.testcontainers.containers.wait.strategy.LogMessageWaitStrategy.waitUntilReady(LogMessageWaitStrategy.java:47)
> at
> org.testcontainers.containers.wait.strategy.AbstractWaitStrategy.waitUntilReady(AbstractWaitStrategy.java:52)
> at
> org.testcontainers.containers.GenericContainer.waitUntilContainerStarted(GenericContainer.java:912)
> at
> org.testcontainers.containers.GenericContainer.tryStart(GenericContainer.java:503)
> ... 8 more
> {noformat}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (CAMEL-20279) Fix issue related to flaky test S3CreateDownloadLinkOperationIT
[
https://issues.apache.org/jira/browse/CAMEL-20279?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17799706#comment-17799706
]
Andrea Cosentino commented on CAMEL-20279:
--
I don't really think something will change, because it happens in different
components, sometimes is s3, sometimes IAM, SQS or SNS. So I don't think we
could isolate the reason.
> Fix issue related to flaky test S3CreateDownloadLinkOperationIT
> ---
>
> Key: CAMEL-20279
> URL: https://issues.apache.org/jira/browse/CAMEL-20279
> Project: Camel
> Issue Type: Task
> Components: camel-aws2
>Affects Versions: 4.3.0
>Reporter: Aurélien Pupier
>Priority: Major
>
> {noformat}
> [camel-aws2-s3] [ERROR]
> org.apache.camel.component.aws2.s3.integration.S3CreateDownloadLinkOperationIT
> -- Time elapsed: 60.31 s <<< ERROR!
> org.testcontainers.containers.ContainerLaunchException: Container startup
> failed for image localstack/localstack:3.0.2
> at
> org.testcontainers.containers.GenericContainer.doStart(GenericContainer.java:362)
> at
> org.testcontainers.containers.GenericContainer.start(GenericContainer.java:333)
> at
> org.apache.camel.test.infra.aws2.services.AWSLocalContainerService.initialize(AWSLocalContainerService.java:106)
> at
> org.apache.camel.test.infra.common.services.TestServiceUtil.tryInitialize(TestServiceUtil.java:43)
> at
> org.apache.camel.test.infra.common.services.TestService.beforeAll(TestService.java:50)
> at java.base/java.util.ArrayList.forEach(ArrayList.java:1511)
> Caused by: org.rnorth.ducttape.RetryCountExceededException: Retry limit hit
> with exception
> at
> org.rnorth.ducttape.unreliables.Unreliables.retryUntilSuccess(Unreliables.java:88)
> at
> org.testcontainers.containers.GenericContainer.doStart(GenericContainer.java:347)
> ... 5 more
> Caused by: org.testcontainers.containers.ContainerLaunchException: Could not
> create/start container
> at
> org.testcontainers.containers.GenericContainer.tryStart(GenericContainer.java:566)
> at
> org.testcontainers.containers.GenericContainer.lambda$doStart$0(GenericContainer.java:357)
> at
> org.rnorth.ducttape.unreliables.Unreliables.retryUntilSuccess(Unreliables.java:81)
> ... 6 more
> Caused by: java.lang.IllegalStateException: Wait strategy failed. Container
> exited with code 245
> at
> org.testcontainers.containers.GenericContainer.tryStart(GenericContainer.java:536)
> ... 8 more
> Caused by: org.testcontainers.containers.ContainerLaunchException: Timed out
> waiting for log output matching '.*Ready\.
> '
> at
> org.testcontainers.containers.wait.strategy.LogMessageWaitStrategy.waitUntilReady(LogMessageWaitStrategy.java:47)
> at
> org.testcontainers.containers.wait.strategy.AbstractWaitStrategy.waitUntilReady(AbstractWaitStrategy.java:52)
> at
> org.testcontainers.containers.GenericContainer.waitUntilContainerStarted(GenericContainer.java:912)
> at
> org.testcontainers.containers.GenericContainer.tryStart(GenericContainer.java:503)
> ... 8 more
> {noformat}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (CAMEL-20279) Fix issue related to flaky test S3CreateDownloadLinkOperationIT
[
https://issues.apache.org/jira/browse/CAMEL-20279?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17799703#comment-17799703
]
Andrea Cosentino commented on CAMEL-20279:
--
It's just a github action glitch.
> Fix issue related to flaky test S3CreateDownloadLinkOperationIT
> ---
>
> Key: CAMEL-20279
> URL: https://issues.apache.org/jira/browse/CAMEL-20279
> Project: Camel
> Issue Type: Task
> Components: camel-aws2
>Affects Versions: 4.3.0
>Reporter: Aurélien Pupier
>Priority: Major
>
> {noformat}
> [camel-aws2-s3] [ERROR]
> org.apache.camel.component.aws2.s3.integration.S3CreateDownloadLinkOperationIT
> -- Time elapsed: 60.31 s <<< ERROR!
> org.testcontainers.containers.ContainerLaunchException: Container startup
> failed for image localstack/localstack:3.0.2
> at
> org.testcontainers.containers.GenericContainer.doStart(GenericContainer.java:362)
> at
> org.testcontainers.containers.GenericContainer.start(GenericContainer.java:333)
> at
> org.apache.camel.test.infra.aws2.services.AWSLocalContainerService.initialize(AWSLocalContainerService.java:106)
> at
> org.apache.camel.test.infra.common.services.TestServiceUtil.tryInitialize(TestServiceUtil.java:43)
> at
> org.apache.camel.test.infra.common.services.TestService.beforeAll(TestService.java:50)
> at java.base/java.util.ArrayList.forEach(ArrayList.java:1511)
> Caused by: org.rnorth.ducttape.RetryCountExceededException: Retry limit hit
> with exception
> at
> org.rnorth.ducttape.unreliables.Unreliables.retryUntilSuccess(Unreliables.java:88)
> at
> org.testcontainers.containers.GenericContainer.doStart(GenericContainer.java:347)
> ... 5 more
> Caused by: org.testcontainers.containers.ContainerLaunchException: Could not
> create/start container
> at
> org.testcontainers.containers.GenericContainer.tryStart(GenericContainer.java:566)
> at
> org.testcontainers.containers.GenericContainer.lambda$doStart$0(GenericContainer.java:357)
> at
> org.rnorth.ducttape.unreliables.Unreliables.retryUntilSuccess(Unreliables.java:81)
> ... 6 more
> Caused by: java.lang.IllegalStateException: Wait strategy failed. Container
> exited with code 245
> at
> org.testcontainers.containers.GenericContainer.tryStart(GenericContainer.java:536)
> ... 8 more
> Caused by: org.testcontainers.containers.ContainerLaunchException: Timed out
> waiting for log output matching '.*Ready\.
> '
> at
> org.testcontainers.containers.wait.strategy.LogMessageWaitStrategy.waitUntilReady(LogMessageWaitStrategy.java:47)
> at
> org.testcontainers.containers.wait.strategy.AbstractWaitStrategy.waitUntilReady(AbstractWaitStrategy.java:52)
> at
> org.testcontainers.containers.GenericContainer.waitUntilContainerStarted(GenericContainer.java:912)
> at
> org.testcontainers.containers.GenericContainer.tryStart(GenericContainer.java:503)
> ... 8 more
> {noformat}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Closed] (CAMEL-20279) Fix issue related to flaky test S3CreateDownloadLinkOperationIT
[
https://issues.apache.org/jira/browse/CAMEL-20279?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrea Cosentino closed CAMEL-20279.
Resolution: Won't Fix
> Fix issue related to flaky test S3CreateDownloadLinkOperationIT
> ---
>
> Key: CAMEL-20279
> URL: https://issues.apache.org/jira/browse/CAMEL-20279
> Project: Camel
> Issue Type: Task
> Components: camel-aws2
>Affects Versions: 4.3.0
>Reporter: Aurélien Pupier
>Priority: Major
>
> {noformat}
> [camel-aws2-s3] [ERROR]
> org.apache.camel.component.aws2.s3.integration.S3CreateDownloadLinkOperationIT
> -- Time elapsed: 60.31 s <<< ERROR!
> org.testcontainers.containers.ContainerLaunchException: Container startup
> failed for image localstack/localstack:3.0.2
> at
> org.testcontainers.containers.GenericContainer.doStart(GenericContainer.java:362)
> at
> org.testcontainers.containers.GenericContainer.start(GenericContainer.java:333)
> at
> org.apache.camel.test.infra.aws2.services.AWSLocalContainerService.initialize(AWSLocalContainerService.java:106)
> at
> org.apache.camel.test.infra.common.services.TestServiceUtil.tryInitialize(TestServiceUtil.java:43)
> at
> org.apache.camel.test.infra.common.services.TestService.beforeAll(TestService.java:50)
> at java.base/java.util.ArrayList.forEach(ArrayList.java:1511)
> Caused by: org.rnorth.ducttape.RetryCountExceededException: Retry limit hit
> with exception
> at
> org.rnorth.ducttape.unreliables.Unreliables.retryUntilSuccess(Unreliables.java:88)
> at
> org.testcontainers.containers.GenericContainer.doStart(GenericContainer.java:347)
> ... 5 more
> Caused by: org.testcontainers.containers.ContainerLaunchException: Could not
> create/start container
> at
> org.testcontainers.containers.GenericContainer.tryStart(GenericContainer.java:566)
> at
> org.testcontainers.containers.GenericContainer.lambda$doStart$0(GenericContainer.java:357)
> at
> org.rnorth.ducttape.unreliables.Unreliables.retryUntilSuccess(Unreliables.java:81)
> ... 6 more
> Caused by: java.lang.IllegalStateException: Wait strategy failed. Container
> exited with code 245
> at
> org.testcontainers.containers.GenericContainer.tryStart(GenericContainer.java:536)
> ... 8 more
> Caused by: org.testcontainers.containers.ContainerLaunchException: Timed out
> waiting for log output matching '.*Ready\.
> '
> at
> org.testcontainers.containers.wait.strategy.LogMessageWaitStrategy.waitUntilReady(LogMessageWaitStrategy.java:47)
> at
> org.testcontainers.containers.wait.strategy.AbstractWaitStrategy.waitUntilReady(AbstractWaitStrategy.java:52)
> at
> org.testcontainers.containers.GenericContainer.waitUntilContainerStarted(GenericContainer.java:912)
> at
> org.testcontainers.containers.GenericContainer.tryStart(GenericContainer.java:503)
> ... 8 more
> {noformat}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Created] (CAMEL-20272) Camel-Azure components: Support SAS Authentication where is still not supported
Andrea Cosentino created CAMEL-20272: Summary: Camel-Azure components: Support SAS Authentication where is still not supported Key: CAMEL-20272 URL: https://issues.apache.org/jira/browse/CAMEL-20272 Project: Camel Issue Type: Improvement Reporter: Andrea Cosentino Assignee: Andrea Cosentino Fix For: 4.4.0 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (CAMEL-20271) Camel-AWS-Cloudtrail: Improve consumers by adding more information as exchange headers
[ https://issues.apache.org/jira/browse/CAMEL-20271?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Cosentino resolved CAMEL-20271. -- Resolution: Fixed > Camel-AWS-Cloudtrail: Improve consumers by adding more information as > exchange headers > -- > > Key: CAMEL-20271 > URL: https://issues.apache.org/jira/browse/CAMEL-20271 > Project: Camel > Issue Type: Improvement >Reporter: Andrea Cosentino >Assignee: Andrea Cosentino >Priority: Major > Fix For: 4.4.0 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (CAMEL-20271) Camel-AWS-Cloudtrail: Improve consumers by adding more information as exchange headers
Andrea Cosentino created CAMEL-20271: Summary: Camel-AWS-Cloudtrail: Improve consumers by adding more information as exchange headers Key: CAMEL-20271 URL: https://issues.apache.org/jira/browse/CAMEL-20271 Project: Camel Issue Type: Improvement Reporter: Andrea Cosentino Assignee: Andrea Cosentino Fix For: 4.4.0 -- This message was sent by Atlassian Jira (v8.20.10#820010)
