[jira] [Resolved] (CAMEL-20260) Remove Camel HDFS Starter
[ https://issues.apache.org/jira/browse/CAMEL-20260?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Cosentino resolved CAMEL-20260. -- Resolution: Fixed > Remove Camel HDFS Starter > - > > Key: CAMEL-20260 > URL: https://issues.apache.org/jira/browse/CAMEL-20260 > Project: Camel > Issue Type: Task > Components: camel-spring-boot >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] [Resolved] (CAMEL-20259) Remove Camel-HDFS Component
[ https://issues.apache.org/jira/browse/CAMEL-20259?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Cosentino resolved CAMEL-20259. -- Resolution: Fixed > Remove Camel-HDFS Component > --- > > Key: CAMEL-20259 > URL: https://issues.apache.org/jira/browse/CAMEL-20259 > Project: Camel > Issue Type: Task >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-20259) Remove Camel-HDFS Component
Andrea Cosentino created CAMEL-20259: Summary: Remove Camel-HDFS Component Key: CAMEL-20259 URL: https://issues.apache.org/jira/browse/CAMEL-20259 Project: Camel Issue Type: Task Reporter: Andrea Cosentino Assignee: Andrea Cosentino Fix For: 4.4.0 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (CAMEL-20260) Remove Camel HDFS Starter
Andrea Cosentino created CAMEL-20260: Summary: Remove Camel HDFS Starter Key: CAMEL-20260 URL: https://issues.apache.org/jira/browse/CAMEL-20260 Project: Camel Issue Type: Task Components: camel-spring-boot 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-20250) camel-kinesis: resume API fails to resume properly
[ https://issues.apache.org/jira/browse/CAMEL-20250?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Cosentino resolved CAMEL-20250. -- Resolution: Fixed > camel-kinesis: resume API fails to resume properly > -- > > Key: CAMEL-20250 > URL: https://issues.apache.org/jira/browse/CAMEL-20250 > Project: Camel > Issue Type: Bug > Components: camel-aws2-kinesis >Affects Versions: 3.21.3, 4.3.0 >Reporter: Otavio Rodolfo Piske >Priority: Major > Fix For: 4.4.0 > > > Quoting [https://github.com/abendt|http://example.com]on the pull request > [#12462|https://github.com/apache/camel/pull/12462]: > * the shardId is not available in the exchange. The shardId is required to > properly configure the GetShardIteratorRequest in the resume scenario (AWS > doc) > * the KinesisResumeAdapter API does not allow to pass in the shardId. > * When consuming multiple shards the KinesisResumeAdapter will potentially be > used by multiple threads concurrently. With the current API, this could cause > concurrency issues -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (CAMEL-18590) Camel-Azure components: Define a unique configuration for authentication
[ https://issues.apache.org/jira/browse/CAMEL-18590?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Cosentino resolved CAMEL-18590. -- Resolution: Fixed > Camel-Azure components: Define a unique configuration for authentication > > > Key: CAMEL-18590 > URL: https://issues.apache.org/jira/browse/CAMEL-18590 > Project: Camel > Issue Type: Improvement > Components: camel-azure >Reporter: Andrea Cosentino >Assignee: Andrea Cosentino >Priority: Major > Fix For: 4.4.0 > > > We have currently different approach for authenticating against Azure > services. For example in Azure Storage Blob we have the credentialType > parameter which is an enum and we have three possible values. In Azure > Eventhubs we have tokenCredential in combination with other possible > approaches. > We should have just one way and one set of parameters in all the Azure > components, like we have in AWS and we are trying to do in GCP. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (CAMEL-20205) Add SBOM to release and release-sbom script to LTS 4.0.x, 3.22.x and 3.21.x
[ https://issues.apache.org/jira/browse/CAMEL-20205?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Cosentino updated CAMEL-20205: - Fix Version/s: 3.21.4 > Add SBOM to release and release-sbom script to LTS 4.0.x, 3.22.x and 3.21.x > --- > > Key: CAMEL-20205 > URL: https://issues.apache.org/jira/browse/CAMEL-20205 > Project: Camel > Issue Type: Improvement >Reporter: Andrea Cosentino >Assignee: Andrea Cosentino >Priority: Major > Fix For: 3.21.4, 3.22.0, 4.0.4 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (CAMEL-20205) Add SBOM to release and release-sbom script to LTS 4.0.x, 3.22.x and 3.21.x
[ https://issues.apache.org/jira/browse/CAMEL-20205?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Cosentino updated CAMEL-20205: - Summary: Add SBOM to release and release-sbom script to LTS 4.0.x, 3.22.x and 3.21.x (was: Add SBOM to release and release-sbom script to LTS 4.0.x and 3.22.x) > Add SBOM to release and release-sbom script to LTS 4.0.x, 3.22.x and 3.21.x > --- > > Key: CAMEL-20205 > URL: https://issues.apache.org/jira/browse/CAMEL-20205 > Project: Camel > Issue Type: Improvement >Reporter: Andrea Cosentino >Assignee: Andrea Cosentino >Priority: Major > Fix For: 3.22.0, 4.0.4 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (CAMEL-20239) Camel-Azure-Files: The component doesn't set account parameter on the URI
[ https://issues.apache.org/jira/browse/CAMEL-20239?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Cosentino updated CAMEL-20239: - Affects Version/s: 4.2.0 4.0.3 4.3.0 > Camel-Azure-Files: The component doesn't set account parameter on the URI > - > > Key: CAMEL-20239 > URL: https://issues.apache.org/jira/browse/CAMEL-20239 > Project: Camel > Issue Type: Bug >Affects Versions: 4.0.3, 4.2.0, 4.3.0 >Reporter: Andrea Cosentino >Priority: Major > Fix For: 4.4.0 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (CAMEL-20239) Camel-Azure-Files: The component doesn't set account parameter on the URI
[ https://issues.apache.org/jira/browse/CAMEL-20239?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Cosentino updated CAMEL-20239: - Description: (was: It's hard to follow all the corner cases in the code. I do believe this component requires a bit of love.) > Camel-Azure-Files: The component doesn't set account parameter on the URI > - > > Key: CAMEL-20239 > URL: https://issues.apache.org/jira/browse/CAMEL-20239 > Project: Camel > Issue Type: Bug >Reporter: Andrea Cosentino >Priority: Major > Fix For: 4.4.0 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (CAMEL-20239) Camel-Azure-Files: The component doesn't set account parameter on the URI
[ https://issues.apache.org/jira/browse/CAMEL-20239?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Cosentino updated CAMEL-20239: - Summary: Camel-Azure-Files: The component doesn't set account parameter on the URI (was: Camel-Azure-Files: Review management of account and share uriPath parameters) > Camel-Azure-Files: The component doesn't set account parameter on the URI > - > > Key: CAMEL-20239 > URL: https://issues.apache.org/jira/browse/CAMEL-20239 > Project: Camel > Issue Type: Improvement >Reporter: Andrea Cosentino >Priority: Major > Fix For: 4.4.0 > > > It's hard to follow all the corner cases in the code. I do believe this > component requires a bit of love. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (CAMEL-20239) Camel-Azure-Files: The component doesn't set account parameter on the URI
[ https://issues.apache.org/jira/browse/CAMEL-20239?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Cosentino updated CAMEL-20239: - Issue Type: Bug (was: Improvement) > Camel-Azure-Files: The component doesn't set account parameter on the URI > - > > Key: CAMEL-20239 > URL: https://issues.apache.org/jira/browse/CAMEL-20239 > Project: Camel > Issue Type: Bug >Reporter: Andrea Cosentino >Priority: Major > Fix For: 4.4.0 > > > It's hard to follow all the corner cases in the code. I do believe this > component requires a bit of love. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (CAMEL-20239) Camel-Azure-Files: Review management of account and share uriPath parameters
Andrea Cosentino created CAMEL-20239: Summary: Camel-Azure-Files: Review management of account and share uriPath parameters Key: CAMEL-20239 URL: https://issues.apache.org/jira/browse/CAMEL-20239 Project: Camel Issue Type: Improvement Reporter: Andrea Cosentino Fix For: 4.4.0 It's hard to follow all the corner cases in the code. I do believe this component requires a bit of love. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (CAMEL-20205) Add SBOM to release and release-sbom script to LTS 4.0.x and 3.22.x
[ https://issues.apache.org/jira/browse/CAMEL-20205?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Cosentino updated CAMEL-20205: - Fix Version/s: 3.22.0 > Add SBOM to release and release-sbom script to LTS 4.0.x and 3.22.x > --- > > Key: CAMEL-20205 > URL: https://issues.apache.org/jira/browse/CAMEL-20205 > Project: Camel > Issue Type: Improvement >Reporter: Andrea Cosentino >Assignee: Andrea Cosentino >Priority: Major > Fix For: 3.22.0, 4.0.4 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (CAMEL-20205) Add SBOM to release and release-sbom script to LTS 4.0.x and 3.22.x
[ https://issues.apache.org/jira/browse/CAMEL-20205?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Cosentino resolved CAMEL-20205. -- Resolution: Fixed > Add SBOM to release and release-sbom script to LTS 4.0.x and 3.22.x > --- > > Key: CAMEL-20205 > URL: https://issues.apache.org/jira/browse/CAMEL-20205 > Project: Camel > Issue Type: Improvement >Reporter: Andrea Cosentino >Assignee: Andrea Cosentino >Priority: Major > Fix For: 3.22.0, 4.0.4 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (CAMEL-20205) Add SBOM to release and release-sbom script to LTS 4.0.x and 3.22.x
[ https://issues.apache.org/jira/browse/CAMEL-20205?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Cosentino updated CAMEL-20205: - Summary: Add SBOM to release and release-sbom script to LTS 4.0.x and 3.22.x (was: Add SBOM to release and release-sbom script to LTS 4.0.x) > Add SBOM to release and release-sbom script to LTS 4.0.x and 3.22.x > --- > > Key: CAMEL-20205 > URL: https://issues.apache.org/jira/browse/CAMEL-20205 > Project: Camel > Issue Type: Improvement >Reporter: Andrea Cosentino >Assignee: Andrea Cosentino >Priority: Major > Fix For: 4.0.4 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (CAMEL-20229) Camel-Azure-Storage-Queue: Add CloudEvents Data Type Transformer
[ https://issues.apache.org/jira/browse/CAMEL-20229?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Cosentino resolved CAMEL-20229. -- Resolution: Fixed > Camel-Azure-Storage-Queue: Add CloudEvents Data Type Transformer > > > Key: CAMEL-20229 > URL: https://issues.apache.org/jira/browse/CAMEL-20229 > Project: Camel > Issue Type: New Feature > Components: camel-azure >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-20229) Camel-Azure-Storage-Queue: Add CloudEvents Data Type Transformer
Andrea Cosentino created CAMEL-20229: Summary: Camel-Azure-Storage-Queue: Add CloudEvents Data Type Transformer Key: CAMEL-20229 URL: https://issues.apache.org/jira/browse/CAMEL-20229 Project: Camel Issue Type: New Feature Components: camel-azure Reporter: Andrea Cosentino Assignee: Andrea Cosentino Fix For: 4.4.0 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (CAMEL-18590) Camel-Azure components: Define a unique configuration for authentication
[ https://issues.apache.org/jira/browse/CAMEL-18590?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Cosentino reassigned CAMEL-18590: Assignee: Andrea Cosentino > Camel-Azure components: Define a unique configuration for authentication > > > Key: CAMEL-18590 > URL: https://issues.apache.org/jira/browse/CAMEL-18590 > Project: Camel > Issue Type: Improvement > Components: camel-azure >Reporter: Andrea Cosentino >Assignee: Andrea Cosentino >Priority: Major > Fix For: 4.x > > > We have currently different approach for authenticating against Azure > services. For example in Azure Storage Blob we have the credentialType > parameter which is an enum and we have three possible values. In Azure > Eventhubs we have tokenCredential in combination with other possible > approaches. > We should have just one way and one set of parameters in all the Azure > components, like we have in AWS and we are trying to do in GCP. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (CAMEL-18590) Camel-Azure components: Define a unique configuration for authentication
[ https://issues.apache.org/jira/browse/CAMEL-18590?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Cosentino updated CAMEL-18590: - Fix Version/s: 4.4.0 (was: 4.x) > Camel-Azure components: Define a unique configuration for authentication > > > Key: CAMEL-18590 > URL: https://issues.apache.org/jira/browse/CAMEL-18590 > Project: Camel > Issue Type: Improvement > Components: camel-azure >Reporter: Andrea Cosentino >Assignee: Andrea Cosentino >Priority: Major > Fix For: 4.4.0 > > > We have currently different approach for authenticating against Azure > services. For example in Azure Storage Blob we have the credentialType > parameter which is an enum and we have three possible values. In Azure > Eventhubs we have tokenCredential in combination with other possible > approaches. > We should have just one way and one set of parameters in all the Azure > components, like we have in AWS and we are trying to do in GCP. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (CAMEL-20223) Camel-Spring-Boot: Camel Azure Key Vault should Support Azure Identity in the component and secrets function
[ https://issues.apache.org/jira/browse/CAMEL-20223?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Cosentino resolved CAMEL-20223. -- Resolution: Fixed > Camel-Spring-Boot: Camel Azure Key Vault should Support Azure Identity in the > component and secrets function > > > Key: CAMEL-20223 > URL: https://issues.apache.org/jira/browse/CAMEL-20223 > Project: Camel > Issue Type: New Feature > Components: camel-spring-boot >Reporter: Andrea Cosentino >Assignee: Andrea Cosentino >Priority: Major > Fix For: 4.4.0 > > > See CAMEL-20220 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (CAMEL-20220) Camel Azure Key Vault: Support Azure Identity in the component and secrets function
[ https://issues.apache.org/jira/browse/CAMEL-20220?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Cosentino resolved CAMEL-20220. -- Resolution: Fixed > Camel Azure Key Vault: Support Azure Identity in the component and secrets > function > --- > > Key: CAMEL-20220 > URL: https://issues.apache.org/jira/browse/CAMEL-20220 > Project: Camel > Issue Type: New Feature > Components: camel-azure >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-20223) Camel-Spring-Boot: Camel Azure Key Vault should Support Azure Identity in the component and secrets function
Andrea Cosentino created CAMEL-20223: Summary: Camel-Spring-Boot: Camel Azure Key Vault should Support Azure Identity in the component and secrets function Key: CAMEL-20223 URL: https://issues.apache.org/jira/browse/CAMEL-20223 Project: Camel Issue Type: New Feature Components: camel-spring-boot Reporter: Andrea Cosentino Assignee: Andrea Cosentino Fix For: 4.4.0 See CAMEL-20220 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (CAMEL-20220) Camel Azure Key Vault: Support Azure Identity in the component and secrets function
[ https://issues.apache.org/jira/browse/CAMEL-20220?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Cosentino updated CAMEL-20220: - Summary: Camel Azure Key Vault: Support Azure Identity in the component and secrets function (was: Camel Azure Key Vault: Support Azure Identity in the component, Secret Function and refresh) > Camel Azure Key Vault: Support Azure Identity in the component and secrets > function > --- > > Key: CAMEL-20220 > URL: https://issues.apache.org/jira/browse/CAMEL-20220 > Project: Camel > Issue Type: New Feature > Components: camel-azure >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-20220) Camel Azure Key Vault: Support Azure Identity in the component, Secret Function and refresh
Andrea Cosentino created CAMEL-20220: Summary: Camel Azure Key Vault: Support Azure Identity in the component, Secret Function and refresh Key: CAMEL-20220 URL: https://issues.apache.org/jira/browse/CAMEL-20220 Project: Camel Issue Type: New Feature Components: camel-azure Reporter: Andrea Cosentino Assignee: Andrea Cosentino Fix For: 4.4.0 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (CAMEL-20205) Add SBOM to release and release-sbom script to LTS 4.0.x
Andrea Cosentino created CAMEL-20205: Summary: Add SBOM to release and release-sbom script to LTS 4.0.x Key: CAMEL-20205 URL: https://issues.apache.org/jira/browse/CAMEL-20205 Project: Camel Issue Type: Improvement Reporter: Andrea Cosentino Assignee: Andrea Cosentino Fix For: 4.0.4 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (CAMEL-16181) KafkaIdempotentRepository cache incorrectly flagged as ready
[
https://issues.apache.org/jira/browse/CAMEL-16181?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17793863#comment-17793863
]
Andrea Cosentino commented on CAMEL-16181:
--
Can you try with 3.21.2? Also this is an LTS, but we are focusing on Camel 4.
so it would be good to test the same scenario with Camel 4.0.3 and 4.2.0
> KafkaIdempotentRepository cache incorrectly flagged as ready
>
>
> Key: CAMEL-16181
> URL: https://issues.apache.org/jira/browse/CAMEL-16181
> Project: Camel
> Issue Type: Improvement
> Components: camel-kafka
>Affects Versions: 3.7.2
>Reporter: Javier Holguera
>Priority: Major
> Fix For: 3.7.3, 3.8.0
>
> Attachments: kafka-idempotent-repository.log
>
>
> The `KafkaIdempotentRepository` initialises its cache off the back of the
> pre-existing Kafka topic with previous entries, with the following code:
>
> {code:java}
> log.debug("Subscribing consumer to {}", topic);
> consumer.subscribe(Collections.singleton(topic));
> log.debug("Seeking to beginning");
> consumer.seekToBeginning(consumer.assignment());
>
> POLL_LOOP: while (running.get()) {
> log.trace("Polling");
> ConsumerRecords consumerRecords =
> consumer.poll(pollDurationMs);
> if (consumerRecords.isEmpty()) {
> // the first time this happens, we can assume that we have consumed all
> messages up to this point
> log.trace("0 messages fetched on poll");
> if (cacheReadyLatch.getCount() > 0) {
> log.debug("Cache warmed up");
> cacheReadyLatch.countDown();
> }
> }{code}
>
> The problem with this code is:
> # `consumer.subscribe` doesn't instantaneously assign partitions to the
> consumer
> # When `consumer.seekToBeginning` is called, the operation doesn't do
> anything because it has no partitions yet (see [seekToBeginning doesn't work
> without auto.offset.reset
> (apache.org)|https://mail-archives.apache.org/mod_mbox/kafka-users/201603.mbox/%3ccakwx9vumpliqtu9o0mpepaupszapw9lm91mwexvafwktgd3...@mail.gmail.com%3e]
>
> # When later the first `consumer.poll` is issued, it returns nothing,
> triggering the sequence to *confirm the cache as ready when it isn't yet*.
> That can cause upstream messages not been correctly de-duplicated.
> The solution is:
> # Use a different overload of `consumer.subscribe` that accepts an
> implementation of the `ConsumerRebalanceListener`.
> # When partitions are assigned to the `consumer` instance, call
> `seekToBeginning` there.
> # Doing an initial `poll(0)` that will never return records but will force
> the partition assignment process
--
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=17793740#comment-17793740 ] Andrea Cosentino commented on CAMEL-20095: -- In terms of structure, I think we should think about having a middle folder called camel-ai and inside creating the related component to deal with. Maybe only azure-open-ai should go in camel-azure middle folder. Are you working on a particular one right 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] [Resolved] (CAMEL-20198) camel-google - Upgrade to newer google-api-services
[ https://issues.apache.org/jira/browse/CAMEL-20198?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Cosentino resolved CAMEL-20198. -- Resolution: Fixed > camel-google - Upgrade to newer google-api-services > --- > > Key: CAMEL-20198 > URL: https://issues.apache.org/jira/browse/CAMEL-20198 > Project: Camel > Issue Type: Dependency upgrade > Components: camel-google >Reporter: Claus Ibsen >Assignee: Andrea Cosentino >Priority: Minor > Fix For: 4.3.0 > > > We have PR from bot for upgrades, but they may need some regen of code, or > some small adjustems. So we need to do this manually. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (CAMEL-20198) camel-google - Upgrade to newer google-api-services
[ https://issues.apache.org/jira/browse/CAMEL-20198?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17793729#comment-17793729 ] Andrea Cosentino commented on CAMEL-20198: -- google-mail done. > camel-google - Upgrade to newer google-api-services > --- > > Key: CAMEL-20198 > URL: https://issues.apache.org/jira/browse/CAMEL-20198 > Project: Camel > Issue Type: Dependency upgrade > Components: camel-google >Reporter: Claus Ibsen >Assignee: Andrea Cosentino >Priority: Minor > Fix For: 4.3.0 > > > We have PR from bot for upgrades, but they may need some regen of code, or > some small adjustems. So we need to do this manually. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (CAMEL-20198) camel-google - Upgrade to newer google-api-services
[ https://issues.apache.org/jira/browse/CAMEL-20198?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Cosentino reassigned CAMEL-20198: Assignee: Andrea Cosentino > camel-google - Upgrade to newer google-api-services > --- > > Key: CAMEL-20198 > URL: https://issues.apache.org/jira/browse/CAMEL-20198 > Project: Camel > Issue Type: Dependency upgrade > Components: camel-google >Reporter: Claus Ibsen >Assignee: Andrea Cosentino >Priority: Minor > Fix For: 4.3.0 > > > We have PR from bot for upgrades, but they may need some regen of code, or > some small adjustems. So we need to do this manually. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (CAMEL-20196) Deprecate camel-hdfs
[ https://issues.apache.org/jira/browse/CAMEL-20196?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Cosentino resolved CAMEL-20196. -- Resolution: Fixed > Deprecate camel-hdfs > > > Key: CAMEL-20196 > URL: https://issues.apache.org/jira/browse/CAMEL-20196 > Project: Camel > Issue Type: Task >Reporter: Andrea Cosentino >Assignee: Andrea Cosentino >Priority: Major > Fix For: 4.3.0 > > > It's really annoying. They don't really care about upgrading dependencies and > also it brings in a billion third party dependencies. > It's time to deprecate and remove on 4.4.0 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (CAMEL-20196) Deprecate camel-hdfs
Andrea Cosentino created CAMEL-20196: Summary: Deprecate camel-hdfs Key: CAMEL-20196 URL: https://issues.apache.org/jira/browse/CAMEL-20196 Project: Camel Issue Type: Task Reporter: Andrea Cosentino Assignee: Andrea Cosentino Fix For: 4.3.0 It's really annoying. They don't really care about upgrading dependencies and also it brings in a billion third party dependencies. It's time to deprecate and remove on 4.4.0 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (CAMEL-20147) camel-spring-boot: Upgrade to 3.1.6
[ https://issues.apache.org/jira/browse/CAMEL-20147?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Cosentino resolved CAMEL-20147. -- Resolution: Fixed > camel-spring-boot: Upgrade to 3.1.6 > --- > > Key: CAMEL-20147 > URL: https://issues.apache.org/jira/browse/CAMEL-20147 > Project: Camel > Issue Type: Dependency upgrade >Reporter: Andrea Cosentino >Assignee: Andrea Cosentino >Priority: Major > Fix For: 4.0.4 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (CAMEL-20149) Release guide: Add instructions to sign and publish SBOM files to dist/release folder
[ https://issues.apache.org/jira/browse/CAMEL-20149?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Cosentino resolved CAMEL-20149. -- Resolution: Fixed > Release guide: Add instructions to sign and publish SBOM files to > dist/release folder > -- > > Key: CAMEL-20149 > URL: https://issues.apache.org/jira/browse/CAMEL-20149 > Project: Camel > Issue Type: Task >Reporter: Andrea Cosentino >Assignee: Andrea Cosentino >Priority: Major > Fix For: 4.3.0 > > > We had this discussion and discovered we are not uploading the SBOMs to > dist/release > The release guide needs to be updated for Camel and Camel Spring Boot. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (CAMEL-20190) Camel-Spring-Boot: Kubernetes Cronjob starter
[ https://issues.apache.org/jira/browse/CAMEL-20190?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Cosentino resolved CAMEL-20190. -- Resolution: Fixed > Camel-Spring-Boot: Kubernetes Cronjob starter > - > > Key: CAMEL-20190 > URL: https://issues.apache.org/jira/browse/CAMEL-20190 > Project: Camel > Issue Type: New Feature > Components: camel-spring-boot >Reporter: Andrea Cosentino >Assignee: Andrea Cosentino >Priority: Major > Fix For: 4.3.0 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (CAMEL-20190) Camel-Spring-Boot: Kubernetes Cronjob starter
Andrea Cosentino created CAMEL-20190: Summary: Camel-Spring-Boot: Kubernetes Cronjob starter Key: CAMEL-20190 URL: https://issues.apache.org/jira/browse/CAMEL-20190 Project: Camel Issue Type: New Feature Components: camel-spring-boot Reporter: Andrea Cosentino Assignee: Andrea Cosentino Fix For: 4.3.0 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (CAMEL-20185) Kubernetes CronJob Component
[
https://issues.apache.org/jira/browse/CAMEL-20185?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrea Cosentino resolved CAMEL-20185.
--
Resolution: Fixed
> Kubernetes CronJob Component
>
>
> Key: CAMEL-20185
> URL: https://issues.apache.org/jira/browse/CAMEL-20185
> Project: Camel
> Issue Type: New Feature
> Components: camel-kubernetes
>Reporter: Matthias Bechtold
>Assignee: Andrea Cosentino
>Priority: Major
> Fix For: 4.3.0
>
>
> We are building an end to end test with Camel and want to read the
> {{.jobTemplate.spec}} field from a k8s {{{}CronJob{}}}.
> Since there is (apparently) no {{CronJob}} component like there is
> ["kubernetes-job"|https://camel.apache.org/components/next/kubernetes-job-component.html],
> we ended up building it the hard way using fabric8's k8s client.
> What we have done so far, could be greatly simplified by having a
> "kubernetes-cronjob" Camel component, with an operation "getCronJob", which
> would retrieve the {{CronJob}} manifest from k8s and put it into a message
> header or body.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Assigned] (CAMEL-20185) Kubernetes CronJob Component
[
https://issues.apache.org/jira/browse/CAMEL-20185?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrea Cosentino reassigned CAMEL-20185:
Assignee: Andrea Cosentino
> Kubernetes CronJob Component
>
>
> Key: CAMEL-20185
> URL: https://issues.apache.org/jira/browse/CAMEL-20185
> Project: Camel
> Issue Type: New Feature
> Components: camel-kubernetes
>Reporter: Matthias Bechtold
>Assignee: Andrea Cosentino
>Priority: Major
>
> We are building an end to end test with Camel and want to read the
> {{.jobTemplate.spec}} field from a k8s {{{}CronJob{}}}.
> Since there is (apparently) no {{CronJob}} component like there is
> ["kubernetes-job"|https://camel.apache.org/components/next/kubernetes-job-component.html],
> we ended up building it the hard way using fabric8's k8s client.
> What we have done so far, could be greatly simplified by having a
> "kubernetes-cronjob" Camel component, with an operation "getCronJob", which
> would retrieve the {{CronJob}} manifest from k8s and put it into a message
> header or body.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (CAMEL-20185) Kubernetes CronJob Component
[
https://issues.apache.org/jira/browse/CAMEL-20185?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrea Cosentino updated CAMEL-20185:
-
Fix Version/s: 4.3.0
> Kubernetes CronJob Component
>
>
> Key: CAMEL-20185
> URL: https://issues.apache.org/jira/browse/CAMEL-20185
> Project: Camel
> Issue Type: New Feature
> Components: camel-kubernetes
>Reporter: Matthias Bechtold
>Assignee: Andrea Cosentino
>Priority: Major
> Fix For: 4.3.0
>
>
> We are building an end to end test with Camel and want to read the
> {{.jobTemplate.spec}} field from a k8s {{{}CronJob{}}}.
> Since there is (apparently) no {{CronJob}} component like there is
> ["kubernetes-job"|https://camel.apache.org/components/next/kubernetes-job-component.html],
> we ended up building it the hard way using fabric8's k8s client.
> What we have done so far, could be greatly simplified by having a
> "kubernetes-cronjob" Camel component, with an operation "getCronJob", which
> would retrieve the {{CronJob}} manifest from k8s and put it into a message
> header or body.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (CAMEL-20159) Camel-AWS-Config: Add Test-infra module
[ https://issues.apache.org/jira/browse/CAMEL-20159?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Cosentino updated CAMEL-20159: - Fix Version/s: 4.3.0 (was: 4.x) > Camel-AWS-Config: Add Test-infra module > --- > > Key: CAMEL-20159 > URL: https://issues.apache.org/jira/browse/CAMEL-20159 > Project: Camel > Issue Type: New Feature >Reporter: Andrea Cosentino >Assignee: Andrea Cosentino >Priority: Major > Fix For: 4.3.0 > > > Localstack supports AWS Config in its community version -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (CAMEL-20159) Camel-AWS-Config: Add Test-infra module
[ https://issues.apache.org/jira/browse/CAMEL-20159?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Cosentino resolved CAMEL-20159. -- Resolution: Fixed > Camel-AWS-Config: Add Test-infra module > --- > > Key: CAMEL-20159 > URL: https://issues.apache.org/jira/browse/CAMEL-20159 > Project: Camel > Issue Type: New Feature >Reporter: Andrea Cosentino >Assignee: Andrea Cosentino >Priority: Major > Fix For: 4.3.0 > > > Localstack supports AWS Config in its community version -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (CAMEL-20152) camel-jetty - OutOfMemoryError with big file upload via multipart
[
https://issues.apache.org/jira/browse/CAMEL-20152?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17790676#comment-17790676
]
Andrea Cosentino commented on CAMEL-20152:
--
Thanks
> camel-jetty - OutOfMemoryError with big file upload via multipart
> -
>
> Key: CAMEL-20152
> URL: https://issues.apache.org/jira/browse/CAMEL-20152
> Project: Camel
> Issue Type: Bug
> Components: camel-jetty
>Affects Versions: 3.21.2
>Reporter: michael elbaz
>Assignee: Nicolas Filotto
>Priority: Major
> Attachments: image-2023-11-28-09-12-11-951.png
>
>
> I don't now if is related to jetty (maybe) but when i use camel with jetty
> and i upload a big file using multipart i get:
> {code:java}
> // espace r23:28:50.262 WARN [qtp1616084922-291] /email/myservice
> java.lang.IllegalStateException: java.lang.OutOfMemoryError: Java heap space
> at
> org.eclipse.jetty.http.MultiPartFormInputStream.throwIfError(MultiPartFormInputStream.java:517)
> ~[!/:9.4.52.v20230823]
> at
> org.eclipse.jetty.http.MultiPartFormInputStream.getParts(MultiPartFormInputStream.java:470)
> ~[!/:9.4.52.v20230823]
> at
> org.eclipse.jetty.server.MultiParts$MultiPartsHttpParser.getParts(MultiParts.java:74)
> ~[!/:9.4.52.v20230823]
> at org.eclipse.jetty.server.Request.getParts(Request.java:2450)
> ~[!/:9.4.52.v20230823]
> at org.eclipse.jetty.server.Request.getParts(Request.java:2420)
> ~[!/:9.4.52.v20230823]
> at
> org.apache.camel.component.jetty.MultiPartFilter.doFilter(MultiPartFilter.java:52)
> ~[?:?]
> at
> org.apache.camel.component.jetty.CamelFilterWrapper.doFilter(CamelFilterWrapper.java:49)
> ~[?:?]
> at
> org.eclipse.jetty.servlet.FilterHolder.doFilter(FilterHolder.java:193) ~[?:?]
> at
> org.eclipse.jetty.servlet.ServletHandler$Chain.doFilter(ServletHandler.java:1626)
> ~[?:?]
> at
> org.eclipse.jetty.servlet.ServletHandler.doHandle(ServletHandler.java:552)
> ~[?:?]
> at
> org.eclipse.jetty.server.handler.ScopedHandler.nextHandle(ScopedHandler.java:233)
> ~[!/:9.4.52.v20230823]
> at
> org.eclipse.jetty.server.handler.ContextHandler.doHandle(ContextHandler.java:1440)
> ~[!/:9.4.52.v20230823]
> at
> org.eclipse.jetty.server.handler.ScopedHandler.nextScope(ScopedHandler.java:188)
> ~[!/:9.4.52.v20230823]
> at
> org.eclipse.jetty.servlet.ServletHandler.doScope(ServletHandler.java:505)
> ~[?:?]
> at
> org.eclipse.jetty.server.handler.ScopedHandler.nextScope(ScopedHandler.java:186)
> ~[!/:9.4.52.v20230823]
> at
> org.eclipse.jetty.server.handler.ContextHandler.doScope(ContextHandler.java:1355)
> ~[!/:9.4.52.v20230823]
> at
> org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:141)
> ~[!/:9.4.52.v20230823]
> at
> org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:127)
> ~[!/:9.4.52.v20230823]
> at org.eclipse.jetty.server.Server.handle(Server.java:516)
> ~[!/:9.4.52.v20230823]
> at
> org.eclipse.jetty.server.HttpChannel.lambda$handle$1(HttpChannel.java:487)
> ~[!/:9.4.52.v20230823]
> at
> org.eclipse.jetty.server.HttpChannel.dispatch(HttpChannel.java:732)
> ~[!/:9.4.52.v20230823]
> at org.eclipse.jetty.server.HttpChannel.handle(HttpChannel.java:479)
> [!/:9.4.52.v20230823]
> at
> org.eclipse.jetty.server.HttpConnection.onFillable(HttpConnection.java:277)
> [!/:9.4.52.v20230823]
> at
> org.eclipse.jetty.io.AbstractConnection$ReadCallback.succeeded(AbstractConnection.java:311)
> [!/:9.4.52.v20230823]
> at org.eclipse.jetty.io.FillInterest.fillable(FillInterest.java:105)
> [!/:9.4.52.v20230823]
> at
> org.eclipse.jetty.io.ChannelEndPoint$1.run(ChannelEndPoint.java:104)
> [!/:9.4.52.v20230823]
> at
> org.eclipse.jetty.util.thread.QueuedThreadPool.runJob(QueuedThreadPool.java:883)
> [!/:9.4.52.v20230823]
> at
> org.eclipse.jetty.util.thread.QueuedThreadPool$Runner.run(QueuedThreadPool.java:1034)
> [!/:9.4.52.v20230823]
> at java.lang.Thread.run(Thread.java:833) [?:?]
> Caused by: java.lang.OutOfMemoryError: Java heap space
> at java.util.Arrays.copyOf(Arrays.java:3537) ~[?:?]
> at
> java.io.ByteArrayOutputStream.ensureCapacity(ByteArrayOutputStream.java:100)
> ~[?:?]
> at
> java.io.ByteArrayOutputStream.write(ByteArrayOutputStream.java:130) ~[?:?]
> at
> org.eclipse.jetty.http.MultiPartFormInputStream$MultiPart.write(MultiPartFormInputStream.java:178)
> ~[!/:9.4.52.v20230823]
> at
> org.eclipse.jetty.http.MultiPartFormInputStream$Handler.content(MultiPartFormInputStream.java:741)
> ~[!/:9.4.52.v20230823]
> at
> org.eclipse
[jira] [Commented] (CAMEL-20152) camel-jetty - OutOfMemoryError with big file upload via multipart
[
https://issues.apache.org/jira/browse/CAMEL-20152?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17790675#comment-17790675
]
Andrea Cosentino commented on CAMEL-20152:
--
Sounds good to me
> camel-jetty - OutOfMemoryError with big file upload via multipart
> -
>
> Key: CAMEL-20152
> URL: https://issues.apache.org/jira/browse/CAMEL-20152
> Project: Camel
> Issue Type: Bug
> Components: camel-jetty
>Affects Versions: 3.21.2
>Reporter: michael elbaz
>Assignee: Nicolas Filotto
>Priority: Major
> Attachments: image-2023-11-28-09-12-11-951.png
>
>
> I don't now if is related to jetty (maybe) but when i use camel with jetty
> and i upload a big file using multipart i get:
> {code:java}
> // espace r23:28:50.262 WARN [qtp1616084922-291] /email/myservice
> java.lang.IllegalStateException: java.lang.OutOfMemoryError: Java heap space
> at
> org.eclipse.jetty.http.MultiPartFormInputStream.throwIfError(MultiPartFormInputStream.java:517)
> ~[!/:9.4.52.v20230823]
> at
> org.eclipse.jetty.http.MultiPartFormInputStream.getParts(MultiPartFormInputStream.java:470)
> ~[!/:9.4.52.v20230823]
> at
> org.eclipse.jetty.server.MultiParts$MultiPartsHttpParser.getParts(MultiParts.java:74)
> ~[!/:9.4.52.v20230823]
> at org.eclipse.jetty.server.Request.getParts(Request.java:2450)
> ~[!/:9.4.52.v20230823]
> at org.eclipse.jetty.server.Request.getParts(Request.java:2420)
> ~[!/:9.4.52.v20230823]
> at
> org.apache.camel.component.jetty.MultiPartFilter.doFilter(MultiPartFilter.java:52)
> ~[?:?]
> at
> org.apache.camel.component.jetty.CamelFilterWrapper.doFilter(CamelFilterWrapper.java:49)
> ~[?:?]
> at
> org.eclipse.jetty.servlet.FilterHolder.doFilter(FilterHolder.java:193) ~[?:?]
> at
> org.eclipse.jetty.servlet.ServletHandler$Chain.doFilter(ServletHandler.java:1626)
> ~[?:?]
> at
> org.eclipse.jetty.servlet.ServletHandler.doHandle(ServletHandler.java:552)
> ~[?:?]
> at
> org.eclipse.jetty.server.handler.ScopedHandler.nextHandle(ScopedHandler.java:233)
> ~[!/:9.4.52.v20230823]
> at
> org.eclipse.jetty.server.handler.ContextHandler.doHandle(ContextHandler.java:1440)
> ~[!/:9.4.52.v20230823]
> at
> org.eclipse.jetty.server.handler.ScopedHandler.nextScope(ScopedHandler.java:188)
> ~[!/:9.4.52.v20230823]
> at
> org.eclipse.jetty.servlet.ServletHandler.doScope(ServletHandler.java:505)
> ~[?:?]
> at
> org.eclipse.jetty.server.handler.ScopedHandler.nextScope(ScopedHandler.java:186)
> ~[!/:9.4.52.v20230823]
> at
> org.eclipse.jetty.server.handler.ContextHandler.doScope(ContextHandler.java:1355)
> ~[!/:9.4.52.v20230823]
> at
> org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:141)
> ~[!/:9.4.52.v20230823]
> at
> org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:127)
> ~[!/:9.4.52.v20230823]
> at org.eclipse.jetty.server.Server.handle(Server.java:516)
> ~[!/:9.4.52.v20230823]
> at
> org.eclipse.jetty.server.HttpChannel.lambda$handle$1(HttpChannel.java:487)
> ~[!/:9.4.52.v20230823]
> at
> org.eclipse.jetty.server.HttpChannel.dispatch(HttpChannel.java:732)
> ~[!/:9.4.52.v20230823]
> at org.eclipse.jetty.server.HttpChannel.handle(HttpChannel.java:479)
> [!/:9.4.52.v20230823]
> at
> org.eclipse.jetty.server.HttpConnection.onFillable(HttpConnection.java:277)
> [!/:9.4.52.v20230823]
> at
> org.eclipse.jetty.io.AbstractConnection$ReadCallback.succeeded(AbstractConnection.java:311)
> [!/:9.4.52.v20230823]
> at org.eclipse.jetty.io.FillInterest.fillable(FillInterest.java:105)
> [!/:9.4.52.v20230823]
> at
> org.eclipse.jetty.io.ChannelEndPoint$1.run(ChannelEndPoint.java:104)
> [!/:9.4.52.v20230823]
> at
> org.eclipse.jetty.util.thread.QueuedThreadPool.runJob(QueuedThreadPool.java:883)
> [!/:9.4.52.v20230823]
> at
> org.eclipse.jetty.util.thread.QueuedThreadPool$Runner.run(QueuedThreadPool.java:1034)
> [!/:9.4.52.v20230823]
> at java.lang.Thread.run(Thread.java:833) [?:?]
> Caused by: java.lang.OutOfMemoryError: Java heap space
> at java.util.Arrays.copyOf(Arrays.java:3537) ~[?:?]
> at
> java.io.ByteArrayOutputStream.ensureCapacity(ByteArrayOutputStream.java:100)
> ~[?:?]
> at
> java.io.ByteArrayOutputStream.write(ByteArrayOutputStream.java:130) ~[?:?]
> at
> org.eclipse.jetty.http.MultiPartFormInputStream$MultiPart.write(MultiPartFormInputStream.java:178)
> ~[!/:9.4.52.v20230823]
> at
> org.eclipse.jetty.http.MultiPartFormInputStream$Handler.content(MultiPartFormInputStream.java:741)
> ~[!/:9.4.52.v20230823]
> at
>
[jira] [Resolved] (CAMEL-20162) Camel-AWS-Config: Add Describe Compliance By Config Rule operation
[ https://issues.apache.org/jira/browse/CAMEL-20162?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Cosentino resolved CAMEL-20162. -- Resolution: Fixed > Camel-AWS-Config: Add Describe Compliance By Config Rule operation > -- > > Key: CAMEL-20162 > URL: https://issues.apache.org/jira/browse/CAMEL-20162 > Project: Camel > Issue Type: New Feature > Components: camel-aws >Reporter: Andrea Cosentino >Assignee: Andrea Cosentino >Priority: Major > Fix For: 4.3.0 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (CAMEL-20162) Camel-AWS-Config: Add Describe Compliance By Config Rule operation
Andrea Cosentino created CAMEL-20162: Summary: Camel-AWS-Config: Add Describe Compliance By Config Rule operation Key: CAMEL-20162 URL: https://issues.apache.org/jira/browse/CAMEL-20162 Project: Camel Issue Type: New Feature Components: camel-aws Reporter: Andrea Cosentino Assignee: Andrea Cosentino Fix For: 4.3.0 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (CAMEL-20157) Add a Camel-AWS-Config component
[ https://issues.apache.org/jira/browse/CAMEL-20157?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Cosentino resolved CAMEL-20157. -- Resolution: Fixed > Add a Camel-AWS-Config component > > > Key: CAMEL-20157 > URL: https://issues.apache.org/jira/browse/CAMEL-20157 > Project: Camel > Issue Type: New Feature > Components: camel-aws >Reporter: Andrea Cosentino >Assignee: Andrea Cosentino >Priority: Major > Fix For: 4.3.0 > > > https://aws.amazon.com/config/ > With a component related to this, we can add/create rule to ensure compliancy > to specific rules on AWS Resources created. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (CAMEL-20152) OutOfMemoryError
[
https://issues.apache.org/jira/browse/CAMEL-20152?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17790471#comment-17790471
]
Andrea Cosentino commented on CAMEL-20152:
--
These are new features and they couldn't be add to 3.21.x, maybe they could go
on Camel 4 or Camel 3.22.0 if there is capacity and if they are not invasive.
> OutOfMemoryError
>
>
> Key: CAMEL-20152
> URL: https://issues.apache.org/jira/browse/CAMEL-20152
> Project: Camel
> Issue Type: Bug
> Components: camel-jetty
>Affects Versions: 3.21.2
>Reporter: michael elbaz
>Assignee: Nicolas Filotto
>Priority: Major
> Attachments: image-2023-11-28-09-12-11-951.png
>
>
> I don't now if is related to jetty (maybe) but when i use camel with jetty
> and i upload a big file using multipart i get:
> {code:java}
> // espace r23:28:50.262 WARN [qtp1616084922-291] /email/myservice
> java.lang.IllegalStateException: java.lang.OutOfMemoryError: Java heap space
> at
> org.eclipse.jetty.http.MultiPartFormInputStream.throwIfError(MultiPartFormInputStream.java:517)
> ~[!/:9.4.52.v20230823]
> at
> org.eclipse.jetty.http.MultiPartFormInputStream.getParts(MultiPartFormInputStream.java:470)
> ~[!/:9.4.52.v20230823]
> at
> org.eclipse.jetty.server.MultiParts$MultiPartsHttpParser.getParts(MultiParts.java:74)
> ~[!/:9.4.52.v20230823]
> at org.eclipse.jetty.server.Request.getParts(Request.java:2450)
> ~[!/:9.4.52.v20230823]
> at org.eclipse.jetty.server.Request.getParts(Request.java:2420)
> ~[!/:9.4.52.v20230823]
> at
> org.apache.camel.component.jetty.MultiPartFilter.doFilter(MultiPartFilter.java:52)
> ~[?:?]
> at
> org.apache.camel.component.jetty.CamelFilterWrapper.doFilter(CamelFilterWrapper.java:49)
> ~[?:?]
> at
> org.eclipse.jetty.servlet.FilterHolder.doFilter(FilterHolder.java:193) ~[?:?]
> at
> org.eclipse.jetty.servlet.ServletHandler$Chain.doFilter(ServletHandler.java:1626)
> ~[?:?]
> at
> org.eclipse.jetty.servlet.ServletHandler.doHandle(ServletHandler.java:552)
> ~[?:?]
> at
> org.eclipse.jetty.server.handler.ScopedHandler.nextHandle(ScopedHandler.java:233)
> ~[!/:9.4.52.v20230823]
> at
> org.eclipse.jetty.server.handler.ContextHandler.doHandle(ContextHandler.java:1440)
> ~[!/:9.4.52.v20230823]
> at
> org.eclipse.jetty.server.handler.ScopedHandler.nextScope(ScopedHandler.java:188)
> ~[!/:9.4.52.v20230823]
> at
> org.eclipse.jetty.servlet.ServletHandler.doScope(ServletHandler.java:505)
> ~[?:?]
> at
> org.eclipse.jetty.server.handler.ScopedHandler.nextScope(ScopedHandler.java:186)
> ~[!/:9.4.52.v20230823]
> at
> org.eclipse.jetty.server.handler.ContextHandler.doScope(ContextHandler.java:1355)
> ~[!/:9.4.52.v20230823]
> at
> org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:141)
> ~[!/:9.4.52.v20230823]
> at
> org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:127)
> ~[!/:9.4.52.v20230823]
> at org.eclipse.jetty.server.Server.handle(Server.java:516)
> ~[!/:9.4.52.v20230823]
> at
> org.eclipse.jetty.server.HttpChannel.lambda$handle$1(HttpChannel.java:487)
> ~[!/:9.4.52.v20230823]
> at
> org.eclipse.jetty.server.HttpChannel.dispatch(HttpChannel.java:732)
> ~[!/:9.4.52.v20230823]
> at org.eclipse.jetty.server.HttpChannel.handle(HttpChannel.java:479)
> [!/:9.4.52.v20230823]
> at
> org.eclipse.jetty.server.HttpConnection.onFillable(HttpConnection.java:277)
> [!/:9.4.52.v20230823]
> at
> org.eclipse.jetty.io.AbstractConnection$ReadCallback.succeeded(AbstractConnection.java:311)
> [!/:9.4.52.v20230823]
> at org.eclipse.jetty.io.FillInterest.fillable(FillInterest.java:105)
> [!/:9.4.52.v20230823]
> at
> org.eclipse.jetty.io.ChannelEndPoint$1.run(ChannelEndPoint.java:104)
> [!/:9.4.52.v20230823]
> at
> org.eclipse.jetty.util.thread.QueuedThreadPool.runJob(QueuedThreadPool.java:883)
> [!/:9.4.52.v20230823]
> at
> org.eclipse.jetty.util.thread.QueuedThreadPool$Runner.run(QueuedThreadPool.java:1034)
> [!/:9.4.52.v20230823]
> at java.lang.Thread.run(Thread.java:833) [?:?]
> Caused by: java.lang.OutOfMemoryError: Java heap space
> at java.util.Arrays.copyOf(Arrays.java:3537) ~[?:?]
> at
> java.io.ByteArrayOutputStream.ensureCapacity(ByteArrayOutputStream.java:100)
> ~[?:?]
> at
> java.io.ByteArrayOutputStream.write(ByteArrayOutputStream.java:130) ~[?:?]
> at
> org.eclipse.jetty.http.MultiPartFormInputStream$MultiPart.write(MultiPartFormInputStream.java:178)
> ~[!/:9.4.52.v20230823]
> at
> org.eclipse.jetty.http.MultiPartFormInputStream$Handler.content(MultiPartFormInputStream.java:741)
[jira] [Resolved] (CAMEL-20160) Camel-AWS-Config: Create Spring Boot Starter
[ https://issues.apache.org/jira/browse/CAMEL-20160?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Cosentino resolved CAMEL-20160. -- Resolution: Fixed > Camel-AWS-Config: Create Spring Boot Starter > > > Key: CAMEL-20160 > URL: https://issues.apache.org/jira/browse/CAMEL-20160 > Project: Camel > Issue Type: New Feature >Reporter: Andrea Cosentino >Assignee: Andrea Cosentino >Priority: Major > Fix For: 4.3.0 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (CAMEL-20160) Camel-AWS-Config: Create Spring Boot Starter
Andrea Cosentino created CAMEL-20160: Summary: Camel-AWS-Config: Create Spring Boot Starter Key: CAMEL-20160 URL: https://issues.apache.org/jira/browse/CAMEL-20160 Project: Camel Issue Type: New Feature Reporter: Andrea Cosentino -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (CAMEL-20160) Camel-AWS-Config: Create Spring Boot Starter
[ https://issues.apache.org/jira/browse/CAMEL-20160?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Cosentino updated CAMEL-20160: - Fix Version/s: 4.3.0 > Camel-AWS-Config: Create Spring Boot Starter > > > Key: CAMEL-20160 > URL: https://issues.apache.org/jira/browse/CAMEL-20160 > Project: Camel > Issue Type: New Feature >Reporter: Andrea Cosentino >Assignee: Andrea Cosentino >Priority: Major > Fix For: 4.3.0 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (CAMEL-20160) Camel-AWS-Config: Create Spring Boot Starter
[ https://issues.apache.org/jira/browse/CAMEL-20160?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Cosentino reassigned CAMEL-20160: Assignee: Andrea Cosentino > Camel-AWS-Config: Create Spring Boot Starter > > > Key: CAMEL-20160 > URL: https://issues.apache.org/jira/browse/CAMEL-20160 > Project: Camel > Issue Type: New Feature >Reporter: Andrea Cosentino >Assignee: Andrea Cosentino >Priority: Major > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (CAMEL-20159) Camel-AWS-Config: Add Test-infra module
Andrea Cosentino created CAMEL-20159: Summary: Camel-AWS-Config: Add Test-infra module Key: CAMEL-20159 URL: https://issues.apache.org/jira/browse/CAMEL-20159 Project: Camel Issue Type: New Feature Reporter: Andrea Cosentino Assignee: Andrea Cosentino Fix For: 4.x Localstack supports AWS Config in its community version -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (CAMEL-20157) Add a Camel-AWS-Config component
Andrea Cosentino created CAMEL-20157: Summary: Add a Camel-AWS-Config component Key: CAMEL-20157 URL: https://issues.apache.org/jira/browse/CAMEL-20157 Project: Camel Issue Type: New Feature Components: camel-aws Reporter: Andrea Cosentino Assignee: Andrea Cosentino Fix For: 4.3.0 https://aws.amazon.com/config/ With a component related to this, we can add/create rule to ensure compliancy to specific rules on AWS Resources created. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (CAMEL-20148) camel-spring-boot - Upgrade to 3.2
[ https://issues.apache.org/jira/browse/CAMEL-20148?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Cosentino reassigned CAMEL-20148: Assignee: (was: Andrea Cosentino) > camel-spring-boot - Upgrade to 3.2 > -- > > Key: CAMEL-20148 > URL: https://issues.apache.org/jira/browse/CAMEL-20148 > Project: Camel > Issue Type: Dependency upgrade > Components: camel-spring-boot >Reporter: Claus Ibsen >Priority: Major > Fix For: 4.3.0 > > > Also see CAMEL-19631 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (CAMEL-20148) camel-spring-boot - Upgrade to 3.2
[
https://issues.apache.org/jira/browse/CAMEL-20148?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17789377#comment-17789377
]
Andrea Cosentino commented on CAMEL-20148:
--
{code:java}
[ERROR] Failed to execute goal
org.apache.maven.plugins:maven-compiler-plugin:3.11.0:compile (default-compile)
on project camel-micrometer-starter: Compilation failure: Compilation failure:
[ERROR]
/home/oscerd/workspace/apache-camel/camel-spring-boot/components-starter/camel-micrometer-starter/src/main/java/org/apache/camel/component/micrometer/springboot/MicrometerTagsAutoConfiguration.java:[30,60]
package org.springframework.boot.actuate.metrics.web.servlet does not exist
[ERROR]
/home/oscerd/workspace/apache-camel/camel-spring-boot/components-starter/camel-micrometer-starter/src/main/java/org/apache/camel/component/micrometer/springboot/MicrometerTagsAutoConfiguration.java:[31,60]
package org.springframework.boot.actuate.metrics.web.servlet does not exist
[ERROR]
/home/oscerd/workspace/apache-camel/camel-spring-boot/components-starter/camel-micrometer-starter/src/main/java/org/apache/camel/component/micrometer/springboot/MicrometerTagsAutoConfiguration.java:[54,5]
cannot find symbol
[ERROR] symbol: class WebMvcTagsProvider
[ERROR] location: class
org.apache.camel.component.micrometer.springboot.MicrometerTagsAutoConfiguration
[ERROR] -> [Help 1]
{code}
> camel-spring-boot - Upgrade to 3.2
> --
>
> Key: CAMEL-20148
> URL: https://issues.apache.org/jira/browse/CAMEL-20148
> Project: Camel
> Issue Type: Dependency upgrade
> Components: camel-spring-boot
>Reporter: Claus Ibsen
>Priority: Major
> Fix For: 4.3.0
>
>
> Also see CAMEL-19631
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Assigned] (CAMEL-20148) camel-spring-boot - Upgrade to 3.2
[ https://issues.apache.org/jira/browse/CAMEL-20148?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Cosentino reassigned CAMEL-20148: Assignee: Andrea Cosentino > camel-spring-boot - Upgrade to 3.2 > -- > > Key: CAMEL-20148 > URL: https://issues.apache.org/jira/browse/CAMEL-20148 > Project: Camel > Issue Type: Dependency upgrade > Components: camel-spring-boot >Reporter: Claus Ibsen >Assignee: Andrea Cosentino >Priority: Major > Fix For: 4.3.0 > > > Also see CAMEL-19631 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (CAMEL-20149) Release guide: Add instructions to sign and publish SBOM files to dist/release folder
Andrea Cosentino created CAMEL-20149: Summary: Release guide: Add instructions to sign and publish SBOM files to dist/release folder Key: CAMEL-20149 URL: https://issues.apache.org/jira/browse/CAMEL-20149 Project: Camel Issue Type: Task Reporter: Andrea Cosentino Assignee: Andrea Cosentino Fix For: 4.3.0 We had this discussion and discovered we are not uploading the SBOMs to dist/release The release guide needs to be updated for Camel and Camel Spring Boot. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (CAMEL-20147) camel-spring-boot: Upgrade to 3.1.6
Andrea Cosentino created CAMEL-20147: Summary: camel-spring-boot: Upgrade to 3.1.6 Key: CAMEL-20147 URL: https://issues.apache.org/jira/browse/CAMEL-20147 Project: Camel Issue Type: Dependency upgrade Reporter: Andrea Cosentino Assignee: Andrea Cosentino Fix For: 4.0.4 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (CAMEL-19973) Camel-AWS components: Revisit description
[ https://issues.apache.org/jira/browse/CAMEL-19973?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Cosentino updated CAMEL-19973: - Fix Version/s: 4.3.0 (was: 4.x) > Camel-AWS components: Revisit description > - > > Key: CAMEL-19973 > URL: https://issues.apache.org/jira/browse/CAMEL-19973 > Project: Camel > Issue Type: Task >Reporter: Andrea Cosentino >Assignee: Andrea Cosentino >Priority: Major > Fix For: 4.3.0 > > > Some of them are copied and pasted, some are inaccurate -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (CAMEL-19973) Camel-AWS components: Revisit description
[ https://issues.apache.org/jira/browse/CAMEL-19973?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Cosentino resolved CAMEL-19973. -- Resolution: Fixed > Camel-AWS components: Revisit description > - > > Key: CAMEL-19973 > URL: https://issues.apache.org/jira/browse/CAMEL-19973 > Project: Camel > Issue Type: Task >Reporter: Andrea Cosentino >Assignee: Andrea Cosentino >Priority: Major > Fix For: 4.3.0 > > > Some of them are copied and pasted, some are inaccurate -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (CAMEL-20138) Avoid time out during dependabot Check Update job
[
https://issues.apache.org/jira/browse/CAMEL-20138?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17788677#comment-17788677
]
Andrea Cosentino commented on CAMEL-20138:
--
No, it doesn't.
The SNAPSHOT repository is coming from Apache Parent POM
> Avoid time out during dependabot Check Update job
> -
>
> Key: CAMEL-20138
> URL: https://issues.apache.org/jira/browse/CAMEL-20138
> Project: Camel
> Issue Type: Task
> Components: build system
>Reporter: Aurélien Pupier
>Priority: Major
>
> The dependabot jobs are currently taking more than 45 minutes and are failing
> in timeout (not a problem right now as it always has enough dependencies
> update to provide)
> {noformat}
> proxy | 2023/11/21 06:29:21 proxy starting, commit:
> 6cffd6fae1b2f713f2d837bc45fe916f855c821d
> {noformat}
> {noformat}
> updater | time="2023-11-21T07:15:42Z" level=warning msg="timeout running job"
> error="waiting for updater: waiting for container: context deadline exceeded"
> job_id=752523002
> updater | 2023/11/21 07:15:42 Unsolicited response received on idle HTTP
> channel starting with "0\r\n"; err=
> updater | 2023/11/21 07:15:42 Unsolicited response received on idle HTTP
> channel starting with "0\r\n"; err=
> {noformat}
> [GitHub is suggesting to limit the number of dependencies to
> check|https://docs.github.com/en/code-security/dependabot/working-with-dependabot/troubleshooting-dependabot-errors#dependabot-timed-out-during-its-update]
> (but in our case we will miss the purpose of it)
> One point that i observed is that the Apache snapshot repository is checked.
> As far as I know it is usually a slow one and i do not think that we care
> about snapshots version. i think this could be the first point to try:
> removing the Apache Snapshots repo during this check
> {noformat}
> proxy | 2023/11/21 06:45:01 [390] HEAD
> https://repository.apache.org:443/snapshots/org/infinispan/infinispan-core/14.0.21.Final/infinispan-core-14.0.21.Final.test-jar
> {noformat}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Comment Edited] (CAMEL-20138) Avoid time out during dependabot Check Update job
[
https://issues.apache.org/jira/browse/CAMEL-20138?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17788677#comment-17788677
]
Andrea Cosentino edited comment on CAMEL-20138 at 11/22/23 9:11 AM:
No, it doesn't.
The SNAPSHOT repository is coming from Apache Parent POM:
https://github.com/apache/maven-apache-parent/blob/master/pom.xml#L158
was (Author: ancosen):
No, it doesn't.
The SNAPSHOT repository is coming from Apache Parent POM
> Avoid time out during dependabot Check Update job
> -
>
> Key: CAMEL-20138
> URL: https://issues.apache.org/jira/browse/CAMEL-20138
> Project: Camel
> Issue Type: Task
> Components: build system
>Reporter: Aurélien Pupier
>Priority: Major
>
> The dependabot jobs are currently taking more than 45 minutes and are failing
> in timeout (not a problem right now as it always has enough dependencies
> update to provide)
> {noformat}
> proxy | 2023/11/21 06:29:21 proxy starting, commit:
> 6cffd6fae1b2f713f2d837bc45fe916f855c821d
> {noformat}
> {noformat}
> updater | time="2023-11-21T07:15:42Z" level=warning msg="timeout running job"
> error="waiting for updater: waiting for container: context deadline exceeded"
> job_id=752523002
> updater | 2023/11/21 07:15:42 Unsolicited response received on idle HTTP
> channel starting with "0\r\n"; err=
> updater | 2023/11/21 07:15:42 Unsolicited response received on idle HTTP
> channel starting with "0\r\n"; err=
> {noformat}
> [GitHub is suggesting to limit the number of dependencies to
> check|https://docs.github.com/en/code-security/dependabot/working-with-dependabot/troubleshooting-dependabot-errors#dependabot-timed-out-during-its-update]
> (but in our case we will miss the purpose of it)
> One point that i observed is that the Apache snapshot repository is checked.
> As far as I know it is usually a slow one and i do not think that we care
> about snapshots version. i think this could be the first point to try:
> removing the Apache Snapshots repo during this check
> {noformat}
> proxy | 2023/11/21 06:45:01 [390] HEAD
> https://repository.apache.org:443/snapshots/org/infinispan/infinispan-core/14.0.21.Final/infinispan-core-14.0.21.Final.test-jar
> {noformat}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (CAMEL-20133) Regen_bot branches: Reviews all the branches and restart from scratch
[ https://issues.apache.org/jira/browse/CAMEL-20133?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Cosentino updated CAMEL-20133: - Summary: Regen_bot branches: Reviews all the branches and restart from scratch (was: Regen_bot branches: Reviews all the branch and restart from scratch) > Regen_bot branches: Reviews all the branches and restart from scratch > - > > Key: CAMEL-20133 > URL: https://issues.apache.org/jira/browse/CAMEL-20133 > Project: Camel > Issue Type: Bug >Reporter: Andrea Cosentino >Assignee: Andrea Cosentino >Priority: Major > Fix For: 4.3.0 > > > regen_bot branch is polluted with multiple branches, we need to go through > the active branches and create a dedicated regen_bot_version branch from the > last tag. Otherwise we'll have invalid PRs. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (CAMEL-20133) Regen_bot branches: Reviews all the branch and restart from scratch
Andrea Cosentino created CAMEL-20133: Summary: Regen_bot branches: Reviews all the branch and restart from scratch Key: CAMEL-20133 URL: https://issues.apache.org/jira/browse/CAMEL-20133 Project: Camel Issue Type: Bug Reporter: Andrea Cosentino Assignee: Andrea Cosentino Fix For: 4.3.0 regen_bot branch is polluted with multiple branches, we need to go through the active branches and create a dedicated regen_bot_version branch from the last tag. Otherwise we'll have invalid PRs. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (CAMEL-20129) Upgrade Localstack to version 3.0.0
[ https://issues.apache.org/jira/browse/CAMEL-20129?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Cosentino resolved CAMEL-20129. -- Resolution: Fixed > Upgrade Localstack to version 3.0.0 > --- > > Key: CAMEL-20129 > URL: https://issues.apache.org/jira/browse/CAMEL-20129 > Project: Camel > Issue Type: Dependency upgrade >Reporter: Andrea Cosentino >Assignee: Andrea Cosentino >Priority: Major > Fix For: 4.3.0 > > > This should also solve the SQS API breaking change. > https://github.com/localstack/localstack/releases/tag/v3.0.0 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (CAMEL-20129) Upgrade Localstack to version 3.0.0
Andrea Cosentino created CAMEL-20129: Summary: Upgrade Localstack to version 3.0.0 Key: CAMEL-20129 URL: https://issues.apache.org/jira/browse/CAMEL-20129 Project: Camel Issue Type: Dependency upgrade Reporter: Andrea Cosentino Assignee: Andrea Cosentino Fix For: 4.3.0 This should also solve the SQS API breaking change. https://github.com/localstack/localstack/releases/tag/v3.0.0 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (CAMEL-20117) Johnzon-jsonb: Update to 2.0.0
[ https://issues.apache.org/jira/browse/CAMEL-20117?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Cosentino resolved CAMEL-20117. -- Resolution: Fixed > Johnzon-jsonb: Update to 2.0.0 > -- > > Key: CAMEL-20117 > URL: https://issues.apache.org/jira/browse/CAMEL-20117 > Project: Camel > Issue Type: Dependency upgrade >Reporter: Andrea Cosentino >Assignee: Andrea Cosentino >Priority: Major > Fix For: 4.3.0 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (CAMEL-20117) Johnzon-jsonb: Update to 2.0.0
Andrea Cosentino created CAMEL-20117: Summary: Johnzon-jsonb: Update to 2.0.0 Key: CAMEL-20117 URL: https://issues.apache.org/jira/browse/CAMEL-20117 Project: Camel Issue Type: Dependency upgrade Reporter: Andrea Cosentino Assignee: Andrea Cosentino Fix For: 4.3.0 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (CAMEL-20116) Upgrade to Jackson BOM 2.16.0
Andrea Cosentino created CAMEL-20116: Summary: 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 Reporter: Andrea Cosentino Assignee: Andrea Cosentino Fix For: 4.3.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-20049) camel-activemq - Upgrade to latest releases
[ https://issues.apache.org/jira/browse/CAMEL-20049?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17786712#comment-17786712 ] Andrea Cosentino commented on CAMEL-20049: -- It is used only as test dependencies. You're not really exposed to anything, also we are not spinning up an ActiveMQ server. You need to have an ActiveMQ server running for exploiting this CVE: https://github.com/oscerd/nice-cve-poc/tree/main/CVE-2023-46604 and we are not doing it. I understand your point and I understand you're giving trust to Snyk, but it is a test dependency and I think you can manage to make the Snyk static analyzer to ignore test dependencies. This reports needs to be analyzed with a grain of salt sometimes. > camel-activemq - Upgrade to latest releases > --- > > Key: CAMEL-20049 > URL: https://issues.apache.org/jira/browse/CAMEL-20049 > Project: Camel > Issue Type: Dependency upgrade > Components: camel-activemq >Reporter: Claus Ibsen >Assignee: Claus Ibsen >Priority: Major > Fix For: 3.14.10, 3.20.9, 3.21.3, 3.22.0, 4.0.3, 4.2.0 > > Attachments: screenshot-1.png > > > There are new releases of ActiveMQ and Artemis. > Though we only use this for testing but we need to be using latest releases. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Comment Edited] (CAMEL-20049) camel-activemq - Upgrade to latest releases
[ https://issues.apache.org/jira/browse/CAMEL-20049?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17786712#comment-17786712 ] Andrea Cosentino edited comment on CAMEL-20049 at 11/16/23 11:24 AM: - It is used only as test dependency. You're not really exposed to anything, also we are not spinning up an ActiveMQ server. You need to have an ActiveMQ server running for exploiting this CVE: https://github.com/oscerd/nice-cve-poc/tree/main/CVE-2023-46604 and we are not doing it. I understand your point and I understand you're giving trust to Snyk, but it is a test dependency and I think you can manage to make the Snyk static analyzer to ignore test dependencies. This reports needs to be analyzed with a grain of salt sometimes. was (Author: ancosen): It is used only as test dependencies. You're not really exposed to anything, also we are not spinning up an ActiveMQ server. You need to have an ActiveMQ server running for exploiting this CVE: https://github.com/oscerd/nice-cve-poc/tree/main/CVE-2023-46604 and we are not doing it. I understand your point and I understand you're giving trust to Snyk, but it is a test dependency and I think you can manage to make the Snyk static analyzer to ignore test dependencies. This reports needs to be analyzed with a grain of salt sometimes. > camel-activemq - Upgrade to latest releases > --- > > Key: CAMEL-20049 > URL: https://issues.apache.org/jira/browse/CAMEL-20049 > Project: Camel > Issue Type: Dependency upgrade > Components: camel-activemq >Reporter: Claus Ibsen >Assignee: Claus Ibsen >Priority: Major > Fix For: 3.14.10, 3.20.9, 3.21.3, 3.22.0, 4.0.3, 4.2.0 > > Attachments: screenshot-1.png > > > There are new releases of ActiveMQ and Artemis. > Though we only use this for testing but we need to be using latest releases. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (CAMEL-20087) Backport data types from Kamelet utils to Camel
[ https://issues.apache.org/jira/browse/CAMEL-20087?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17784407#comment-17784407 ] Andrea Cosentino commented on CAMEL-20087: -- This is done. With [~christophd] we would like to move also the bits related to kafka transformation and processors, directly in kafka component, but it could be for 4.3.0 LTS. > Backport data types from Kamelet utils to Camel > --- > > Key: CAMEL-20087 > URL: https://issues.apache.org/jira/browse/CAMEL-20087 > Project: Camel > Issue Type: Improvement > Components: camel-kamelet >Reporter: Christoph Deppisch >Assignee: Christoph Deppisch >Priority: Major > Fix For: 4.2.0 > > > The camel-kamelets-utils library > ([https://github.com/apache/camel-kamelets/tree/main/library/camel-kamelets-utils/src/main/java/org/apache/camel/kamelets/utils/format/converter)] > provides several data type implementations that can be used as declarative > data transformations. > Data types are not bound to Kamelets anymore but can be used in all Camel > routes. We should move these implementations to the respective Camel > components in the Camel repository in order to also leverage the automatic > meta data generation for these data types. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (CAMEL-20087) Backport data types from Kamelet utils to Camel
[ https://issues.apache.org/jira/browse/CAMEL-20087?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Cosentino resolved CAMEL-20087. -- Resolution: Fixed > Backport data types from Kamelet utils to Camel > --- > > Key: CAMEL-20087 > URL: https://issues.apache.org/jira/browse/CAMEL-20087 > Project: Camel > Issue Type: Improvement > Components: camel-kamelet >Reporter: Christoph Deppisch >Assignee: Christoph Deppisch >Priority: Major > Fix For: 4.2.0 > > > The camel-kamelets-utils library > ([https://github.com/apache/camel-kamelets/tree/main/library/camel-kamelets-utils/src/main/java/org/apache/camel/kamelets/utils/format/converter)] > provides several data type implementations that can be used as declarative > data transformations. > Data types are not bound to Kamelets anymore but can be used in all Camel > routes. We should move these implementations to the respective Camel > components in the Camel repository in order to also leverage the automatic > meta data generation for these data types. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (CAMEL-20087) Backport data types from Kamelet utils to Camel
[ https://issues.apache.org/jira/browse/CAMEL-20087?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Cosentino updated CAMEL-20087: - Fix Version/s: 4.2.0 (was: 4.x) > Backport data types from Kamelet utils to Camel > --- > > Key: CAMEL-20087 > URL: https://issues.apache.org/jira/browse/CAMEL-20087 > Project: Camel > Issue Type: Improvement > Components: camel-kamelet >Reporter: Christoph Deppisch >Assignee: Christoph Deppisch >Priority: Major > Fix For: 4.2.0 > > > The camel-kamelets-utils library > ([https://github.com/apache/camel-kamelets/tree/main/library/camel-kamelets-utils/src/main/java/org/apache/camel/kamelets/utils/format/converter)] > provides several data type implementations that can be used as declarative > data transformations. > Data types are not bound to Kamelets anymore but can be used in all Camel > routes. We should move these implementations to the respective Camel > components in the Camel repository in order to also leverage the automatic > meta data generation for these data types. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (CAMEL-20092) camel-core - ScheduledPollConsumer should reset error count when greedy
[ https://issues.apache.org/jira/browse/CAMEL-20092?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Cosentino updated CAMEL-20092: - Fix Version/s: (was: 3.20.9) > camel-core - ScheduledPollConsumer should reset error count when greedy > --- > > Key: CAMEL-20092 > URL: https://issues.apache.org/jira/browse/CAMEL-20092 > Project: Camel > Issue Type: Bug >Affects Versions: 3.21.2 >Reporter: Simon Rasmussen >Assignee: Simon Rasmussen >Priority: Major > Fix For: 3.21.3, 3.22.0, 4.0.3, 4.2.0 > > > We have had the following scenario happen to us on a SQS consumer with > greedy=true: > poll 1: fails with exception, causing error count to increase to 1 (due to > sqs problem) > poll 2: successfully poll, and since greedy, continues with the next poll. > This continued for 1 hour as the queue it polled from had many messages > Since the error count wasn't updated, then our readiness check remained DOWN > for a full hour even though the application actually processed messages of > the queue. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (CAMEL-20092) camel-core - ScheduledPollConsumer should reset error count when greedy
[ https://issues.apache.org/jira/browse/CAMEL-20092?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Cosentino resolved CAMEL-20092. -- Resolution: Fixed > camel-core - ScheduledPollConsumer should reset error count when greedy > --- > > Key: CAMEL-20092 > URL: https://issues.apache.org/jira/browse/CAMEL-20092 > Project: Camel > Issue Type: Bug >Affects Versions: 3.21.2 >Reporter: Simon Rasmussen >Assignee: Simon Rasmussen >Priority: Major > Fix For: 3.21.3, 3.22.0, 4.0.3, 4.2.0 > > > We have had the following scenario happen to us on a SQS consumer with > greedy=true: > poll 1: fails with exception, causing error count to increase to 1 (due to > sqs problem) > poll 2: successfully poll, and since greedy, continues with the next poll. > This continued for 1 hour as the queue it polled from had many messages > Since the error count wasn't updated, then our readiness check remained DOWN > for a full hour even though the application actually processed messages of > the queue. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (CAMEL-20092) camel-core - ScheduledPollConsumer should reset error count when greedy
[ https://issues.apache.org/jira/browse/CAMEL-20092?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Cosentino updated CAMEL-20092: - Fix Version/s: 3.22.0 (was: 3.x) > camel-core - ScheduledPollConsumer should reset error count when greedy > --- > > Key: CAMEL-20092 > URL: https://issues.apache.org/jira/browse/CAMEL-20092 > Project: Camel > Issue Type: Bug >Affects Versions: 3.21.2 >Reporter: Simon Rasmussen >Assignee: Simon Rasmussen >Priority: Major > Fix For: 3.20.9, 3.21.3, 3.22.0, 4.0.3, 4.2.0 > > > We have had the following scenario happen to us on a SQS consumer with > greedy=true: > poll 1: fails with exception, causing error count to increase to 1 (due to > sqs problem) > poll 2: successfully poll, and since greedy, continues with the next poll. > This continued for 1 hour as the queue it polled from had many messages > Since the error count wasn't updated, then our readiness check remained DOWN > for a full hour even though the application actually processed messages of > the queue. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (CAMEL-20085) camel-aws - Sqs consumer throws unhandled exception during deleteMessage, should be caught by exception handler in consumer
[
https://issues.apache.org/jira/browse/CAMEL-20085?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrea Cosentino updated CAMEL-20085:
-
Fix Version/s: 3.20.9
3.21.3
3.x
4.0.3
> camel-aws - Sqs consumer throws unhandled exception during deleteMessage,
> should be caught by exception handler in consumer
> ---
>
> Key: CAMEL-20085
> URL: https://issues.apache.org/jira/browse/CAMEL-20085
> Project: Camel
> Issue Type: Improvement
> Components: camel-aws2
>Affects Versions: 3.21.1
>Reporter: Simon Rasmussen
>Assignee: Simon Rasmussen
>Priority: Major
> Fix For: 3.20.9, 3.21.3, 3.x, 4.0.3, 4.2.0
>
>
> We have observed that SQS based consumers throws an exception which is not
> handled by the exception handler, this causes a verbose error in the logs. We
> should catch that exception directly and print a warn using the error handler
> which can then be bridged as any other exception.
> {code:java}
> 2023-11-04 12:10:20.351 WARN 11 --- [ebhook_incoming]
> o.apache.camel.support.UnitOfWorkHelper : [] Exception occurred during
> onCompletion. This exception will be ignored.
> software.amazon.awssdk.core.exception.SdkClientException: Unable to execute
> HTTP request: Connection reset by peer at
> software.amazon.awssdk.core.exception.SdkClientException$BuilderImpl.build(SdkClientException.java:111)
> ~[sdk-core-2.20.99.jar:na] at
> software.amazon.awssdk.core.exception.SdkClientException.create(SdkClientException.java:47)
> ~[sdk-core-2.20.99.jar:na] at
> software.amazon.awssdk.core.internal.http.pipeline.stages.utils.RetryableStageHelper.setLastException(RetryableStageHelper.java:223)
> ~[sdk-core-2.20.99.jar:na] at
> software.amazon.awssdk.core.internal.http.pipeline.stages.RetryableStage.execute(RetryableStage.java:83)
> ~[sdk-core-2.20.99.jar:na] at
> software.amazon.awssdk.core.internal.http.pipeline.stages.RetryableStage.execute(RetryableStage.java:36)
> ~[sdk-core-2.20.99.jar:na] at
> software.amazon.awssdk.core.internal.http.pipeline.RequestPipelineBuilder$ComposingRequestPipelineStage.execute(RequestPipelineBuilder.java:206)
> ~[sdk-core-2.20.99.jar:na] at
> software.amazon.awssdk.core.internal.http.StreamManagingStage.execute(StreamManagingStage.java:56)
> ~[sdk-core-2.20.99.jar:na] at
> software.amazon.awssdk.core.internal.http.StreamManagingStage.execute(StreamManagingStage.java:36)
> ~[sdk-core-2.20.99.jar:na] at
> software.amazon.awssdk.core.internal.http.pipeline.stages.ApiCallTimeoutTrackingStage.executeWithTimer(ApiCallTimeoutTrackingStage.java:80)
> ~[sdk-core-2.20.99.jar:na] at
> software.amazon.awssdk.core.internal.http.pipeline.stages.ApiCallTimeoutTrackingStage.execute(ApiCallTimeoutTrackingStage.java:60)
> ~[sdk-core-2.20.99.jar:na] at
> software.amazon.awssdk.core.internal.http.pipeline.stages.ApiCallTimeoutTrackingStage.execute(ApiCallTimeoutTrackingStage.java:42)
> ~[sdk-core-2.20.99.jar:na] at
> software.amazon.awssdk.core.internal.http.pipeline.stages.ApiCallMetricCollectionStage.execute(ApiCallMetricCollectionStage.java:48)
> ~[sdk-core-2.20.99.jar:na] at
> software.amazon.awssdk.core.internal.http.pipeline.stages.ApiCallMetricCollectionStage.execute(ApiCallMetricCollectionStage.java:31)
> ~[sdk-core-2.20.99.jar:na] at
> software.amazon.awssdk.core.internal.http.pipeline.RequestPipelineBuilder$ComposingRequestPipelineStage.execute(RequestPipelineBuilder.java:206)
> ~[sdk-core-2.20.99.jar:na] at
> software.amazon.awssdk.core.internal.http.pipeline.RequestPipelineBuilder$ComposingRequestPipelineStage.execute(RequestPipelineBuilder.java:206)
> ~[sdk-core-2.20.99.jar:na] at
> software.amazon.awssdk.core.internal.http.pipeline.stages.ExecutionFailureExceptionReportingStage.execute(ExecutionFailureExceptionReportingStage.java:37)
> ~[sdk-core-2.20.99.jar:na] at
> software.amazon.awssdk.core.internal.http.pipeline.stages.ExecutionFailureExceptionReportingStage.execute(ExecutionFailureExceptionReportingStage.java:26)
> ~[sdk-core-2.20.99.jar:na] at
> software.amazon.awssdk.core.internal.http.AmazonSyncHttpClient$RequestExecutionBuilderImpl.execute(AmazonSyncHttpClient.java:193)
> ~[sdk-core-2.20.99.jar:na] at
> software.amazon.awssdk.core.internal.handler.BaseSyncClientHandler.invoke(BaseSyncClientHandler.java:103)
> ~[sdk-core-2.20.99.jar:na] at
> software.amazon.awssdk.core.internal.handler.BaseSyncClientHandler.doExecute(BaseSyncClientHandler.java:171)
> ~[sdk-core-2.20.99.jar:na] at
> software.amazon.awssdk.core.internal.handler.BaseSyncClientHandler.lambda$execute$1(BaseSyncClientHandler.java:82)
> ~[sdk-core-2.20.99.jar:na] at
> software.amazon.awssdk.core.internal.handler.BaseSy
[jira] [Updated] (CAMEL-20092) camel-core - ScheduledPollConsumer should reset error count when greedy
[ https://issues.apache.org/jira/browse/CAMEL-20092?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Cosentino updated CAMEL-20092: - Fix Version/s: 3.20.9 3.x > camel-core - ScheduledPollConsumer should reset error count when greedy > --- > > Key: CAMEL-20092 > URL: https://issues.apache.org/jira/browse/CAMEL-20092 > Project: Camel > Issue Type: Bug >Affects Versions: 3.21.2 >Reporter: Simon Rasmussen >Assignee: Simon Rasmussen >Priority: Major > Fix For: 3.20.9, 3.21.3, 3.x, 4.0.3, 4.2.0 > > > We have had the following scenario happen to us on a SQS consumer with > greedy=true: > poll 1: fails with exception, causing error count to increase to 1 (due to > sqs problem) > poll 2: successfully poll, and since greedy, continues with the next poll. > This continued for 1 hour as the queue it polled from had many messages > Since the error count wasn't updated, then our readiness check remained DOWN > for a full hour even though the application actually processed messages of > the queue. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (CAMEL-20087) Backport data types from Kamelet utils to Camel
[ https://issues.apache.org/jira/browse/CAMEL-20087?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Cosentino reassigned CAMEL-20087: Assignee: Christoph Deppisch > Backport data types from Kamelet utils to Camel > --- > > Key: CAMEL-20087 > URL: https://issues.apache.org/jira/browse/CAMEL-20087 > Project: Camel > Issue Type: Improvement > Components: camel-kamelet >Reporter: Christoph Deppisch >Assignee: Christoph Deppisch >Priority: Major > Fix For: 4.x > > > The camel-kamelets-utils library > ([https://github.com/apache/camel-kamelets/tree/main/library/camel-kamelets-utils/src/main/java/org/apache/camel/kamelets/utils/format/converter)] > provides several data type implementations that can be used as declarative > data transformations. > Data types are not bound to Kamelets anymore but can be used in all Camel > routes. We should move these implementations to the respective Camel > components in the Camel repository in order to also leverage the automatic > meta data generation for these data types. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (CAMEL-20088) Camel-Azure-Schema-Registry component: Moving the bits from camel-kamelets and have a non-classic component
[ https://issues.apache.org/jira/browse/CAMEL-20088?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Cosentino resolved CAMEL-20088. -- Resolution: Fixed > Camel-Azure-Schema-Registry component: Moving the bits from camel-kamelets > and have a non-classic component > --- > > Key: CAMEL-20088 > URL: https://issues.apache.org/jira/browse/CAMEL-20088 > Project: Camel > Issue Type: New Feature >Reporter: Andrea Cosentino >Assignee: Andrea Cosentino >Priority: Major > Fix For: 4.2.0 > > > In Camel-Kamelets we have a particular class to deal with the authentication > of Azure Schema Registry. Instead of polluting the Camel-Kamelets repository, > we should start to create specialized components (like camel-headersmap, so > non-classical component) for Schema Registries, so we could simply re-use > some logic in the Kamelets and in other flavors if needed. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (CAMEL-20088) Camel-Azure-Schema-Registry component: Moving the bits from camel-kamelets and have a non-classic component
Andrea Cosentino created CAMEL-20088: Summary: Camel-Azure-Schema-Registry component: Moving the bits from camel-kamelets and have a non-classic component Key: CAMEL-20088 URL: https://issues.apache.org/jira/browse/CAMEL-20088 Project: Camel Issue Type: New Feature Reporter: Andrea Cosentino Assignee: Andrea Cosentino Fix For: 4.2.0 In Camel-Kamelets we have a particular class to deal with the authentication of Azure Schema Registry. Instead of polluting the Camel-Kamelets repository, we should start to create specialized components (like camel-headersmap, so non-classical component) for Schema Registries, so we could simply re-use some logic in the Kamelets and in other flavors if needed. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (CAMEL-20084) Create a Camel-SMB Spring Boot Starter
[ https://issues.apache.org/jira/browse/CAMEL-20084?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Cosentino resolved CAMEL-20084. -- Resolution: Fixed > Create a Camel-SMB Spring Boot Starter > -- > > Key: CAMEL-20084 > URL: https://issues.apache.org/jira/browse/CAMEL-20084 > Project: Camel > Issue Type: Task > Components: camel-spring-boot >Reporter: Andrea Cosentino >Assignee: Andrea Cosentino >Priority: Major > Fix For: 4.2.0 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (CAMEL-20084) Create a Camel-SMB Spring Boot Starter
Andrea Cosentino created CAMEL-20084: Summary: Create a Camel-SMB Spring Boot Starter Key: CAMEL-20084 URL: https://issues.apache.org/jira/browse/CAMEL-20084 Project: Camel Issue Type: Task Components: camel-spring-boot Reporter: Andrea Cosentino Assignee: Andrea Cosentino Fix For: 4.2.0 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (CAMEL-19961) Missing Features in Camel Spring RabbitMQ in Camel 3.21.0
[ https://issues.apache.org/jira/browse/CAMEL-19961?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17783131#comment-17783131 ] Andrea Cosentino commented on CAMEL-19961: -- December 2023. > Missing Features in Camel Spring RabbitMQ in Camel 3.21.0 > - > > Key: CAMEL-19961 > URL: https://issues.apache.org/jira/browse/CAMEL-19961 > Project: Camel > Issue Type: Improvement > Components: camel-rabbitmq, camel-spring-rabbitmq >Affects Versions: 3.21.0 >Reporter: Tanay Agarwal >Priority: Minor > Fix For: 3.22.0 > > > According to the Camel-RabbitMQ documentation > [https://camel.apache.org/components/3.21.x/rabbitmq-component.html], it is > advisable to employ the Camel Spring RabbitMQ Component. I am currently > utilizing the most recent version of Camel, which is Version 3.21.0. However, > I have observed that in this particular version, the Camel Spring RabbitMQ > Component lacks certain headers that are available in the RabbitMQ Component. > In contrast, these headers are present in Camel 4. Unfortunately, I am unable > to migrate to Camel 4 at this time. Therefore, I am inquiring whether there > are any plans to incorporate these headers into Camel 3, or if it is feasible > to do so. Your guidance on this matter would be greatly appreciated. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (CAMEL-20072) Upgrade Google Cloud BOM to version 26.26.0
[ https://issues.apache.org/jira/browse/CAMEL-20072?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Cosentino resolved CAMEL-20072. -- Resolution: Fixed > Upgrade Google Cloud BOM to version 26.26.0 > --- > > Key: CAMEL-20072 > URL: https://issues.apache.org/jira/browse/CAMEL-20072 > Project: Camel > Issue Type: Dependency upgrade >Reporter: Andrea Cosentino >Assignee: Andrea Cosentino >Priority: Major > Fix For: 4.2.0 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (CAMEL-20075) camel-kubernetes - upgrade to 6.9.2
[ https://issues.apache.org/jira/browse/CAMEL-20075?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Cosentino resolved CAMEL-20075. -- Resolution: Fixed > camel-kubernetes - upgrade to 6.9.2 > --- > > Key: CAMEL-20075 > URL: https://issues.apache.org/jira/browse/CAMEL-20075 > Project: Camel > Issue Type: Dependency upgrade > Components: camel-kubernetes >Reporter: Claus Ibsen >Assignee: Andrea Cosentino >Priority: Minor > Fix For: 4.2.0 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (CAMEL-20069) Upgrade Azure SDK BOM to version 1.2.18
[ https://issues.apache.org/jira/browse/CAMEL-20069?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Cosentino resolved CAMEL-20069. -- Resolution: Fixed > Upgrade Azure SDK BOM to version 1.2.18 > --- > > Key: CAMEL-20069 > URL: https://issues.apache.org/jira/browse/CAMEL-20069 > Project: Camel > Issue Type: Dependency upgrade >Reporter: Andrea Cosentino >Assignee: Andrea Cosentino >Priority: Major > Fix For: 4.2.0 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (CAMEL-20073) Bump google-cloud-functions-bom to version 2.31.0
[ https://issues.apache.org/jira/browse/CAMEL-20073?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Cosentino resolved CAMEL-20073. -- Resolution: Fixed > Bump google-cloud-functions-bom to version 2.31.0 > - > > Key: CAMEL-20073 > URL: https://issues.apache.org/jira/browse/CAMEL-20073 > Project: Camel > Issue Type: Dependency upgrade >Reporter: Andrea Cosentino >Assignee: Andrea Cosentino >Priority: Major > Fix For: 4.2.0 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (CAMEL-20074) Bump google-cloud-secretmanager-bom to version 2.29.0
[ https://issues.apache.org/jira/browse/CAMEL-20074?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Cosentino resolved CAMEL-20074. -- Resolution: Fixed > Bump google-cloud-secretmanager-bom to version 2.29.0 > - > > Key: CAMEL-20074 > URL: https://issues.apache.org/jira/browse/CAMEL-20074 > Project: Camel > Issue Type: Dependency upgrade >Reporter: Andrea Cosentino >Assignee: Andrea Cosentino >Priority: Major > Fix For: 4.2.0 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (CAMEL-20075) camel-kubernetes - upgrade to 6.9.2
[ https://issues.apache.org/jira/browse/CAMEL-20075?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Cosentino reassigned CAMEL-20075: Assignee: Andrea Cosentino > camel-kubernetes - upgrade to 6.9.2 > --- > > Key: CAMEL-20075 > URL: https://issues.apache.org/jira/browse/CAMEL-20075 > Project: Camel > Issue Type: Dependency upgrade > Components: camel-kubernetes >Reporter: Claus Ibsen >Assignee: Andrea Cosentino >Priority: Minor > Fix For: 4.2.0 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (CAMEL-20072) Upgrade Google Cloud BOM to version 26.26.0
Andrea Cosentino created CAMEL-20072: Summary: Upgrade Google Cloud BOM to version 26.26.0 Key: CAMEL-20072 URL: https://issues.apache.org/jira/browse/CAMEL-20072 Project: Camel Issue Type: Dependency upgrade Reporter: Andrea Cosentino Assignee: Andrea Cosentino Fix For: 4.2.0 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (CAMEL-20074) Bump google-cloud-secretmanager-bom to version 2.29.0
Andrea Cosentino created CAMEL-20074: Summary: Bump google-cloud-secretmanager-bom to version 2.29.0 Key: CAMEL-20074 URL: https://issues.apache.org/jira/browse/CAMEL-20074 Project: Camel Issue Type: Dependency upgrade Reporter: Andrea Cosentino Assignee: Andrea Cosentino Fix For: 4.2.0 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (CAMEL-20073) Bump google-cloud-functions-bom to version 2.31.0
Andrea Cosentino created CAMEL-20073: Summary: Bump google-cloud-functions-bom to version 2.31.0 Key: CAMEL-20073 URL: https://issues.apache.org/jira/browse/CAMEL-20073 Project: Camel Issue Type: Dependency upgrade Reporter: Andrea Cosentino Assignee: Andrea Cosentino Fix For: 4.2.0 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (CAMEL-20069) Upgrade Azure SDK BOM to version 1.2.18
Andrea Cosentino created CAMEL-20069: Summary: Upgrade Azure SDK BOM to version 1.2.18 Key: CAMEL-20069 URL: https://issues.apache.org/jira/browse/CAMEL-20069 Project: Camel Issue Type: Dependency upgrade Reporter: Andrea Cosentino Assignee: Andrea Cosentino Fix For: 4.2.0 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (CAMEL-20063) camel-jbang - Upgrade to kamelets 4.1.0
[ https://issues.apache.org/jira/browse/CAMEL-20063?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Cosentino resolved CAMEL-20063. -- Resolution: Fixed > camel-jbang - Upgrade to kamelets 4.1.0 > --- > > Key: CAMEL-20063 > URL: https://issues.apache.org/jira/browse/CAMEL-20063 > Project: Camel > Issue Type: Dependency upgrade > Components: camel-jbang >Reporter: Claus Ibsen >Assignee: Andrea Cosentino >Priority: Minor > Fix For: 4.2.0 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (CAMEL-20063) camel-jbang - Upgrade to kamelets 4.1.0
[ https://issues.apache.org/jira/browse/CAMEL-20063?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Cosentino reassigned CAMEL-20063: Assignee: Andrea Cosentino > camel-jbang - Upgrade to kamelets 4.1.0 > --- > > Key: CAMEL-20063 > URL: https://issues.apache.org/jira/browse/CAMEL-20063 > Project: Camel > Issue Type: Dependency upgrade > Components: camel-jbang >Reporter: Claus Ibsen >Assignee: Andrea Cosentino >Priority: Minor > Fix For: 4.2.0 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (CAMEL-20060) Add Azure SAS support for azure blob storage
[ https://issues.apache.org/jira/browse/CAMEL-20060?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Cosentino updated CAMEL-20060: - Fix Version/s: 4.2.0 (was: 4.x) > Add Azure SAS support for azure blob storage > > > Key: CAMEL-20060 > URL: https://issues.apache.org/jira/browse/CAMEL-20060 > Project: Camel > Issue Type: Improvement > Components: camel-azure >Reporter: Andrea Cosentino >Assignee: Andrea Cosentino >Priority: Major > Fix For: 4.2.0 > > > We already have the same for Datalake. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (CAMEL-20060) Add Azure SAS support for azure blob storage
[ https://issues.apache.org/jira/browse/CAMEL-20060?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Cosentino resolved CAMEL-20060. -- Resolution: Fixed > Add Azure SAS support for azure blob storage > > > Key: CAMEL-20060 > URL: https://issues.apache.org/jira/browse/CAMEL-20060 > Project: Camel > Issue Type: Improvement > Components: camel-azure >Reporter: Andrea Cosentino >Assignee: Andrea Cosentino >Priority: Major > Fix For: 4.2.0 > > > We already have the same for Datalake. -- This message was sent by Atlassian Jira (v8.20.10#820010)
