[jira] [Created] (CAMEL-21061) Google Secrets Manager Properties function: Add documentation about creating required infra
Andrea Cosentino created CAMEL-21061: Summary: Google Secrets Manager Properties function: Add documentation about creating required infra Key: CAMEL-21061 URL: https://issues.apache.org/jira/browse/CAMEL-21061 Project: Camel Issue Type: Task Reporter: Andrea Cosentino Assignee: Andrea Cosentino Fix For: 4.x -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (CAMEL-21062) Azure Key Vault Properties function: Add documentation about creating required infra
Andrea Cosentino created CAMEL-21062: Summary: Azure Key Vault Properties function: Add documentation about creating required infra Key: CAMEL-21062 URL: https://issues.apache.org/jira/browse/CAMEL-21062 Project: Camel Issue Type: Task Reporter: Andrea Cosentino Assignee: Andrea Cosentino Fix For: 4.x -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (CAMEL-21060) AWS Secrets Manager Properties function: Add documentation about creating required infra
Andrea Cosentino created CAMEL-21060: Summary: AWS Secrets Manager Properties function: Add documentation about creating required infra Key: CAMEL-21060 URL: https://issues.apache.org/jira/browse/CAMEL-21060 Project: Camel Issue Type: Task Reporter: Andrea Cosentino Assignee: Andrea Cosentino Fix For: 4.x -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (CAMEL-21010) camel-milvus: collection name mismatch with embeddings
[
https://issues.apache.org/jira/browse/CAMEL-21010?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrea Cosentino resolved CAMEL-21010.
--
Resolution: Information Provided
> camel-milvus: collection name mismatch with embeddings
> --
>
> Key: CAMEL-21010
> URL: https://issues.apache.org/jira/browse/CAMEL-21010
> Project: Camel
> Issue Type: Task
> Components: camel-milvus
>Affects Versions: 4.7.0
>Reporter: Otavio Rodolfo Piske
>Assignee: Andrea Cosentino
>Priority: Major
> Fix For: 4.8.0
>
>
> The embedding component and the Milvus component in Camel have different
> behaviors when it comes to handling collection names.
> The embedding component requires the collection name to be specified as a
> header, while the Milvus component allows for a different collection name to
> be used.
> For instance:
> {code:java}
>
>MyTestCollectionName2
>
>
>
> {code}
> This inconsistency can lead to confusion and errors when trying to use both
> components together. It would be beneficial to standardize the behavior of
> these components so that they can work seamlessly with each other.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (CAMEL-21010) camel-milvus: collection name mismatch with embeddings
[
https://issues.apache.org/jira/browse/CAMEL-21010?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17871644#comment-17871644
]
Andrea Cosentino commented on CAMEL-21010:
--
There is no easy way of doing this because the library works differently in
relation to Qdrant. We need to specify the collectionName at POJO level when
doing insert/upsert. This means we have to pass it via an header. I think we
should document this in the component doc.
> camel-milvus: collection name mismatch with embeddings
> --
>
> Key: CAMEL-21010
> URL: https://issues.apache.org/jira/browse/CAMEL-21010
> Project: Camel
> Issue Type: Task
> Components: camel-milvus
>Affects Versions: 4.7.0
>Reporter: Otavio Rodolfo Piske
>Assignee: Andrea Cosentino
>Priority: Major
> Fix For: 4.8.0
>
>
> The embedding component and the Milvus component in Camel have different
> behaviors when it comes to handling collection names.
> The embedding component requires the collection name to be specified as a
> header, while the Milvus component allows for a different collection name to
> be used.
> For instance:
> {code:java}
>
>MyTestCollectionName2
>
>
>
> {code}
> This inconsistency can lead to confusion and errors when trying to use both
> components together. It would be beneficial to standardize the behavior of
> these components so that they can work seamlessly with each other.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Resolved] (CAMEL-21012) camel-milvus: action name mismatch with embeddings
[
https://issues.apache.org/jira/browse/CAMEL-21012?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrea Cosentino resolved CAMEL-21012.
--
Resolution: Fixed
> camel-milvus: action name mismatch with embeddings
> --
>
> Key: CAMEL-21012
> URL: https://issues.apache.org/jira/browse/CAMEL-21012
> Project: Camel
> Issue Type: Task
> Components: camel-milvus
>Affects Versions: 4.7.0
>Reporter: Otavio Rodolfo Piske
>Assignee: Andrea Cosentino
>Priority: Major
> Fix For: 4.8.0
>
>
> The embedding component and the Milvus component in Camel have different
> behaviors when it comes to handling actions
> The embedding component requires the action name to be specified as a header:
> {code:xml}
>
> UPSERT
>
> {code}
> However, this causes problems when using in combination with the Milvus
> embedding, because the transformer creates a InsertParam object.
> The problem is in the `private void upsert(Exchange exchange)` method from
> MilvusProducer.java. When we try to get the body of the message, we look for
> an `UpsertParam.class`.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Resolved] (CAMEL-21023) Camel-Spring-Boot: Add Langchain component starters Integration tests
[ https://issues.apache.org/jira/browse/CAMEL-21023?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Cosentino resolved CAMEL-21023. -- Resolution: Fixed > Camel-Spring-Boot: Add Langchain component starters Integration tests > - > > Key: CAMEL-21023 > URL: https://issues.apache.org/jira/browse/CAMEL-21023 > Project: Camel > Issue Type: Task > Components: camel-spring-boot >Reporter: Andrea Cosentino >Assignee: Andrea Cosentino >Priority: Major > Fix For: 4.8.0 > > > They're missing in the set. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (CAMEL-21037) Camel-Jbang Kubernetes Plugin: In case of Spring Boot runtime and OCP target we should use jkube openshift-maven-plugin instead of kubernetes-maven-plugin
[ https://issues.apache.org/jira/browse/CAMEL-21037?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Cosentino updated CAMEL-21037: - Description: I guess this needs to be addressed. By following the documentation, deploying on OCP doesn't work with the current POM template. (was: I guess this needs to be addressed. By testing following the documentation, deploying on OCP doesn't work with the current POM template.) > Camel-Jbang Kubernetes Plugin: In case of Spring Boot runtime and OCP target > we should use jkube openshift-maven-plugin instead of kubernetes-maven-plugin > -- > > Key: CAMEL-21037 > URL: https://issues.apache.org/jira/browse/CAMEL-21037 > Project: Camel > Issue Type: Improvement >Reporter: Andrea Cosentino >Assignee: Thomas Diesler >Priority: Major > Fix For: 4.x > > > I guess this needs to be addressed. By following the documentation, deploying > on OCP doesn't work with the current POM template. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (CAMEL-21037) Camel-Jbang Kubernetes Plugin: In case of Spring Boot runtime and OCP target we should use jkube openshift-maven-plugin instead of kubernetes-maven-plugin
[ https://issues.apache.org/jira/browse/CAMEL-21037?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17869897#comment-17869897 ] Andrea Cosentino commented on CAMEL-21037: -- [~tdiesler] I assigned this to you, because you worked on the feature. Let me know if you have time. > Camel-Jbang Kubernetes Plugin: In case of Spring Boot runtime and OCP target > we should use jkube openshift-maven-plugin instead of kubernetes-maven-plugin > -- > > Key: CAMEL-21037 > URL: https://issues.apache.org/jira/browse/CAMEL-21037 > Project: Camel > Issue Type: Improvement >Reporter: Andrea Cosentino >Assignee: Thomas Diesler >Priority: Major > Fix For: 4.x > > > I guess this needs to be addressed. By testing following the documentation, > deploying on OCP doesn't work with the current POM template. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (CAMEL-21037) Camel-Jbang Kubernetes Plugin: In case of Spring Boot runtime and OCP target we should use jkube openshift-maven-plugin instead of kubernetes-maven-plugin
Andrea Cosentino created CAMEL-21037: Summary: Camel-Jbang Kubernetes Plugin: In case of Spring Boot runtime and OCP target we should use jkube openshift-maven-plugin instead of kubernetes-maven-plugin Key: CAMEL-21037 URL: https://issues.apache.org/jira/browse/CAMEL-21037 Project: Camel Issue Type: Improvement Reporter: Andrea Cosentino Assignee: Thomas Diesler Fix For: 4.x I guess this needs to be addressed. By testing following the documentation, deploying on OCP doesn't work with the current POM template. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (CAMEL-21021) Camel-AWS-Secrets-Manager: Give the ability of refreshing the context on Secrets update by using Eventbridge service instead of pure Cloudtrail
[ https://issues.apache.org/jira/browse/CAMEL-21021?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Cosentino resolved CAMEL-21021. -- Resolution: Fixed > Camel-AWS-Secrets-Manager: Give the ability of refreshing the context on > Secrets update by using Eventbridge service instead of pure Cloudtrail > --- > > Key: CAMEL-21021 > URL: https://issues.apache.org/jira/browse/CAMEL-21021 > Project: Camel > Issue Type: New Feature >Reporter: Andrea Cosentino >Assignee: Andrea Cosentino >Priority: Major > Fix For: 4.8.0 > > > Eventbridge could send events to SQS or SNS, we can choose SQS for > convenience as default. It's far more reliable than waiting for events > publish on Cloudtrail and we could be able to refresh the context faster. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (CAMEL-21025) Camel-AWS-Secrets-Manager: Give the ability of refreshing the context on Secrets update by using Eventbridge service instead of pure Cloudtrail - Spring Boot support
[ https://issues.apache.org/jira/browse/CAMEL-21025?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Cosentino resolved CAMEL-21025. -- Resolution: Fixed > Camel-AWS-Secrets-Manager: Give the ability of refreshing the context on > Secrets update by using Eventbridge service instead of pure Cloudtrail - > Spring Boot support > - > > Key: CAMEL-21025 > URL: https://issues.apache.org/jira/browse/CAMEL-21025 > Project: Camel > Issue Type: Sub-task >Reporter: Andrea Cosentino >Assignee: Andrea Cosentino >Priority: Major > Fix For: 4.8.0 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (CAMEL-21024) Camel-AWS-Secrets-Manager: Eventbridge/SQS notifications documentation
[ https://issues.apache.org/jira/browse/CAMEL-21024?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Cosentino resolved CAMEL-21024. -- Resolution: Fixed > Camel-AWS-Secrets-Manager: Eventbridge/SQS notifications documentation > -- > > Key: CAMEL-21024 > URL: https://issues.apache.org/jira/browse/CAMEL-21024 > Project: Camel > Issue Type: Sub-task >Reporter: Andrea Cosentino >Assignee: Andrea Cosentino >Priority: Major > Fix For: 4.8.0 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (CAMEL-21024) Camel-AWS-Secrets-Manager: Eventbridge/SQS notifications documentation
Andrea Cosentino created CAMEL-21024: Summary: Camel-AWS-Secrets-Manager: Eventbridge/SQS notifications documentation Key: CAMEL-21024 URL: https://issues.apache.org/jira/browse/CAMEL-21024 Project: Camel Issue Type: Sub-task Reporter: Andrea Cosentino Assignee: Andrea Cosentino Fix For: 4.8.0 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (CAMEL-21025) Camel-AWS-Secrets-Manager: Give the ability of refreshing the context on Secrets update by using Eventbridge service instead of pure Cloudtrail - Spring Boot support
Andrea Cosentino created CAMEL-21025: Summary: Camel-AWS-Secrets-Manager: Give the ability of refreshing the context on Secrets update by using Eventbridge service instead of pure Cloudtrail - Spring Boot support Key: CAMEL-21025 URL: https://issues.apache.org/jira/browse/CAMEL-21025 Project: Camel Issue Type: Sub-task Reporter: Andrea Cosentino Assignee: Andrea Cosentino Fix For: 4.8.0 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (CAMEL-21022) Create Camel Langchain4j Web Search Starter
[ https://issues.apache.org/jira/browse/CAMEL-21022?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Cosentino resolved CAMEL-21022. -- Resolution: Fixed > Create Camel Langchain4j Web Search Starter > --- > > Key: CAMEL-21022 > URL: https://issues.apache.org/jira/browse/CAMEL-21022 > Project: Camel > Issue Type: Task > Components: camel-spring-boot >Reporter: Andrea Cosentino >Assignee: Andrea Cosentino >Priority: Major > Fix For: 4.8.0 > > > Website is failing the build -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (CAMEL-21023) Camel-Spring-Boot: Add Langchain component starters Integration tests
Andrea Cosentino created CAMEL-21023: Summary: Camel-Spring-Boot: Add Langchain component starters Integration tests Key: CAMEL-21023 URL: https://issues.apache.org/jira/browse/CAMEL-21023 Project: Camel Issue Type: Task Components: camel-spring-boot Reporter: Andrea Cosentino Assignee: Andrea Cosentino Fix For: 4.8.0 They're missing in the set. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (CAMEL-21022) Create Camel Langchain4j Web Search Starter
Andrea Cosentino created CAMEL-21022: Summary: Create Camel Langchain4j Web Search Starter Key: CAMEL-21022 URL: https://issues.apache.org/jira/browse/CAMEL-21022 Project: Camel Issue Type: Task Components: camel-spring-boot Reporter: Andrea Cosentino Assignee: Andrea Cosentino Fix For: 4.8.0 Website is failing the build -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (CAMEL-21021) Camel-AWS-Secrets-Manager: Give the ability of refreshing the context on Secrets update by using Eventbridge service instead of pure Cloudtrail
[ https://issues.apache.org/jira/browse/CAMEL-21021?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Cosentino updated CAMEL-21021: - Summary: Camel-AWS-Secrets-Manager: Give the ability of refreshing the context on Secrets update by using Eventbridge service instead of pure Cloudtrail (was: Camel-AWS-Secrets-Manager: Give the ability of refreshing the context on Secrets update by using Eventbridge service instead then pure Cloudtrail) > Camel-AWS-Secrets-Manager: Give the ability of refreshing the context on > Secrets update by using Eventbridge service instead of pure Cloudtrail > --- > > Key: CAMEL-21021 > URL: https://issues.apache.org/jira/browse/CAMEL-21021 > Project: Camel > Issue Type: New Feature >Reporter: Andrea Cosentino >Assignee: Andrea Cosentino >Priority: Major > Fix For: 4.8.0 > > > Eventbridge could send events to SQS or SNS, we can choose SQS for > convenience as default. It's far more reliable than waiting for events > publish on Cloudtrail and we could be able to refresh the context faster. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (CAMEL-21021) Camel-AWS-Secrets-Manager: Give the ability of refreshing the context on Secrets update by using Eventbridge service instead then pure Cloudtrail
[ https://issues.apache.org/jira/browse/CAMEL-21021?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Cosentino updated CAMEL-21021: - Summary: Camel-AWS-Secrets-Manager: Give the ability of refreshing the context on Secrets update by using Eventbridge service instead then pure Cloudtrail (was: Camel-AWS-Secrets-Manager: Give the ability of refreshing the context on Secrets update, by using Eventbridge service instead then pure Cloudtrail) > Camel-AWS-Secrets-Manager: Give the ability of refreshing the context on > Secrets update by using Eventbridge service instead then pure Cloudtrail > - > > Key: CAMEL-21021 > URL: https://issues.apache.org/jira/browse/CAMEL-21021 > Project: Camel > Issue Type: New Feature >Reporter: Andrea Cosentino >Assignee: Andrea Cosentino >Priority: Major > Fix For: 4.8.0 > > > Eventbridge could send events to SQS or SNS, we can choose SQS for > convenience as default. It's far more reliable than waiting for events > publish on Cloudtrail and we could be able to refresh the context faster. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (CAMEL-21021) Camel-AWS-Secrets-Manager: Give the ability of refreshing the context on Secrets update, by using Eventbridge service instead then pure Cloudtrail
Andrea Cosentino created CAMEL-21021: Summary: Camel-AWS-Secrets-Manager: Give the ability of refreshing the context on Secrets update, by using Eventbridge service instead then pure Cloudtrail Key: CAMEL-21021 URL: https://issues.apache.org/jira/browse/CAMEL-21021 Project: Camel Issue Type: New Feature Reporter: Andrea Cosentino Assignee: Andrea Cosentino Fix For: 4.8.0 Eventbridge could send events to SQS or SNS, we can choose SQS for convenience as default. It's far more reliable than waiting for events publish on Cloudtrail and we could be able to refresh the context faster. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Comment Edited] (CAMEL-21012) camel-milvus: action name mismatch with embeddings
[
https://issues.apache.org/jira/browse/CAMEL-21012?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17868914#comment-17868914
]
Andrea Cosentino edited comment on CAMEL-21012 at 7/26/24 10:30 AM:
Can you provide an example of what you're doing? The transforms are aimend to
be used with langchain-embeddings component only. So in the end you're not
going to do an upsert, or at least the basic idea is to insert a new object.
was (Author: ancosen):
Can you provide an example of what you're doing. The transforms are aimend to
be used with langchain-embeddings component only
> camel-milvus: action name mismatch with embeddings
> --
>
> Key: CAMEL-21012
> URL: https://issues.apache.org/jira/browse/CAMEL-21012
> Project: Camel
> Issue Type: Task
> Components: camel-milvus
>Affects Versions: 4.7.0
>Reporter: Otavio Rodolfo Piske
>Assignee: Andrea Cosentino
>Priority: Major
> Fix For: 4.8.0
>
>
> The embedding component and the Milvus component in Camel have different
> behaviors when it comes to handling actions
> The embedding component requires the action name to be specified as a header:
> {code:xml}
>
> UPSERT
>
> {code}
> However, this causes problems when using in combination with the Milvus
> embedding, because the transformer creates a InsertParam object.
> The problem is in the `private void upsert(Exchange exchange)` method from
> MilvusProducer.java. When we try to get the body of the message, we look for
> an `UpsertParam.class`.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (CAMEL-21012) camel-milvus: action name mismatch with embeddings
[
https://issues.apache.org/jira/browse/CAMEL-21012?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17868914#comment-17868914
]
Andrea Cosentino commented on CAMEL-21012:
--
Can you provide an example of what you're doing. The transforms are aimend to
be used with langchain-embeddings component only
> camel-milvus: action name mismatch with embeddings
> --
>
> Key: CAMEL-21012
> URL: https://issues.apache.org/jira/browse/CAMEL-21012
> Project: Camel
> Issue Type: Task
> Components: camel-milvus
>Affects Versions: 4.7.0
>Reporter: Otavio Rodolfo Piske
>Assignee: Andrea Cosentino
>Priority: Major
> Fix For: 4.8.0
>
>
> The embedding component and the Milvus component in Camel have different
> behaviors when it comes to handling actions
> The embedding component requires the action name to be specified as a header:
> {code:xml}
>
> UPSERT
>
> {code}
> However, this causes problems when using in combination with the Milvus
> embedding, because the transformer creates a InsertParam object.
> The problem is in the `private void upsert(Exchange exchange)` method from
> MilvusProducer.java. When we try to get the body of the message, we look for
> an `UpsertParam.class`.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Resolved] (CAMEL-21009) Camel-AWS2-Kinesis: CloudWatchAsyncClient and DynamoDbAsyncClient parameters are ignored from KCL Consumer
[ https://issues.apache.org/jira/browse/CAMEL-21009?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Cosentino resolved CAMEL-21009. -- Resolution: Fixed > Camel-AWS2-Kinesis: CloudWatchAsyncClient and DynamoDbAsyncClient parameters > are ignored from KCL Consumer > -- > > Key: CAMEL-21009 > URL: https://issues.apache.org/jira/browse/CAMEL-21009 > Project: Camel > Issue Type: Bug >Affects Versions: 4.7.0 >Reporter: Andrea Cosentino >Assignee: Andrea Cosentino >Priority: Major > Fix For: 4.8.0 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (CAMEL-21009) Camel-AWS2-Kinesis: CloudWatchAsyncClient and DynamoDbAsyncClient parameters are ignored from KCL Consumer
[ https://issues.apache.org/jira/browse/CAMEL-21009?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Cosentino updated CAMEL-21009: - Affects Version/s: 4.7.0 > Camel-AWS2-Kinesis: CloudWatchAsyncClient and DynamoDbAsyncClient parameters > are ignored from KCL Consumer > -- > > Key: CAMEL-21009 > URL: https://issues.apache.org/jira/browse/CAMEL-21009 > Project: Camel > Issue Type: Bug >Affects Versions: 4.7.0 >Reporter: Andrea Cosentino >Assignee: Andrea Cosentino >Priority: Major > Fix For: 4.8.0 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (CAMEL-20765) Camel-AWS-Bedrock: Support Amazon Titan Text Embeddings V2
[ https://issues.apache.org/jira/browse/CAMEL-20765?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Cosentino updated CAMEL-20765: - Fix Version/s: 4.8.0 (was: 4.x) > Camel-AWS-Bedrock: Support Amazon Titan Text Embeddings V2 > -- > > Key: CAMEL-20765 > URL: https://issues.apache.org/jira/browse/CAMEL-20765 > Project: Camel > Issue Type: Sub-task > Components: camel-aws >Reporter: Andrea Cosentino >Assignee: Andrea Cosentino >Priority: Major > Fix For: 4.8.0 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (CAMEL-20765) Camel-AWS-Bedrock: Support Amazon Titan Text Embeddings V2
[ https://issues.apache.org/jira/browse/CAMEL-20765?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Cosentino resolved CAMEL-20765. -- Resolution: Fixed > Camel-AWS-Bedrock: Support Amazon Titan Text Embeddings V2 > -- > > Key: CAMEL-20765 > URL: https://issues.apache.org/jira/browse/CAMEL-20765 > Project: Camel > Issue Type: Sub-task > Components: camel-aws >Reporter: Andrea Cosentino >Assignee: Andrea Cosentino >Priority: Major > Fix For: 4.x > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (CAMEL-21010) camel-milvus: collection name mismatch with embeddings
[
https://issues.apache.org/jira/browse/CAMEL-21010?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrea Cosentino updated CAMEL-21010:
-
Fix Version/s: 4.8.0
> camel-milvus: collection name mismatch with embeddings
> --
>
> Key: CAMEL-21010
> URL: https://issues.apache.org/jira/browse/CAMEL-21010
> Project: Camel
> Issue Type: Task
> Components: camel-milvus
>Affects Versions: 4.7.0
>Reporter: Otavio Rodolfo Piske
>Assignee: Andrea Cosentino
>Priority: Major
> Fix For: 4.8.0
>
>
> The embedding component and the Milvus component in Camel have different
> behaviors when it comes to handling collection names.
> The embedding component requires the collection name to be specified as a
> header, while the Milvus component allows for a different collection name to
> be used.
> For instance:
> {code:java}
>
>MyTestCollectionName2
>
>
>
> {code}
> This inconsistency can lead to confusion and errors when trying to use both
> components together. It would be beneficial to standardize the behavior of
> these components so that they can work seamlessly with each other.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Assigned] (CAMEL-21010) camel-milvus: collection name mismatch with embeddings
[
https://issues.apache.org/jira/browse/CAMEL-21010?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrea Cosentino reassigned CAMEL-21010:
Assignee: Andrea Cosentino
> camel-milvus: collection name mismatch with embeddings
> --
>
> Key: CAMEL-21010
> URL: https://issues.apache.org/jira/browse/CAMEL-21010
> Project: Camel
> Issue Type: Task
> Components: camel-milvus
>Affects Versions: 4.7.0
>Reporter: Otavio Rodolfo Piske
>Assignee: Andrea Cosentino
>Priority: Major
>
> The embedding component and the Milvus component in Camel have different
> behaviors when it comes to handling collection names.
> The embedding component requires the collection name to be specified as a
> header, while the Milvus component allows for a different collection name to
> be used.
> For instance:
> {code:java}
>
>MyTestCollectionName2
>
>
>
> {code}
> This inconsistency can lead to confusion and errors when trying to use both
> components together. It would be beneficial to standardize the behavior of
> these components so that they can work seamlessly with each other.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Created] (CAMEL-21009) Camel-AWS2-Kinesis: CloudWatchAsyncClient and DynamoDbAsyncClient parameters are ignored from KCL Consumer
Andrea Cosentino created CAMEL-21009: Summary: Camel-AWS2-Kinesis: CloudWatchAsyncClient and DynamoDbAsyncClient parameters are ignored from KCL Consumer Key: CAMEL-21009 URL: https://issues.apache.org/jira/browse/CAMEL-21009 Project: Camel Issue Type: Bug Reporter: Andrea Cosentino Assignee: Andrea Cosentino Fix For: 4.8.0 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (CAMEL-20995) camel-azure-storage-blob uploadBlockBlob retry operation fails due to mark and reset issue / Flux
[ https://issues.apache.org/jira/browse/CAMEL-20995?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Cosentino resolved CAMEL-20995. -- Resolution: Fixed > camel-azure-storage-blob uploadBlockBlob retry operation fails due to mark > and reset issue / Flux > - > > Key: CAMEL-20995 > URL: https://issues.apache.org/jira/browse/CAMEL-20995 > Project: Camel > Issue Type: Bug > Components: camel-azure >Affects Versions: 4.0.0, 4.4.0, 4.7.0 >Reporter: Hareesh Billa >Assignee: Andrea Cosentino >Priority: Minor > Fix For: 4.0.6, 4.4.4, 4.8.0 > > Attachments: Code snip.png, Log trace > > > camel-azure-storage-blob uploadBlockBlob retry operation fails due to mark > and reset issue / Flux > Due to some of the issues Azure blob storage retrying for upload again, but > it is failed to upload due to the input stream length is 0 which is not > expected. > As per the azure core/common bode Flux code suggestion it is suggested to > make markAndreset request parameter to *true,* But the out camel component > always send the parameter value as false. > *Solution:* Instead of sending the default value to false, we can use > inputStream.markSupported() method. > Here I am adding traces and screenshots, for easy understanding. > Thanks. > > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (CAMEL-20140) camel-report:route-coverage results in no code coverage
[
https://issues.apache.org/jira/browse/CAMEL-20140?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17868064#comment-17868064
]
Andrea Cosentino commented on CAMEL-20140:
--
The fix on 4.0.6, was breaking 4.0.x branch, I had to revert it here:
https://github.com/apache/camel/commit/d0e983eff36b28bb6576d3198aa9ad7c8c091251
The error was:
{code:java}
[ERROR] Failed to execute goal
org.apache.maven.plugins:maven-compiler-plugin:3.11.0:compile (default-compile)
on project camel-management: Compilation failure
[ERROR]
/home/oscerd/workspace/apache-camel/camel/core/camel-management/src/main/java/org/apache/camel/management/mbean/ManagedCamelContext.java:[681,22]
no suitable method found for dumpRoutesAsXml(boolean,boolean)
[ERROR] method
org.apache.camel.management.mbean.ManagedCamelContext.dumpRoutesAsXml() is not
applicable
[ERROR] (actual and formal argument lists differ in length)
[ERROR] method
org.apache.camel.management.mbean.ManagedCamelContext.dumpRoutesAsXml(boolean)
is not applicable
[ERROR] (actual and formal argument lists differ in length)
[ERROR]
[ERROR] -> [Help 1]
{code}
> camel-report:route-coverage results in no code coverage
>
>
> Key: CAMEL-20140
> URL: https://issues.apache.org/jira/browse/CAMEL-20140
> Project: Camel
> Issue Type: Bug
> Components: tooling
>Affects Versions: 4.1.0
> Environment: Apache Maven 3.9.4
> (dfbb324ad4a7c8fb0bf182e6d91b0ae20e3d2dd9)
> Maven home: /opt/maven
> Java version: 17.0.8.1, vendor: Private Build, runtime:
> /usr/lib/jvm/java-17-openjdk-amd64
> Default locale: en, platform encoding: UTF-8
> OS name: "linux", version: "5.10.16.3-microsoft-standard-wsl2", arch:
> "amd64", family: "unix"
>Reporter: Magnus Bosson
>Assignee: Claus Ibsen
>Priority: Minor
> Fix For: 4.3.0
>
>
> After upgrading my application from camel 3.20.4 and spring 2.7.11 to camel
> 4.1.0 and spring-boot 3.1.4 {{mvn camel-report:route-coverage}} results in no
> code coverage.
> {{mvn test}} generates files under target/camel-route-coverage for both
> versions
> *Camel 3.20.4*
> {code:java}
> mvn camel-report:route-coverage
> [INFO] Scanning for projects...
> [INFO]
> [INFO] -< xx.xxx.xxx.:-producer
> >--
> [INFO] Building -producer 0.0.1-SNAPSHOT
> [INFO] from pom.xml
> [INFO] [ jar
> ]-
> [INFO]
> [INFO] --- camel-report:3.20.4:route-coverage (default-cli) @
> -producer ---
> [INFO] Discovered 1 routes
> [INFO] Route coverage summary:Class: xx.xxx.xxx.:-producer
> Route: ExampleRoute Line # Count Route
> -- - -
> 33 3 from
> 35 3 setHeader
> 36 3 log
> 37 3 to
> 38 2 choice
> 40 1 setHeader
> 41 1 log
> 43 1 setHeader
> 44 1 log
> 46 2 removeHeaders
> 47 2 to
> 48 2 logCoverage: 12 out of 12 (100.0% / threshold
> 100.0%)
> Status: Success{code}
> {{ }}
> *Camel 4.1*
> {code:java}
> mvn camel-report:route-coverage
> [WARNING] No route coverage data found for route: ExampleRouteId. Make sure
> to enable route coverage in your unit tests and assign unique route ids to
> your routes. Also remember to run unit tests first.{code}
> I found a differance in the output xml-files in target/camel-route-coverage
> between the versions
> The attribute *_customId="true"_* is missing from element *_route_* in
> version 4.1.0 ({{{} camel-report:route-coverage}} yields the expected result.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (CAMEL-20140) camel-report:route-coverage results in no code coverage
[
https://issues.apache.org/jira/browse/CAMEL-20140?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrea Cosentino updated CAMEL-20140:
-
Fix Version/s: (was: 4.0.6)
> camel-report:route-coverage results in no code coverage
>
>
> Key: CAMEL-20140
> URL: https://issues.apache.org/jira/browse/CAMEL-20140
> Project: Camel
> Issue Type: Bug
> Components: tooling
>Affects Versions: 4.1.0
> Environment: Apache Maven 3.9.4
> (dfbb324ad4a7c8fb0bf182e6d91b0ae20e3d2dd9)
> Maven home: /opt/maven
> Java version: 17.0.8.1, vendor: Private Build, runtime:
> /usr/lib/jvm/java-17-openjdk-amd64
> Default locale: en, platform encoding: UTF-8
> OS name: "linux", version: "5.10.16.3-microsoft-standard-wsl2", arch:
> "amd64", family: "unix"
>Reporter: Magnus Bosson
>Assignee: Claus Ibsen
>Priority: Minor
> Fix For: 4.3.0
>
>
> After upgrading my application from camel 3.20.4 and spring 2.7.11 to camel
> 4.1.0 and spring-boot 3.1.4 {{mvn camel-report:route-coverage}} results in no
> code coverage.
> {{mvn test}} generates files under target/camel-route-coverage for both
> versions
> *Camel 3.20.4*
> {code:java}
> mvn camel-report:route-coverage
> [INFO] Scanning for projects...
> [INFO]
> [INFO] -< xx.xxx.xxx.:-producer
> >--
> [INFO] Building -producer 0.0.1-SNAPSHOT
> [INFO] from pom.xml
> [INFO] [ jar
> ]-
> [INFO]
> [INFO] --- camel-report:3.20.4:route-coverage (default-cli) @
> -producer ---
> [INFO] Discovered 1 routes
> [INFO] Route coverage summary:Class: xx.xxx.xxx.:-producer
> Route: ExampleRoute Line # Count Route
> -- - -
> 33 3 from
> 35 3 setHeader
> 36 3 log
> 37 3 to
> 38 2 choice
> 40 1 setHeader
> 41 1 log
> 43 1 setHeader
> 44 1 log
> 46 2 removeHeaders
> 47 2 to
> 48 2 logCoverage: 12 out of 12 (100.0% / threshold
> 100.0%)
> Status: Success{code}
> {{ }}
> *Camel 4.1*
> {code:java}
> mvn camel-report:route-coverage
> [WARNING] No route coverage data found for route: ExampleRouteId. Make sure
> to enable route coverage in your unit tests and assign unique route ids to
> your routes. Also remember to run unit tests first.{code}
> I found a differance in the output xml-files in target/camel-route-coverage
> between the versions
> The attribute *_customId="true"_* is missing from element *_route_* in
> version 4.1.0 ({{{} camel-report:route-coverage}} yields the expected result.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Assigned] (CAMEL-20904) camel-jbang - Run and deploy to Kubernetes
[ https://issues.apache.org/jira/browse/CAMEL-20904?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Cosentino reassigned CAMEL-20904: Assignee: Christoph Deppisch (was: Andrea Cosentino) > camel-jbang - Run and deploy to Kubernetes > -- > > Key: CAMEL-20904 > URL: https://issues.apache.org/jira/browse/CAMEL-20904 > Project: Camel > Issue Type: New Feature > Components: camel-jbang >Reporter: Claus Ibsen >Assignee: Christoph Deppisch >Priority: Major > Fix For: 4.8.0 > > > Lets see if we can make a command to camel-jbang that can build and deploy a > standard Camel Spring Boot / Camel Quarkus (and potentially camel-main) to > kubernetes. > This would mean to export first, and then build and deploy via SB / Quarkus > standard using how you would normally do this via their maven plugins. > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (CAMEL-20904) camel-jbang - Run and deploy to Kubernetes
[ https://issues.apache.org/jira/browse/CAMEL-20904?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17868059#comment-17868059 ] Andrea Cosentino commented on CAMEL-20904: -- [~christophd] I set you as assignee, since you've done most of the work with [~tdiesler] > camel-jbang - Run and deploy to Kubernetes > -- > > Key: CAMEL-20904 > URL: https://issues.apache.org/jira/browse/CAMEL-20904 > Project: Camel > Issue Type: New Feature > Components: camel-jbang >Reporter: Claus Ibsen >Assignee: Christoph Deppisch >Priority: Major > Fix For: 4.8.0 > > > Lets see if we can make a command to camel-jbang that can build and deploy a > standard Camel Spring Boot / Camel Quarkus (and potentially camel-main) to > kubernetes. > This would mean to export first, and then build and deploy via SB / Quarkus > standard using how you would normally do this via their maven plugins. > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (CAMEL-21006) Allow kubernetes export without image registry
[ https://issues.apache.org/jira/browse/CAMEL-21006?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Cosentino resolved CAMEL-21006. -- Resolution: Fixed > Allow kubernetes export without image registry > -- > > Key: CAMEL-21006 > URL: https://issues.apache.org/jira/browse/CAMEL-21006 > Project: Camel > Issue Type: Improvement > Components: camel-jbang >Reporter: Thomas Diesler >Assignee: Thomas Diesler >Priority: Major > Fix For: 4.8.0 > > > Kubernetes export has an `--image-registry` parameter which defaults to > `quay.io`. It is currently not possible to export a k8s project that uses an > image name without registry prefix. > I suggest to remove the arbitrary default and instead require this to be set > explicitly when needed. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (CAMEL-20959) Camel-upgrade-recipes: next steps (to enable releasing)
[ https://issues.apache.org/jira/browse/CAMEL-20959?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17867977#comment-17867977 ] Andrea Cosentino commented on CAMEL-20959: -- I can have a look > Camel-upgrade-recipes: next steps (to enable releasing) > --- > > Key: CAMEL-20959 > URL: https://issues.apache.org/jira/browse/CAMEL-20959 > Project: Camel > Issue Type: Task > Components: upgrade-recipes >Reporter: Jiri Ondrusek >Assignee: Jiri Ondrusek >Priority: Major > Fix For: 4.x > > > TBH I'm not sure what has to be done next. > [Here|https://github.com/apache/camel-upgrade-recipes/pull/1] is the initial > commit for the camel-upgrade-recipes repo. > I think that we should release this library when this commit is merged. > Why? > Once released, I can update draft > [PR|https://github.com/quarkusio/quarkus-updates/pull/177] for > quarkus-updates project and leverage the camel-upgrade-recipes dependency. > With some guiding from someone I can try to achieve some of the task. > (It would be nice to have component in jira, which would represent > upgrade-recipes. > The affects version/fix version does not make sense in the camel project, as > the versioning might be different) -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (CAMEL-20995) camel-azure-storage-blob uploadBlockBlob retry operation fails due to mark and reset issue / Flux
[ https://issues.apache.org/jira/browse/CAMEL-20995?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Cosentino updated CAMEL-20995: - Fix Version/s: 4.0.6 4.4.4 4.8.0 > camel-azure-storage-blob uploadBlockBlob retry operation fails due to mark > and reset issue / Flux > - > > Key: CAMEL-20995 > URL: https://issues.apache.org/jira/browse/CAMEL-20995 > Project: Camel > Issue Type: Bug > Components: camel-azure >Affects Versions: 4.0.0, 4.4.0, 4.7.0 >Reporter: Hareesh Billa >Assignee: Andrea Cosentino >Priority: Minor > Fix For: 4.0.6, 4.4.4, 4.8.0 > > Attachments: Code snip.png, Log trace > > > camel-azure-storage-blob uploadBlockBlob retry operation fails due to mark > and reset issue / Flux > Due to some of the issues Azure blob storage retrying for upload again, but > it is failed to upload due to the input stream length is 0 which is not > expected. > As per the azure core/common bode Flux code suggestion it is suggested to > make markAndreset request parameter to *true,* But the out camel component > always send the parameter value as false. > *Solution:* Instead of sending the default value to false, we can use > inputStream.markSupported() method. > Here I am adding traces and screenshots, for easy understanding. > Thanks. > > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (CAMEL-20995) camel-azure-storage-blob uploadBlockBlob retry operation fails due to mark and reset issue / Flux
[ https://issues.apache.org/jira/browse/CAMEL-20995?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Cosentino updated CAMEL-20995: - Priority: Minor (was: Critical) > camel-azure-storage-blob uploadBlockBlob retry operation fails due to mark > and reset issue / Flux > - > > Key: CAMEL-20995 > URL: https://issues.apache.org/jira/browse/CAMEL-20995 > Project: Camel > Issue Type: Bug > Components: camel-azure >Affects Versions: 4.0.0, 4.4.0, 4.7.0 >Reporter: Hareesh Billa >Priority: Minor > Attachments: Code snip.png, Log trace > > > camel-azure-storage-blob uploadBlockBlob retry operation fails due to mark > and reset issue / Flux > Due to some of the issues Azure blob storage retrying for upload again, but > it is failed to upload due to the input stream length is 0 which is not > expected. > As per the azure core/common bode Flux code suggestion it is suggested to > make markAndreset request parameter to *true,* But the out camel component > always send the parameter value as false. > *Solution:* Instead of sending the default value to false, we can use > inputStream.markSupported() method. > Here I am adding traces and screenshots, for easy understanding. > Thanks. > > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (CAMEL-20995) camel-azure-storage-blob uploadBlockBlob retry operation fails due to mark and reset issue / Flux
[ https://issues.apache.org/jira/browse/CAMEL-20995?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Cosentino reassigned CAMEL-20995: Assignee: Andrea Cosentino > camel-azure-storage-blob uploadBlockBlob retry operation fails due to mark > and reset issue / Flux > - > > Key: CAMEL-20995 > URL: https://issues.apache.org/jira/browse/CAMEL-20995 > Project: Camel > Issue Type: Bug > Components: camel-azure >Affects Versions: 4.0.0, 4.4.0, 4.7.0 >Reporter: Hareesh Billa >Assignee: Andrea Cosentino >Priority: Minor > Attachments: Code snip.png, Log trace > > > camel-azure-storage-blob uploadBlockBlob retry operation fails due to mark > and reset issue / Flux > Due to some of the issues Azure blob storage retrying for upload again, but > it is failed to upload due to the input stream length is 0 which is not > expected. > As per the azure core/common bode Flux code suggestion it is suggested to > make markAndreset request parameter to *true,* But the out camel component > always send the parameter value as false. > *Solution:* Instead of sending the default value to false, we can use > inputStream.markSupported() method. > Here I am adding traces and screenshots, for easy understanding. > Thanks. > > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (CAMEL-21002) Camel-Spring-Boot: Upgrade to Spring Boot 3.3.2
[ https://issues.apache.org/jira/browse/CAMEL-21002?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Cosentino updated CAMEL-21002: - Fix Version/s: 4.8.0 > Camel-Spring-Boot: Upgrade to Spring Boot 3.3.2 > --- > > Key: CAMEL-21002 > URL: https://issues.apache.org/jira/browse/CAMEL-21002 > Project: Camel > Issue Type: Dependency upgrade >Reporter: Andrea Cosentino >Assignee: Andrea Cosentino >Priority: Major > Fix For: 4.8.0 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (CAMEL-21002) Camel-Spring-Boot: Upgrade to Spring Boot 3.3.2
[ https://issues.apache.org/jira/browse/CAMEL-21002?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Cosentino resolved CAMEL-21002. -- Resolution: Fixed > Camel-Spring-Boot: Upgrade to Spring Boot 3.3.2 > --- > > Key: CAMEL-21002 > URL: https://issues.apache.org/jira/browse/CAMEL-21002 > Project: Camel > Issue Type: Dependency upgrade >Reporter: Andrea Cosentino >Assignee: Andrea Cosentino >Priority: Major > Fix For: 4.8.0 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (CAMEL-21002) Camel-Spring-Boot: Upgrade to Spring Boot 3.3.2
[ https://issues.apache.org/jira/browse/CAMEL-21002?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Cosentino reassigned CAMEL-21002: Assignee: Andrea Cosentino > Camel-Spring-Boot: Upgrade to Spring Boot 3.3.2 > --- > > Key: CAMEL-21002 > URL: https://issues.apache.org/jira/browse/CAMEL-21002 > Project: Camel > Issue Type: Dependency upgrade >Reporter: Andrea Cosentino >Assignee: Andrea Cosentino >Priority: Major > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (CAMEL-21002) Camel-Spring-Boot: Upgrade to Spring Boot 3.3.2
Andrea Cosentino created CAMEL-21002: Summary: Camel-Spring-Boot: Upgrade to Spring Boot 3.3.2 Key: CAMEL-21002 URL: https://issues.apache.org/jira/browse/CAMEL-21002 Project: Camel Issue Type: Dependency upgrade Reporter: Andrea Cosentino -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (CAMEL-20918) Salesforce component does not resubscribe after exception
[
https://issues.apache.org/jira/browse/CAMEL-20918?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrea Cosentino resolved CAMEL-20918.
--
Resolution: Fixed
> Salesforce component does not resubscribe after exception
> -
>
> Key: CAMEL-20918
> URL: https://issues.apache.org/jira/browse/CAMEL-20918
> Project: Camel
> Issue Type: Bug
> Components: camel-salesforce
>Affects Versions: 3.22.2, 4.4.2, 4.6.0
>Reporter: Bartosz Popiela
>Assignee: Andrea Cosentino
>Priority: Major
> Fix For: 4.8.0
>
>
> In February this year I raised a ticket CAMEL-20388 after observing that the
> _SubscriptionHelper#handshake_ method was not being used, as the first thread
> to invoke it would hang in a deadlock state. After it was fixed there is no
> deadlock, but two other issues were introduced:
> - if any exception occurs during the connect phase and the response message
> does not contain a rehandshake advice, it will permanently disconnect the
> client,
> - because _SubscriptionHelper#connectListener_ delegates to a different
> thread poll and there may be a case whereBayeuxClient sends a request to
> rehandshake before _SubscriptionHelper#connectListener_ disconnects the
> client hance the disconnect will fail and consequently terminate the executor
> in _BayeuxClient_. This results in the following exception being thrown:
> {code:java}
> 16:56:01.757 [Camel (camel-1) thread #287 - SalesforceHttpClient] DEBUG
> o.cometd.client.BayeuxClient.598138b - Transport failure:
> FailureInfo@1d90b9a7[transport=null,cause=java.util.concurrent.RejectedExecutionException:
> Task
> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask@2ed1c350[Not
> completed, task =
> java.util.concurrent.Executors$RunnableAdapter@2429a820[Wrapped task =
> org.cometd.client.http.jetty.JettyHttpClientTransport$$Lambda$1947/0x7f1581f26718@2aee42d5]]
> rejected from org.cometd.client.BayeuxClient$Scheduler@6bd348ee[Terminated,
> pool size = 0, active threads = 0, queued tasks = 0, completed tasks =
> 27],action=handshake] for
> {failure={exception=java.util.concurrent.RejectedExecutionException: Task
> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask@2ed1c350[Not
> completed, task =
> java.util.concurrent.Executors$RunnableAdapter@2429a820[Wrapped task =
> org.cometd.client.http.jetty.JettyHttpClientTransport$$Lambda$1947/0x7f1581f26718@2aee42d5]]
> rejected from org.cometd.client.BayeuxClient$Scheduler@6bd348ee[Terminated,
> pool size = 0, active threads = 0, queued tasks = 0, completed tasks = 27],
> message={ext={replay=true}, supportedConnectionTypes=[long-polling],
> channel=/meta/handshake, id=304, version=1.0}, connectionType=long-polling},
> channel=/meta/handshake, id=304, successful=false}
> {code}
> In addition, because SubscriptionHelper#connectListener clears
> SubscriptionHelper#connectListener and subscriptionListener doesn't put the
> listeners back to the map if the subscription message fails, the Salesforce
> component will not be able to recover (SubscriptionHelper@listenerMap will be
> empty).
> Also, SalesforceComponent#REQUEST_TIMEOUT should be greater than 110 sec as
> this is the default Salesforce timeout for long-polling as per [Clients and
> Timeouts|https://developer.salesforce.com/docs/atlas.en-us.api_streaming.meta/api_streaming/using_streaming_api_timeouts.htm]
> and
> [CometD#1142|https://github.com/cometd/cometd/issues/1142#issuecomment-1048256297].
> Otherwise, java.util.concurrent.TimeoutException will be thrown if there are
> is no event before the timeout expires.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Assigned] (CAMEL-20918) Salesforce component does not resubscribe after exception
[
https://issues.apache.org/jira/browse/CAMEL-20918?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrea Cosentino reassigned CAMEL-20918:
Assignee: Andrea Cosentino
> Salesforce component does not resubscribe after exception
> -
>
> Key: CAMEL-20918
> URL: https://issues.apache.org/jira/browse/CAMEL-20918
> Project: Camel
> Issue Type: Bug
> Components: camel-salesforce
>Affects Versions: 3.22.2, 4.4.2, 4.6.0
>Reporter: Bartosz Popiela
>Assignee: Andrea Cosentino
>Priority: Major
> Fix For: 4.8.0
>
>
> In February this year I raised a ticket CAMEL-20388 after observing that the
> _SubscriptionHelper#handshake_ method was not being used, as the first thread
> to invoke it would hang in a deadlock state. After it was fixed there is no
> deadlock, but two other issues were introduced:
> - if any exception occurs during the connect phase and the response message
> does not contain a rehandshake advice, it will permanently disconnect the
> client,
> - because _SubscriptionHelper#connectListener_ delegates to a different
> thread poll and there may be a case whereBayeuxClient sends a request to
> rehandshake before _SubscriptionHelper#connectListener_ disconnects the
> client hance the disconnect will fail and consequently terminate the executor
> in _BayeuxClient_. This results in the following exception being thrown:
> {code:java}
> 16:56:01.757 [Camel (camel-1) thread #287 - SalesforceHttpClient] DEBUG
> o.cometd.client.BayeuxClient.598138b - Transport failure:
> FailureInfo@1d90b9a7[transport=null,cause=java.util.concurrent.RejectedExecutionException:
> Task
> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask@2ed1c350[Not
> completed, task =
> java.util.concurrent.Executors$RunnableAdapter@2429a820[Wrapped task =
> org.cometd.client.http.jetty.JettyHttpClientTransport$$Lambda$1947/0x7f1581f26718@2aee42d5]]
> rejected from org.cometd.client.BayeuxClient$Scheduler@6bd348ee[Terminated,
> pool size = 0, active threads = 0, queued tasks = 0, completed tasks =
> 27],action=handshake] for
> {failure={exception=java.util.concurrent.RejectedExecutionException: Task
> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask@2ed1c350[Not
> completed, task =
> java.util.concurrent.Executors$RunnableAdapter@2429a820[Wrapped task =
> org.cometd.client.http.jetty.JettyHttpClientTransport$$Lambda$1947/0x7f1581f26718@2aee42d5]]
> rejected from org.cometd.client.BayeuxClient$Scheduler@6bd348ee[Terminated,
> pool size = 0, active threads = 0, queued tasks = 0, completed tasks = 27],
> message={ext={replay=true}, supportedConnectionTypes=[long-polling],
> channel=/meta/handshake, id=304, version=1.0}, connectionType=long-polling},
> channel=/meta/handshake, id=304, successful=false}
> {code}
> In addition, because SubscriptionHelper#connectListener clears
> SubscriptionHelper#connectListener and subscriptionListener doesn't put the
> listeners back to the map if the subscription message fails, the Salesforce
> component will not be able to recover (SubscriptionHelper@listenerMap will be
> empty).
> Also, SalesforceComponent#REQUEST_TIMEOUT should be greater than 110 sec as
> this is the default Salesforce timeout for long-polling as per [Clients and
> Timeouts|https://developer.salesforce.com/docs/atlas.en-us.api_streaming.meta/api_streaming/using_streaming_api_timeouts.htm]
> and
> [CometD#1142|https://github.com/cometd/cometd/issues/1142#issuecomment-1048256297].
> Otherwise, java.util.concurrent.TimeoutException will be thrown if there are
> is no event before the timeout expires.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Resolved] (CAMEL-20996) camel-solr: revive component and upgrade to the latest version
[ https://issues.apache.org/jira/browse/CAMEL-20996?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Cosentino resolved CAMEL-20996. -- Resolution: Fixed > camel-solr: revive component and upgrade to the latest version > -- > > Key: CAMEL-20996 > URL: https://issues.apache.org/jira/browse/CAMEL-20996 > Project: Camel > Issue Type: New Feature > Components: camel-solr >Reporter: Otavio Rodolfo Piske >Assignee: Otavio Rodolfo Piske >Priority: Major > Fix For: 4.8.0 > > > As part of CAMEL-19290, we have removed camel-solr. But recent updates on the > libraries used to implement it now allow us to have this component in a way > that is compatible with Camel 4. As such, this is a ticket for reviving the > component and aligning it with Camel 4. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (CAMEL-20980) Allow to set custom Jackson object mapper on the JSON Schema Validator
[ https://issues.apache.org/jira/browse/CAMEL-20980?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Cosentino updated CAMEL-20980: - Fix Version/s: 4.8.0 > Allow to set custom Jackson object mapper on the JSON Schema Validator > -- > > Key: CAMEL-20980 > URL: https://issues.apache.org/jira/browse/CAMEL-20980 > Project: Camel > Issue Type: New Feature >Affects Versions: 4.7.0 >Reporter: Alvin Kwekel >Priority: Major > Fix For: 4.8.0 > > > To be able to validate a very large (over 20.000.000 character) JSON string > the Jackson object mapper needs to be configured with a custom `JsonFactory` > with a `StreamReadConstraints` with a higher `maxStringLength`. > The string length can't be configured via the Jackson deserialization > features that are settable via the query parameters of the validator. There > is a new ObjectMapper constructed in the doInit method of the > `JsonValidatorEndpoint` so there is not way to override that. > This feature is discussed in chat: > https://camel.zulipchat.com/#narrow/stream/257301-camel-spring-boot/topic/Custom.20Jackson.20object.20mapper.20on.20the.20JSON.20Schema.20Validator -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (CAMEL-20980) Allow to set custom Jackson object mapper on the JSON Schema Validator
[ https://issues.apache.org/jira/browse/CAMEL-20980?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Cosentino resolved CAMEL-20980. -- Resolution: Fixed > Allow to set custom Jackson object mapper on the JSON Schema Validator > -- > > Key: CAMEL-20980 > URL: https://issues.apache.org/jira/browse/CAMEL-20980 > Project: Camel > Issue Type: New Feature >Affects Versions: 4.7.0 >Reporter: Alvin Kwekel >Priority: Major > Fix For: 4.8.0 > > > To be able to validate a very large (over 20.000.000 character) JSON string > the Jackson object mapper needs to be configured with a custom `JsonFactory` > with a `StreamReadConstraints` with a higher `maxStringLength`. > The string length can't be configured via the Jackson deserialization > features that are settable via the query parameters of the validator. There > is a new ObjectMapper constructed in the doInit method of the > `JsonValidatorEndpoint` so there is not way to override that. > This feature is discussed in chat: > https://camel.zulipchat.com/#narrow/stream/257301-camel-spring-boot/topic/Custom.20Jackson.20object.20mapper.20on.20the.20JSON.20Schema.20Validator -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (CAMEL-20904) camel-jbang - Run and deploy to Kubernetes
[ https://issues.apache.org/jira/browse/CAMEL-20904?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17866281#comment-17866281 ] Andrea Cosentino commented on CAMEL-20904: -- I think it makes sense to collect all the related tasks here and use the issue as epic. > camel-jbang - Run and deploy to Kubernetes > -- > > Key: CAMEL-20904 > URL: https://issues.apache.org/jira/browse/CAMEL-20904 > Project: Camel > Issue Type: New Feature > Components: camel-jbang >Reporter: Claus Ibsen >Assignee: Andrea Cosentino >Priority: Major > Fix For: 4.8.0 > > > Lets see if we can make a command to camel-jbang that can build and deploy a > standard Camel Spring Boot / Camel Quarkus (and potentially camel-main) to > kubernetes. > This would mean to export first, and then build and deploy via SB / Quarkus > standard using how you would normally do this via their maven plugins. > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (CAMEL-20904) camel-jbang - Run and deploy to Kubernetes
[ https://issues.apache.org/jira/browse/CAMEL-20904?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Cosentino updated CAMEL-20904: - Fix Version/s: 4.8.0 (was: 4.x) > camel-jbang - Run and deploy to Kubernetes > -- > > Key: CAMEL-20904 > URL: https://issues.apache.org/jira/browse/CAMEL-20904 > Project: Camel > Issue Type: New Feature > Components: camel-jbang >Reporter: Claus Ibsen >Assignee: Andrea Cosentino >Priority: Major > Fix For: 4.8.0 > > > Lets see if we can make a command to camel-jbang that can build and deploy a > standard Camel Spring Boot / Camel Quarkus (and potentially camel-main) to > kubernetes. > This would mean to export first, and then build and deploy via SB / Quarkus > standard using how you would normally do this via their maven plugins. > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (CAMEL-20918) Salesforce component does not resubscribe after exception
[
https://issues.apache.org/jira/browse/CAMEL-20918?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17866228#comment-17866228
]
Andrea Cosentino commented on CAMEL-20918:
--
4.7.x is not an LTS release, it's a development release. The next LTS will be
4.8.0
> Salesforce component does not resubscribe after exception
> -
>
> Key: CAMEL-20918
> URL: https://issues.apache.org/jira/browse/CAMEL-20918
> Project: Camel
> Issue Type: Bug
> Components: camel-salesforce
>Affects Versions: 3.22.2, 4.4.2, 4.6.0
>Reporter: Bartosz Popiela
>Priority: Major
> Fix For: 4.8.0
>
>
> In February this year I raised a ticket CAMEL-20388 after observing that the
> _SubscriptionHelper#handshake_ method was not being used, as the first thread
> to invoke it would hang in a deadlock state. After it was fixed there is no
> deadlock, but two other issues were introduced:
> - if any exception occurs during the connect phase and the response message
> does not contain a rehandshake advice, it will permanently disconnect the
> client,
> - because _SubscriptionHelper#connectListener_ delegates to a different
> thread poll and there may be a case whereBayeuxClient sends a request to
> rehandshake before _SubscriptionHelper#connectListener_ disconnects the
> client hance the disconnect will fail and consequently terminate the executor
> in _BayeuxClient_. This results in the following exception being thrown:
> {code:java}
> 16:56:01.757 [Camel (camel-1) thread #287 - SalesforceHttpClient] DEBUG
> o.cometd.client.BayeuxClient.598138b - Transport failure:
> FailureInfo@1d90b9a7[transport=null,cause=java.util.concurrent.RejectedExecutionException:
> Task
> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask@2ed1c350[Not
> completed, task =
> java.util.concurrent.Executors$RunnableAdapter@2429a820[Wrapped task =
> org.cometd.client.http.jetty.JettyHttpClientTransport$$Lambda$1947/0x7f1581f26718@2aee42d5]]
> rejected from org.cometd.client.BayeuxClient$Scheduler@6bd348ee[Terminated,
> pool size = 0, active threads = 0, queued tasks = 0, completed tasks =
> 27],action=handshake] for
> {failure={exception=java.util.concurrent.RejectedExecutionException: Task
> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask@2ed1c350[Not
> completed, task =
> java.util.concurrent.Executors$RunnableAdapter@2429a820[Wrapped task =
> org.cometd.client.http.jetty.JettyHttpClientTransport$$Lambda$1947/0x7f1581f26718@2aee42d5]]
> rejected from org.cometd.client.BayeuxClient$Scheduler@6bd348ee[Terminated,
> pool size = 0, active threads = 0, queued tasks = 0, completed tasks = 27],
> message={ext={replay=true}, supportedConnectionTypes=[long-polling],
> channel=/meta/handshake, id=304, version=1.0}, connectionType=long-polling},
> channel=/meta/handshake, id=304, successful=false}
> {code}
> In addition, because SubscriptionHelper#connectListener clears
> SubscriptionHelper#connectListener and subscriptionListener doesn't put the
> listeners back to the map if the subscription message fails, the Salesforce
> component will not be able to recover (SubscriptionHelper@listenerMap will be
> empty).
> Also, SalesforceComponent#REQUEST_TIMEOUT should be greater than 110 sec as
> this is the default Salesforce timeout for long-polling as per [Clients and
> Timeouts|https://developer.salesforce.com/docs/atlas.en-us.api_streaming.meta/api_streaming/using_streaming_api_timeouts.htm]
> and
> [CometD#1142|https://github.com/cometd/cometd/issues/1142#issuecomment-1048256297].
> Otherwise, java.util.concurrent.TimeoutException will be thrown if there are
> is no event before the timeout expires.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Resolved] (CAMEL-20971) camel - aws - S3 getObject consumer does not accept dynamic keyname
[ https://issues.apache.org/jira/browse/CAMEL-20971?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Cosentino resolved CAMEL-20971. -- Resolution: Fixed > camel - aws - S3 getObject consumer does not accept dynamic keyname > --- > > Key: CAMEL-20971 > URL: https://issues.apache.org/jira/browse/CAMEL-20971 > Project: Camel > Issue Type: New Feature > Components: camel-aws >Affects Versions: 4.6.0 > Environment: Camel 4.6.0 > Localstack 3.0.2 >Reporter: Mark Wimpory >Assignee: Claus Ibsen >Priority: Minor > Fix For: 4.8.0 > > Attachments: WranglerSQSS3RouteBuilder.java > > > I have spent some time trying to build a route that will read a message from > SQS and then based on the content of the message read a file from S3. This > is a fairly typical triggering mechanism for S3 and we use it a lot. So when > a file arrives in S3 we trigger an SQS message that will process said file. > With the keyname as a constant this works fine and I can retrieve a stream > from S3. However whenever I switch the keyname to a variable value I get a > 'key not found' error. > I will attach a route class as a reproducer. Its worth noting that I have > tried several approaches which will be commented out in the reproducer. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (CAMEL-20726) Camel-Pinecone: Improve Documentation
[ https://issues.apache.org/jira/browse/CAMEL-20726?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Cosentino updated CAMEL-20726: - Fix Version/s: 4.8.0 (was: 4.7.0) > Camel-Pinecone: Improve Documentation > - > > Key: CAMEL-20726 > URL: https://issues.apache.org/jira/browse/CAMEL-20726 > Project: Camel > Issue Type: New Feature >Reporter: Andrea Cosentino >Assignee: Andrea Cosentino >Priority: Major > Fix For: 4.8.0 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (CAMEL-20741) Support Chroma DB Vector database
[ https://issues.apache.org/jira/browse/CAMEL-20741?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Cosentino updated CAMEL-20741: - Fix Version/s: 4.x (was: 4.7.0) > Support Chroma DB Vector database > - > > Key: CAMEL-20741 > URL: https://issues.apache.org/jira/browse/CAMEL-20741 > Project: Camel > Issue Type: New Feature >Reporter: Andrea Cosentino >Assignee: Andrea Cosentino >Priority: Major > Fix For: 4.x > > > https://www.trychroma.com/ > https://github.com/amikos-tech/chromadb-java-client -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (CAMEL-20468) Camel-AWS-Bedrock: Support available models
[ https://issues.apache.org/jira/browse/CAMEL-20468?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Cosentino updated CAMEL-20468: - Fix Version/s: 4.x (was: 4.7.0) > Camel-AWS-Bedrock: Support available models > --- > > Key: CAMEL-20468 > URL: https://issues.apache.org/jira/browse/CAMEL-20468 > Project: Camel > Issue Type: New Feature >Reporter: Andrea Cosentino >Assignee: Andrea Cosentino >Priority: Major > Fix For: 4.x > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (CAMEL-20272) Camel-Azure components: Support SAS Authentication where is still not supported
[ https://issues.apache.org/jira/browse/CAMEL-20272?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Cosentino updated CAMEL-20272: - Fix Version/s: 4.x (was: 4.7.0) > Camel-Azure components: Support SAS Authentication where is still not > supported > --- > > Key: CAMEL-20272 > URL: https://issues.apache.org/jira/browse/CAMEL-20272 > Project: Camel > Issue Type: Improvement > Components: camel-azure >Reporter: Andrea Cosentino >Assignee: Andrea Cosentino >Priority: Major > Fix For: 4.x > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (CAMEL-20765) Camel-AWS-Bedrock: Support Amazon Titan Text Embeddings V2
[ https://issues.apache.org/jira/browse/CAMEL-20765?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Cosentino updated CAMEL-20765: - Fix Version/s: 4.x (was: 4.7.0) > Camel-AWS-Bedrock: Support Amazon Titan Text Embeddings V2 > -- > > Key: CAMEL-20765 > URL: https://issues.apache.org/jira/browse/CAMEL-20765 > Project: Camel > Issue Type: Sub-task > Components: camel-aws >Reporter: Andrea Cosentino >Assignee: Andrea Cosentino >Priority: Major > Fix For: 4.x > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (CAMEL-20827) Add endpoint service location to aws, azure and google components
[ https://issues.apache.org/jira/browse/CAMEL-20827?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Cosentino updated CAMEL-20827: - Summary: Add endpoint service location to aws, azure and google components (was: Add endpoint service location to aws, azure and google componentd) > Add endpoint service location to aws, azure and google components > - > > Key: CAMEL-20827 > URL: https://issues.apache.org/jira/browse/CAMEL-20827 > Project: Camel > Issue Type: New Feature >Reporter: Claus Ibsen >Assignee: Andrea Cosentino >Priority: Major > Fix For: 4.7.0 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (CAMEL-20827) Add endpoint service location to aws, azure and google componentd
[ https://issues.apache.org/jira/browse/CAMEL-20827?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Cosentino resolved CAMEL-20827. -- Resolution: Fixed > Add endpoint service location to aws, azure and google componentd > - > > Key: CAMEL-20827 > URL: https://issues.apache.org/jira/browse/CAMEL-20827 > Project: Camel > Issue Type: New Feature >Reporter: Claus Ibsen >Assignee: Andrea Cosentino >Priority: Major > Fix For: 4.7.0 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (CAMEL-20909) Camel-Aws-Kinesis: Support KCL Consumers
[ https://issues.apache.org/jira/browse/CAMEL-20909?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Cosentino resolved CAMEL-20909. -- Resolution: Fixed > Camel-Aws-Kinesis: Support KCL Consumers > > > Key: CAMEL-20909 > URL: https://issues.apache.org/jira/browse/CAMEL-20909 > Project: Camel > Issue Type: New Feature >Reporter: Andrea Cosentino >Assignee: Andrea Cosentino >Priority: Major > Fix For: 4.7.0 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (CAMEL-20916) Camel-AWS-Kinesis: KCL Consumers, add documentation
[ https://issues.apache.org/jira/browse/CAMEL-20916?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Cosentino resolved CAMEL-20916. -- Resolution: Fixed > Camel-AWS-Kinesis: KCL Consumers, add documentation > --- > > Key: CAMEL-20916 > URL: https://issues.apache.org/jira/browse/CAMEL-20916 > Project: Camel > Issue Type: Sub-task >Reporter: Andrea Cosentino >Assignee: Andrea Cosentino >Priority: Major > Fix For: 4.7.0 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Deleted] (CAMEL-20925) Camel-AWS-Kinesis: KCL Consumers, add parameters for setting the start position of stream in the RetrievalConfig
[ https://issues.apache.org/jira/browse/CAMEL-20925?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Cosentino deleted CAMEL-20925: - > Camel-AWS-Kinesis: KCL Consumers, add parameters for setting the start > position of stream in the RetrievalConfig > > > Key: CAMEL-20925 > URL: https://issues.apache.org/jira/browse/CAMEL-20925 > Project: Camel > Issue Type: Sub-task >Reporter: Andrea Cosentino >Assignee: Andrea Cosentino >Priority: Major > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (CAMEL-20925) Camel-AWS-Kinesis: KCL Consumers, add parameters for setting the start position of stream in the RetrievalConfig
Andrea Cosentino created CAMEL-20925: Summary: Camel-AWS-Kinesis: KCL Consumers, add parameters for setting the start position of stream in the RetrievalConfig Key: CAMEL-20925 URL: https://issues.apache.org/jira/browse/CAMEL-20925 Project: Camel Issue Type: Sub-task Reporter: Andrea Cosentino Assignee: Andrea Cosentino Fix For: 4.7.0 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (CAMEL-20914) Camel-AWS-Kinesis: KCL Consumers add an example
[ https://issues.apache.org/jira/browse/CAMEL-20914?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Cosentino updated CAMEL-20914: - Fix Version/s: 4.7.0 (was: 4.x) > Camel-AWS-Kinesis: KCL Consumers add an example > --- > > Key: CAMEL-20914 > URL: https://issues.apache.org/jira/browse/CAMEL-20914 > Project: Camel > Issue Type: Sub-task >Reporter: Andrea Cosentino >Assignee: Andrea Cosentino >Priority: Major > Fix For: 4.7.0 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (CAMEL-20914) Camel-AWS-Kinesis: KCL Consumers add an example
[ https://issues.apache.org/jira/browse/CAMEL-20914?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Cosentino resolved CAMEL-20914. -- Resolution: Fixed > Camel-AWS-Kinesis: KCL Consumers add an example > --- > > Key: CAMEL-20914 > URL: https://issues.apache.org/jira/browse/CAMEL-20914 > Project: Camel > Issue Type: Sub-task >Reporter: Andrea Cosentino >Assignee: Andrea Cosentino >Priority: Major > Fix For: 4.7.0 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (CAMEL-20827) Add endpoint service location to aws, azure and google componentd
[ https://issues.apache.org/jira/browse/CAMEL-20827?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17860212#comment-17860212 ] Andrea Cosentino commented on CAMEL-20827: -- I'll complete GCP this week. > Add endpoint service location to aws, azure and google componentd > - > > Key: CAMEL-20827 > URL: https://issues.apache.org/jira/browse/CAMEL-20827 > Project: Camel > Issue Type: New Feature >Reporter: Claus Ibsen >Assignee: Andrea Cosentino >Priority: Major > Fix For: 4.7.0 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (CAMEL-20913) Camel-AWS-Kinesis: KCL Consumers, add support for profile/default/session credentials for Cloudwatch and DynamoDB clients
[ https://issues.apache.org/jira/browse/CAMEL-20913?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Cosentino resolved CAMEL-20913. -- Resolution: Fixed > Camel-AWS-Kinesis: KCL Consumers, add support for profile/default/session > credentials for Cloudwatch and DynamoDB clients > - > > Key: CAMEL-20913 > URL: https://issues.apache.org/jira/browse/CAMEL-20913 > Project: Camel > Issue Type: Sub-task >Reporter: Andrea Cosentino >Assignee: Andrea Cosentino >Priority: Major > Fix For: 4.7.0 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (CAMEL-20912) Camel-AWS-Kinesis: KCL Consumers add parameters for passing Cloudwatch and DynamoDB Clients
[ https://issues.apache.org/jira/browse/CAMEL-20912?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Cosentino updated CAMEL-20912: - Fix Version/s: 4.7.0 (was: 4.x) > Camel-AWS-Kinesis: KCL Consumers add parameters for passing Cloudwatch and > DynamoDB Clients > --- > > Key: CAMEL-20912 > URL: https://issues.apache.org/jira/browse/CAMEL-20912 > Project: Camel > Issue Type: Sub-task >Reporter: Andrea Cosentino >Assignee: Andrea Cosentino >Priority: Major > Fix For: 4.7.0 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (CAMEL-20912) Camel-AWS-Kinesis: KCL Consumers add parameters for passing Cloudwatch and DynamoDB Clients
[ https://issues.apache.org/jira/browse/CAMEL-20912?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Cosentino resolved CAMEL-20912. -- Resolution: Fixed > Camel-AWS-Kinesis: KCL Consumers add parameters for passing Cloudwatch and > DynamoDB Clients > --- > > Key: CAMEL-20912 > URL: https://issues.apache.org/jira/browse/CAMEL-20912 > Project: Camel > Issue Type: Sub-task >Reporter: Andrea Cosentino >Assignee: Andrea Cosentino >Priority: Major > Fix For: 4.7.0 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (CAMEL-20913) Camel-AWS-Kinesis: KCL Consumers, add support for profile/default/session credentials for Cloudwatch and DynamoDB clients
[ https://issues.apache.org/jira/browse/CAMEL-20913?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Cosentino updated CAMEL-20913: - Fix Version/s: 4.7.0 (was: 4.x) > Camel-AWS-Kinesis: KCL Consumers, add support for profile/default/session > credentials for Cloudwatch and DynamoDB clients > - > > Key: CAMEL-20913 > URL: https://issues.apache.org/jira/browse/CAMEL-20913 > Project: Camel > Issue Type: Sub-task >Reporter: Andrea Cosentino >Assignee: Andrea Cosentino >Priority: Major > Fix For: 4.7.0 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (CAMEL-20914) Camel-AWS-Kinesis: KCL Consumers add an example
[ https://issues.apache.org/jira/browse/CAMEL-20914?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Cosentino updated CAMEL-20914: - Summary: Camel-AWS-Kinesis: KCL Consumers add an example (was: Camel-AWS-Kinesis: KCL Consumers and an example) > Camel-AWS-Kinesis: KCL Consumers add an example > --- > > Key: CAMEL-20914 > URL: https://issues.apache.org/jira/browse/CAMEL-20914 > Project: Camel > Issue Type: Sub-task >Reporter: Andrea Cosentino >Assignee: Andrea Cosentino >Priority: Major > Fix For: 4.x > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (CAMEL-20916) Camel-AWS-Kinesis: KCL Consumers, add documentation
Andrea Cosentino created CAMEL-20916: Summary: Camel-AWS-Kinesis: KCL Consumers, add documentation Key: CAMEL-20916 URL: https://issues.apache.org/jira/browse/CAMEL-20916 Project: Camel Issue Type: Sub-task Reporter: Andrea Cosentino Assignee: Andrea Cosentino Fix For: 4.7.0 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (CAMEL-20914) Camel-AWS-Kinesis: KCL Consumers and an example
Andrea Cosentino created CAMEL-20914: Summary: Camel-AWS-Kinesis: KCL Consumers and an example Key: CAMEL-20914 URL: https://issues.apache.org/jira/browse/CAMEL-20914 Project: Camel Issue Type: Sub-task Reporter: Andrea Cosentino Assignee: Andrea Cosentino Fix For: 4.x -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (CAMEL-20913) Camel-AWS-Kinesis: KCL Consumers, add support for profile/default/session credentials for Cloudwatch and DynamoDB clients
Andrea Cosentino created CAMEL-20913: Summary: Camel-AWS-Kinesis: KCL Consumers, add support for profile/default/session credentials for Cloudwatch and DynamoDB clients Key: CAMEL-20913 URL: https://issues.apache.org/jira/browse/CAMEL-20913 Project: Camel Issue Type: Sub-task Reporter: Andrea Cosentino Assignee: Andrea Cosentino Fix For: 4.x -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (CAMEL-20912) Camel-AWS-Kinesis: KCL Consumers add parameters for passing Cloudwatch and DynamoDB Clients
[ https://issues.apache.org/jira/browse/CAMEL-20912?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Cosentino updated CAMEL-20912: - Fix Version/s: 4.x > Camel-AWS-Kinesis: KCL Consumers add parameters for passing Cloudwatch and > DynamoDB Clients > --- > > Key: CAMEL-20912 > URL: https://issues.apache.org/jira/browse/CAMEL-20912 > Project: Camel > Issue Type: Sub-task >Reporter: Andrea Cosentino >Assignee: Andrea Cosentino >Priority: Major > Fix For: 4.x > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (CAMEL-20912) Camel-AWS-Kinesis: KCL Consumers add parameters for passing Cloudwatch and DynamoDB Clients
[ https://issues.apache.org/jira/browse/CAMEL-20912?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Cosentino reassigned CAMEL-20912: Assignee: Andrea Cosentino > Camel-AWS-Kinesis: KCL Consumers add parameters for passing Cloudwatch and > DynamoDB Clients > --- > > Key: CAMEL-20912 > URL: https://issues.apache.org/jira/browse/CAMEL-20912 > Project: Camel > Issue Type: Sub-task >Reporter: Andrea Cosentino >Assignee: Andrea Cosentino >Priority: Major > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (CAMEL-20912) Camel-AWS-Kinesis: KCL Consumers add parameters for passing Cloudwatch and DynamoDB Clients
Andrea Cosentino created CAMEL-20912: Summary: Camel-AWS-Kinesis: KCL Consumers add parameters for passing Cloudwatch and DynamoDB Clients Key: CAMEL-20912 URL: https://issues.apache.org/jira/browse/CAMEL-20912 Project: Camel Issue Type: Sub-task Reporter: Andrea Cosentino -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (CAMEL-20909) Camel-Aws-Kinesis: Support KCL Consumers
Andrea Cosentino created CAMEL-20909: Summary: Camel-Aws-Kinesis: Support KCL Consumers Key: CAMEL-20909 URL: https://issues.apache.org/jira/browse/CAMEL-20909 Project: Camel Issue Type: New Feature Reporter: Andrea Cosentino Assignee: Andrea Cosentino Fix For: 4.7.0 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (CAMEL-20904) camel-jbang - Run and deploy to Kubernetes
[ https://issues.apache.org/jira/browse/CAMEL-20904?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17856715#comment-17856715 ] Andrea Cosentino commented on CAMEL-20904: -- I'll try to have a look. > camel-jbang - Run and deploy to Kubernetes > -- > > Key: CAMEL-20904 > URL: https://issues.apache.org/jira/browse/CAMEL-20904 > Project: Camel > Issue Type: New Feature > Components: camel-jbang >Reporter: Claus Ibsen >Assignee: Andrea Cosentino >Priority: Major > Fix For: 4.x > > > Lets see if we can make a command to camel-jbang that can build and deploy a > standard Camel Spring Boot / Camel Quarkus (and potentially camel-main) to > kubernetes. > This would mean to export first, and then build and deploy via SB / Quarkus > standard using how you would normally do this via their maven plugins. > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (CAMEL-20904) camel-jbang - Run and deploy to Kubernetes
[ https://issues.apache.org/jira/browse/CAMEL-20904?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Cosentino reassigned CAMEL-20904: Assignee: Andrea Cosentino > camel-jbang - Run and deploy to Kubernetes > -- > > Key: CAMEL-20904 > URL: https://issues.apache.org/jira/browse/CAMEL-20904 > Project: Camel > Issue Type: New Feature > Components: camel-jbang >Reporter: Claus Ibsen >Assignee: Andrea Cosentino >Priority: Major > Fix For: 4.x > > > Lets see if we can make a command to camel-jbang that can build and deploy a > standard Camel Spring Boot / Camel Quarkus (and potentially camel-main) to > kubernetes. > This would mean to export first, and then build and deploy via SB / Quarkus > standard using how you would normally do this via their maven plugins. > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (CAMEL-20827) Add endpoint service location to aws, azure and google componentd
[ https://issues.apache.org/jira/browse/CAMEL-20827?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17856712#comment-17856712 ] Andrea Cosentino commented on CAMEL-20827: -- Azure completed > Add endpoint service location to aws, azure and google componentd > - > > Key: CAMEL-20827 > URL: https://issues.apache.org/jira/browse/CAMEL-20827 > Project: Camel > Issue Type: New Feature >Reporter: Claus Ibsen >Assignee: Andrea Cosentino >Priority: Major > Fix For: 4.7.0 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Comment Edited] (CAMEL-20904) camel-jbang - Run and deploy to Kubernetes
[ https://issues.apache.org/jira/browse/CAMEL-20904?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17856706#comment-17856706 ] Andrea Cosentino edited comment on CAMEL-20904 at 6/21/24 9:20 AM: --- We need to add also a parameter in the export command to manage plugins section of the POM, because both Quarkus and Spring Boot will need to add some bits to make the deploy works. Otherwise we'll have to do this behind the curtain. was (Author: ancosen): We need to add also a subcommand to manage plugins section of the POM, because both Quarkus and Spring Boot will need to add some bits to make the deploy works. > camel-jbang - Run and deploy to Kubernetes > -- > > Key: CAMEL-20904 > URL: https://issues.apache.org/jira/browse/CAMEL-20904 > Project: Camel > Issue Type: New Feature > Components: camel-jbang >Reporter: Claus Ibsen >Priority: Major > Fix For: 4.x > > > Lets see if we can make a command to camel-jbang that can build and deploy a > standard Camel Spring Boot / Camel Quarkus (and potentially camel-main) to > kubernetes. > This would mean to export first, and then build and deploy via SB / Quarkus > standard using how you would normally do this via their maven plugins. > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Comment Edited] (CAMEL-20904) camel-jbang - Run and deploy to Kubernetes
[ https://issues.apache.org/jira/browse/CAMEL-20904?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17856706#comment-17856706 ] Andrea Cosentino edited comment on CAMEL-20904 at 6/21/24 9:17 AM: --- We need to add also a subcommand to manage plugins section of the POM, because both Quarkus and Spring Boot will need to add some bits to make the deploy works. was (Author: ancosen): We need to add also a subcommand to manage plugins section of the POM, because both Quarkus and Spring Boot will need to add some bits to make the deploy work. > camel-jbang - Run and deploy to Kubernetes > -- > > Key: CAMEL-20904 > URL: https://issues.apache.org/jira/browse/CAMEL-20904 > Project: Camel > Issue Type: New Feature > Components: camel-jbang >Reporter: Claus Ibsen >Priority: Major > Fix For: 4.x > > > Lets see if we can make a command to camel-jbang that can build and deploy a > standard Camel Spring Boot / Camel Quarkus (and potentially camel-main) to > kubernetes. > This would mean to export first, and then build and deploy via SB / Quarkus > standard using how you would normally do this via their maven plugins. > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (CAMEL-20904) camel-jbang - Run and deploy to Kubernetes
[ https://issues.apache.org/jira/browse/CAMEL-20904?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17856706#comment-17856706 ] Andrea Cosentino commented on CAMEL-20904: -- We need to add also a subcommand to manage plugins section of the POM, because both Quarkus and Spring Boot will need to add some bits to make the deploy work. > camel-jbang - Run and deploy to Kubernetes > -- > > Key: CAMEL-20904 > URL: https://issues.apache.org/jira/browse/CAMEL-20904 > Project: Camel > Issue Type: New Feature > Components: camel-jbang >Reporter: Claus Ibsen >Priority: Major > Fix For: 4.x > > > Lets see if we can make a command to camel-jbang that can build and deploy a > standard Camel Spring Boot / Camel Quarkus (and potentially camel-main) to > kubernetes. > This would mean to export first, and then build and deploy via SB / Quarkus > standard using how you would normally do this via their maven plugins. > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (CAMEL-20827) Add endpoint service location to aws, azure and google componentd
[ https://issues.apache.org/jira/browse/CAMEL-20827?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17855871#comment-17855871 ] Andrea Cosentino commented on CAMEL-20827: -- AWS completed > Add endpoint service location to aws, azure and google componentd > - > > Key: CAMEL-20827 > URL: https://issues.apache.org/jira/browse/CAMEL-20827 > Project: Camel > Issue Type: New Feature >Reporter: Claus Ibsen >Assignee: Andrea Cosentino >Priority: Major > Fix For: 4.7.0 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (CAMEL-20798) camel-tracing - Add servername to more decorators
[ https://issues.apache.org/jira/browse/CAMEL-20798?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17855869#comment-17855869 ] Andrea Cosentino commented on CAMEL-20798: -- AWS are completed. > camel-tracing - Add servername to more decorators > - > > Key: CAMEL-20798 > URL: https://issues.apache.org/jira/browse/CAMEL-20798 > Project: Camel > Issue Type: Improvement > Components: camel-tracing >Reporter: Claus Ibsen >Assignee: Claus Ibsen >Priority: Major > Fix For: 4.7.0 > > > There is a tag for SERVER_ADDRESS which we can enrich for more of the > decorators. > > Some like JMS is harder as the JMS broker is configured specific such as > ActiveMQ has the brokerURL on the activemq class. > Kafka has boostrapServers etc. > We may add some SPI interface that a component can implemented, and then we > can call it via an endpoint, and then we can use the logic in the component > to return the server address. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (CAMEL-20414) Add CloudEvent Transformers to cloud oriented component
[ https://issues.apache.org/jira/browse/CAMEL-20414?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Cosentino resolved CAMEL-20414. -- Resolution: Fixed > Add CloudEvent Transformers to cloud oriented component > --- > > Key: CAMEL-20414 > URL: https://issues.apache.org/jira/browse/CAMEL-20414 > Project: Camel > Issue Type: Task >Reporter: Andrea Cosentino >Assignee: Andrea Cosentino >Priority: Major > Fix For: 4.7.0 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (CAMEL-20880) Move AI related component to camel-ai middle folder
[ https://issues.apache.org/jira/browse/CAMEL-20880?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Cosentino resolved CAMEL-20880. -- Resolution: Fixed > Move AI related component to camel-ai middle folder > --- > > Key: CAMEL-20880 > URL: https://issues.apache.org/jira/browse/CAMEL-20880 > Project: Camel > Issue Type: Task >Reporter: Andrea Cosentino >Assignee: Andrea Cosentino >Priority: Major > Fix For: 4.7.0 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (CAMEL-20880) Move AI related component to camel-ai middle folder
Andrea Cosentino created CAMEL-20880: Summary: Move AI related component to camel-ai middle folder Key: CAMEL-20880 URL: https://issues.apache.org/jira/browse/CAMEL-20880 Project: Camel Issue Type: Task Reporter: Andrea Cosentino Assignee: Andrea Cosentino Fix For: 4.7.0 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (CAMEL-20876) Support Akeyless Vault service
Andrea Cosentino created CAMEL-20876: Summary: Support Akeyless Vault service Key: CAMEL-20876 URL: https://issues.apache.org/jira/browse/CAMEL-20876 Project: Camel Issue Type: New Feature Reporter: Andrea Cosentino Assignee: Andrea Cosentino Fix For: 4.x https://github.com/akeylesslabs/akeyless-java -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (CAMEL-20797) Camel-Jbang Export Subcommand: Add a parameter to add a plugin in the plugins section of pom
Andrea Cosentino created CAMEL-20797: Summary: Camel-Jbang Export Subcommand: Add a parameter to add a plugin in the plugins section of pom Key: CAMEL-20797 URL: https://issues.apache.org/jira/browse/CAMEL-20797 Project: Camel Issue Type: Improvement Reporter: Andrea Cosentino We can do that for dependencies, but not for plugins. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (CAMEL-20795) camel-nats - NATS Credential file support
[
https://issues.apache.org/jira/browse/CAMEL-20795?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrea Cosentino resolved CAMEL-20795.
--
Resolution: Fixed
> camel-nats - NATS Credential file support
> -
>
> Key: CAMEL-20795
> URL: https://issues.apache.org/jira/browse/CAMEL-20795
> Project: Camel
> Issue Type: Improvement
> Components: camel-nats
>Affects Versions: 4.6.0
>Reporter: Mikael Koskinen
>Assignee: Andrea Cosentino
>Priority: Minor
> Fix For: 4.7.0
>
>
> NATS component currently supports username/password and Token-authentication.
> Unfortunately all the NATS cloud providers (Scaleway, Synadia) use credential
> files for authentication. So currently it is not possible to connect NATS
> component to these hosted NATS solutions.
> Would it be possible to update the NATS component so that it would support
> the credentials file authentication?
> NATS documentation provides an example of how to connect to a NATS server
> using the credentials file:
>
> {code:java}
> Options options = new Options.Builder().
> server("nats://localhost:4222").
> authHandler(Nats.credentials("path_to_creds_file")).
> build();
> Connection nc = Nats.connect(options);
> // Do something with the connection
> nc.close();
> {code}
>
>
> This was previously discussed on of
> https://issues.apache.org/jira/browse/CAMEL-17066
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (CAMEL-20795) camel-nats - NATS Credential file support
[
https://issues.apache.org/jira/browse/CAMEL-20795?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrea Cosentino updated CAMEL-20795:
-
Fix Version/s: 4.7.0
(was: 4.x)
> camel-nats - NATS Credential file support
> -
>
> Key: CAMEL-20795
> URL: https://issues.apache.org/jira/browse/CAMEL-20795
> Project: Camel
> Issue Type: Improvement
> Components: camel-nats
>Affects Versions: 4.6.0
>Reporter: Mikael Koskinen
>Assignee: Andrea Cosentino
>Priority: Minor
> Fix For: 4.7.0
>
>
> NATS component currently supports username/password and Token-authentication.
> Unfortunately all the NATS cloud providers (Scaleway, Synadia) use credential
> files for authentication. So currently it is not possible to connect NATS
> component to these hosted NATS solutions.
> Would it be possible to update the NATS component so that it would support
> the credentials file authentication?
> NATS documentation provides an example of how to connect to a NATS server
> using the credentials file:
>
> {code:java}
> Options options = new Options.Builder().
> server("nats://localhost:4222").
> authHandler(Nats.credentials("path_to_creds_file")).
> build();
> Connection nc = Nats.connect(options);
> // Do something with the connection
> nc.close();
> {code}
>
>
> This was previously discussed on of
> https://issues.apache.org/jira/browse/CAMEL-17066
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Assigned] (CAMEL-20795) camel-nats - NATS Credential file support
[
https://issues.apache.org/jira/browse/CAMEL-20795?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrea Cosentino reassigned CAMEL-20795:
Assignee: Andrea Cosentino
> camel-nats - NATS Credential file support
> -
>
> Key: CAMEL-20795
> URL: https://issues.apache.org/jira/browse/CAMEL-20795
> Project: Camel
> Issue Type: Improvement
> Components: camel-nats
>Affects Versions: 4.6.0
>Reporter: Mikael Koskinen
>Assignee: Andrea Cosentino
>Priority: Minor
> Fix For: 4.x
>
>
> NATS component currently supports username/password and Token-authentication.
> Unfortunately all the NATS cloud providers (Scaleway, Synadia) use credential
> files for authentication. So currently it is not possible to connect NATS
> component to these hosted NATS solutions.
> Would it be possible to update the NATS component so that it would support
> the credentials file authentication?
> NATS documentation provides an example of how to connect to a NATS server
> using the credentials file:
>
> {code:java}
> Options options = new Options.Builder().
> server("nats://localhost:4222").
> authHandler(Nats.credentials("path_to_creds_file")).
> build();
> Connection nc = Nats.connect(options);
> // Do something with the connection
> nc.close();
> {code}
>
>
> This was previously discussed on of
> https://issues.apache.org/jira/browse/CAMEL-17066
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (CAMEL-20795) NATS Credential file support
[
https://issues.apache.org/jira/browse/CAMEL-20795?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17848493#comment-17848493
]
Andrea Cosentino commented on CAMEL-20795:
--
I'll work on this
> NATS Credential file support
>
>
> Key: CAMEL-20795
> URL: https://issues.apache.org/jira/browse/CAMEL-20795
> Project: Camel
> Issue Type: Bug
> Components: camel-nats
>Affects Versions: 4.6.0
>Reporter: Mikael Koskinen
>Priority: Major
>
> NATS component currently supports username/password and Token-authentication.
> Unfortunately all the NATS cloud providers (Scaleway, Synadia) use credential
> files for authentication. So currently it is not possible to connect NATS
> component to these hosted NATS solutions.
> Would it be possible to update the NATS component so that it would support
> the credentials file authentication?
> NATS documentation provides an example of how to connect to a NATS server
> using the credentials file:
>
> {code:java}
> Options options = new Options.Builder().
> server("nats://localhost:4222").
> authHandler(Nats.credentials("path_to_creds_file")).
> build();
> Connection nc = Nats.connect(options);
> // Do something with the connection
> nc.close();
> {code}
>
>
> This was previously discussed on of
> https://issues.apache.org/jira/browse/CAMEL-17066
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (CAMEL-20789) camel-kubernetes - Secrets and Config Maps with binay content should be saved as binary file, instead of String in property resolver
[ https://issues.apache.org/jira/browse/CAMEL-20789?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Cosentino updated CAMEL-20789: - Fix Version/s: 4.7.0 > camel-kubernetes - Secrets and Config Maps with binay content should be saved > as binary file, instead of String in property resolver > > > Key: CAMEL-20789 > URL: https://issues.apache.org/jira/browse/CAMEL-20789 > Project: Camel > Issue Type: Improvement > Components: camel-kubernetes >Affects Versions: 4.6.0 >Reporter: Marco Carletti >Assignee: Marco Carletti >Priority: Minor > Fix For: 4.7.0 > > > Since the content of a Secret or Config Map are dynamically retrieved as > property, it should be useful to have a file path of the downloaded binary > content instead of the String object of the byte[] of a binary content -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (CAMEL-20789) camel-kubernetes - Secrets and Config Maps with binay content should be saved as binary file, instead of String in property resolver
[ https://issues.apache.org/jira/browse/CAMEL-20789?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Cosentino resolved CAMEL-20789. -- Resolution: Fixed > camel-kubernetes - Secrets and Config Maps with binay content should be saved > as binary file, instead of String in property resolver > > > Key: CAMEL-20789 > URL: https://issues.apache.org/jira/browse/CAMEL-20789 > Project: Camel > Issue Type: Improvement > Components: camel-kubernetes >Affects Versions: 4.6.0 >Reporter: Marco Carletti >Assignee: Marco Carletti >Priority: Minor > Fix For: 4.7.0 > > > Since the content of a Secret or Config Map are dynamically retrieved as > property, it should be useful to have a file path of the downloaded binary > content instead of the String object of the byte[] of a binary content -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (CAMEL-20775) camel-hashicorp-vault - configure multiple engines
[
https://issues.apache.org/jira/browse/CAMEL-20775?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrea Cosentino updated CAMEL-20775:
-
Fix Version/s: 4.7.0
(was: 4.x)
> camel-hashicorp-vault - configure multiple engines
> --
>
> Key: CAMEL-20775
> URL: https://issues.apache.org/jira/browse/CAMEL-20775
> Project: Camel
> Issue Type: Improvement
> Components: camel-hashicorp-vault
>Reporter: Federico Mariani
>Assignee: Andrea Cosentino
>Priority: Major
> Fix For: 4.7.0
>
>
> Currently, only one engine can be (easily) configured in the
> camel-hashicorp-vault component.
> It would be nice to configure the engine ala
> \{{hashicorp:engine:path/to/secret}} so that multiple engines can be used in
> the same application. for example, key/value store engine and pki store
> engine.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Assigned] (CAMEL-20775) camel-hashicorp-vault - configure multiple engines
[
https://issues.apache.org/jira/browse/CAMEL-20775?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrea Cosentino reassigned CAMEL-20775:
Assignee: Andrea Cosentino
> camel-hashicorp-vault - configure multiple engines
> --
>
> Key: CAMEL-20775
> URL: https://issues.apache.org/jira/browse/CAMEL-20775
> Project: Camel
> Issue Type: Improvement
> Components: camel-hashicorp-vault
>Reporter: Federico Mariani
>Assignee: Andrea Cosentino
>Priority: Major
> Fix For: 4.x
>
>
> Currently, only one engine can be (easily) configured in the
> camel-hashicorp-vault component.
> It would be nice to configure the engine ala
> \{{hashicorp:engine:path/to/secret}} so that multiple engines can be used in
> the same application. for example, key/value store engine and pki store
> engine.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
