[jira] [Updated] (CAMEL-21536) camel-platform-http-starter throws "No ThreadPoolTaskExecutor configured" if virtual threads are enabled
[
https://issues.apache.org/jira/browse/CAMEL-21536?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bjorn Beskow updated CAMEL-21536:
-
Patch Info: Patch Available
> camel-platform-http-starter throws "No ThreadPoolTaskExecutor configured" if
> virtual threads are enabled
>
>
> Key: CAMEL-21536
> URL: https://issues.apache.org/jira/browse/CAMEL-21536
> Project: Camel
> Issue Type: Bug
> Components: camel-spring-boot-starters
>Affects Versions: 4.8.2, 4.9.0
> Environment: SpringBoot 3.4.0, Java 21.
>Reporter: Bjorn Beskow
>Priority: Major
>
> {color:#00}If spring.threads.virtual.enabled = true, a Camel application
> that uses camel-platform-http-starter fails at startup with{color}
> {color:#00}Caused by: java.lang.RuntimeException: No
> ThreadPoolTaskExecutor configured{color}
> {color:#00} {color}{color:#00}at
> org.apache.camel.component.platform.http.springboot.SpringBootPlatformHttpAutoConfiguration.lambda$springBootPlatformHttpEngine$1(SpringBootPlatformHttpAutoConfiguration.java:54)
> ~[camel-platform-http-starter-4.9.0.jar:4.9.0]{color}
> {color:#00} {color}{color:#00}at
> java.base/java.util.Optional.orElseThrow(Optional.java:403) ~[na:na]{color}
> {color:#00} {color}{color:#00}at
> org.apache.camel.component.platform.http.springboot.SpringBootPlatformHttpAutoConfiguration.springBootPlatformHttpEngine(SpringBootPlatformHttpAutoConfiguration.java:54)
> ~[camel-platform-http-starter-4.9.0.jar:4.9.0]{color}
> {color:#00} {color}{color:#00}at
> java.base/jdk.internal.reflect.DirectMethodHandleAccessor.invoke(DirectMethodHandleAccessor.java:103)
> ~[na:na]{color}
> {color:#00} {color}{color:#00}at
> java.base/java.lang.reflect.Method.invoke(Method.java:580) ~[na:na]{color}
> {color:#00} {color}{color:#00}at
> org.springframework.beans.factory.support.SimpleInstantiationStrategy.lambda$instantiate$0(SimpleInstantiationStrategy.java:171)
> ~[spring-beans-6.2.0.jar:6.2.0]{color}
> {color:#00} {color}{color:#00}... 24 common frames omitted{color}
> {color:#00}unless a ThreadPoolTaskExecutor is explicitly
> configured.{color}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (CAMEL-21536) camel-platform-http-starter throws "No ThreadPoolTaskExecutor configured" if virtual threads are enabled
[
https://issues.apache.org/jira/browse/CAMEL-21536?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17905071#comment-17905071
]
Bjorn Beskow commented on CAMEL-21536:
--
Pull request submitted: https://github.com/apache/camel-spring-boot/pull/1306
> camel-platform-http-starter throws "No ThreadPoolTaskExecutor configured" if
> virtual threads are enabled
>
>
> Key: CAMEL-21536
> URL: https://issues.apache.org/jira/browse/CAMEL-21536
> Project: Camel
> Issue Type: Bug
> Components: camel-spring-boot-starters
>Affects Versions: 4.8.2, 4.9.0
> Environment: SpringBoot 3.4.0, Java 21.
>Reporter: Bjorn Beskow
>Priority: Major
>
> {color:#00}If spring.threads.virtual.enabled = true, a Camel application
> that uses camel-platform-http-starter fails at startup with{color}
> {color:#00}Caused by: java.lang.RuntimeException: No
> ThreadPoolTaskExecutor configured{color}
> {color:#00} {color}{color:#00}at
> org.apache.camel.component.platform.http.springboot.SpringBootPlatformHttpAutoConfiguration.lambda$springBootPlatformHttpEngine$1(SpringBootPlatformHttpAutoConfiguration.java:54)
> ~[camel-platform-http-starter-4.9.0.jar:4.9.0]{color}
> {color:#00} {color}{color:#00}at
> java.base/java.util.Optional.orElseThrow(Optional.java:403) ~[na:na]{color}
> {color:#00} {color}{color:#00}at
> org.apache.camel.component.platform.http.springboot.SpringBootPlatformHttpAutoConfiguration.springBootPlatformHttpEngine(SpringBootPlatformHttpAutoConfiguration.java:54)
> ~[camel-platform-http-starter-4.9.0.jar:4.9.0]{color}
> {color:#00} {color}{color:#00}at
> java.base/jdk.internal.reflect.DirectMethodHandleAccessor.invoke(DirectMethodHandleAccessor.java:103)
> ~[na:na]{color}
> {color:#00} {color}{color:#00}at
> java.base/java.lang.reflect.Method.invoke(Method.java:580) ~[na:na]{color}
> {color:#00} {color}{color:#00}at
> org.springframework.beans.factory.support.SimpleInstantiationStrategy.lambda$instantiate$0(SimpleInstantiationStrategy.java:171)
> ~[spring-beans-6.2.0.jar:6.2.0]{color}
> {color:#00} {color}{color:#00}... 24 common frames omitted{color}
> {color:#00}unless a ThreadPoolTaskExecutor is explicitly
> configured.{color}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Assigned] (CAMEL-21526) camel-aws - Unable to set Timestamp in query parameters to initialize iterator of AT_TIMESTAMP type for AWS Kinesis component
[ https://issues.apache.org/jira/browse/CAMEL-21526?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Cosentino reassigned CAMEL-21526: Assignee: Andrea Cosentino > camel-aws - Unable to set Timestamp in query parameters to initialize > iterator of AT_TIMESTAMP type for AWS Kinesis component > - > > Key: CAMEL-21526 > URL: https://issues.apache.org/jira/browse/CAMEL-21526 > Project: Camel > Issue Type: Bug > Components: camel-aws2-kinesis >Affects Versions: 3.20.9, 4.9.0 >Reporter: Artem >Assignee: Andrea Cosentino >Priority: Minor > Fix For: 4.x > > Attachments: kinesis-timestamp-bug.zip > > > *Problem* > In AWS Kinesis, the iteratorType=AT_TIMESTAMP is an option that allows you to > start consuming records from a stream starting at a specific point in time. > To use iteratorType=AT_TIMESTAMP, we need to request the GetShardIterator > from AWS Kinesis API and specify Timestamp parameter for that request. > This message timestamp parameter must be set initially when we create AWS > Kinesis Consumer. > But in current Camel implementation unfortunately we don't have such ability. > You can see in docs > (https://camel.apache.org/components/next/aws2-kinesis-component.html) that > all we can is to set CamelMessageTimestamp message header. This way is not > suitable for initial setup of the iterator. > Apparently, the most suitable way is to set the timestamp in the URL options > (like for sequenceNumber). > *Steps to reproduce* > You can use the example project attached to this bug. > *Solution* > Possible solution you can find here: > https://github.com/apache/camel/commit/8772c5f2d4a57633447d2717dff53d87555b0e3b -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (CAMEL-21496) Camel-Azure-Key-Vault: Add Update Secret operation to Producer
[ https://issues.apache.org/jira/browse/CAMEL-21496?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Cosentino resolved CAMEL-21496. -- Resolution: Fixed > Camel-Azure-Key-Vault: Add Update Secret operation to Producer > -- > > Key: CAMEL-21496 > URL: https://issues.apache.org/jira/browse/CAMEL-21496 > Project: Camel > Issue Type: New Feature > Components: camel-azure >Reporter: Andrea Cosentino >Assignee: Andrea Cosentino >Priority: Major > Fix For: 4.10.0 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (CAMEL-21526) camel-aws - Unable to set Timestamp in query parameters to initialize iterator of AT_TIMESTAMP type for AWS Kinesis component
[ https://issues.apache.org/jira/browse/CAMEL-21526?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Cosentino updated CAMEL-21526: - Fix Version/s: 4.10.0 (was: 4.x) > camel-aws - Unable to set Timestamp in query parameters to initialize > iterator of AT_TIMESTAMP type for AWS Kinesis component > - > > Key: CAMEL-21526 > URL: https://issues.apache.org/jira/browse/CAMEL-21526 > Project: Camel > Issue Type: Bug > Components: camel-aws2-kinesis >Affects Versions: 3.20.9, 4.9.0 >Reporter: Artem >Assignee: Andrea Cosentino >Priority: Minor > Fix For: 4.10.0 > > Attachments: kinesis-timestamp-bug.zip > > > *Problem* > In AWS Kinesis, the iteratorType=AT_TIMESTAMP is an option that allows you to > start consuming records from a stream starting at a specific point in time. > To use iteratorType=AT_TIMESTAMP, we need to request the GetShardIterator > from AWS Kinesis API and specify Timestamp parameter for that request. > This message timestamp parameter must be set initially when we create AWS > Kinesis Consumer. > But in current Camel implementation unfortunately we don't have such ability. > You can see in docs > (https://camel.apache.org/components/next/aws2-kinesis-component.html) that > all we can is to set CamelMessageTimestamp message header. This way is not > suitable for initial setup of the iterator. > Apparently, the most suitable way is to set the timestamp in the URL options > (like for sequenceNumber). > *Steps to reproduce* > You can use the example project attached to this bug. > *Solution* > Possible solution you can find here: > https://github.com/apache/camel/commit/8772c5f2d4a57633447d2717dff53d87555b0e3b -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (CAMEL-21536) camel-platform-http-starter throws "No ThreadPoolTaskExecutor configured" if virtual threads are enabled
[
https://issues.apache.org/jira/browse/CAMEL-21536?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen resolved CAMEL-21536.
-
Resolution: Fixed
Thanks for the PR
> camel-platform-http-starter throws "No ThreadPoolTaskExecutor configured" if
> virtual threads are enabled
>
>
> Key: CAMEL-21536
> URL: https://issues.apache.org/jira/browse/CAMEL-21536
> Project: Camel
> Issue Type: Bug
> Components: camel-spring-boot-starters
>Affects Versions: 4.8.2, 4.9.0
> Environment: SpringBoot 3.4.0, Java 21.
>Reporter: Bjorn Beskow
>Priority: Major
> Fix For: 4.8.3, 4.10.0
>
>
> {color:#00}If spring.threads.virtual.enabled = true, a Camel application
> that uses camel-platform-http-starter fails at startup with{color}
> {color:#00}Caused by: java.lang.RuntimeException: No
> ThreadPoolTaskExecutor configured{color}
> {color:#00} {color}{color:#00}at
> org.apache.camel.component.platform.http.springboot.SpringBootPlatformHttpAutoConfiguration.lambda$springBootPlatformHttpEngine$1(SpringBootPlatformHttpAutoConfiguration.java:54)
> ~[camel-platform-http-starter-4.9.0.jar:4.9.0]{color}
> {color:#00} {color}{color:#00}at
> java.base/java.util.Optional.orElseThrow(Optional.java:403) ~[na:na]{color}
> {color:#00} {color}{color:#00}at
> org.apache.camel.component.platform.http.springboot.SpringBootPlatformHttpAutoConfiguration.springBootPlatformHttpEngine(SpringBootPlatformHttpAutoConfiguration.java:54)
> ~[camel-platform-http-starter-4.9.0.jar:4.9.0]{color}
> {color:#00} {color}{color:#00}at
> java.base/jdk.internal.reflect.DirectMethodHandleAccessor.invoke(DirectMethodHandleAccessor.java:103)
> ~[na:na]{color}
> {color:#00} {color}{color:#00}at
> java.base/java.lang.reflect.Method.invoke(Method.java:580) ~[na:na]{color}
> {color:#00} {color}{color:#00}at
> org.springframework.beans.factory.support.SimpleInstantiationStrategy.lambda$instantiate$0(SimpleInstantiationStrategy.java:171)
> ~[spring-beans-6.2.0.jar:6.2.0]{color}
> {color:#00} {color}{color:#00}... 24 common frames omitted{color}
> {color:#00}unless a ThreadPoolTaskExecutor is explicitly
> configured.{color}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (CAMEL-21536) camel-platform-http-starter throws "No ThreadPoolTaskExecutor configured" if virtual threads are enabled
[
https://issues.apache.org/jira/browse/CAMEL-21536?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen updated CAMEL-21536:
Fix Version/s: 4.8.3
4.10.0
> camel-platform-http-starter throws "No ThreadPoolTaskExecutor configured" if
> virtual threads are enabled
>
>
> Key: CAMEL-21536
> URL: https://issues.apache.org/jira/browse/CAMEL-21536
> Project: Camel
> Issue Type: Bug
> Components: camel-spring-boot-starters
>Affects Versions: 4.8.2, 4.9.0
> Environment: SpringBoot 3.4.0, Java 21.
>Reporter: Bjorn Beskow
>Priority: Major
> Fix For: 4.8.3, 4.10.0
>
>
> {color:#00}If spring.threads.virtual.enabled = true, a Camel application
> that uses camel-platform-http-starter fails at startup with{color}
> {color:#00}Caused by: java.lang.RuntimeException: No
> ThreadPoolTaskExecutor configured{color}
> {color:#00} {color}{color:#00}at
> org.apache.camel.component.platform.http.springboot.SpringBootPlatformHttpAutoConfiguration.lambda$springBootPlatformHttpEngine$1(SpringBootPlatformHttpAutoConfiguration.java:54)
> ~[camel-platform-http-starter-4.9.0.jar:4.9.0]{color}
> {color:#00} {color}{color:#00}at
> java.base/java.util.Optional.orElseThrow(Optional.java:403) ~[na:na]{color}
> {color:#00} {color}{color:#00}at
> org.apache.camel.component.platform.http.springboot.SpringBootPlatformHttpAutoConfiguration.springBootPlatformHttpEngine(SpringBootPlatformHttpAutoConfiguration.java:54)
> ~[camel-platform-http-starter-4.9.0.jar:4.9.0]{color}
> {color:#00} {color}{color:#00}at
> java.base/jdk.internal.reflect.DirectMethodHandleAccessor.invoke(DirectMethodHandleAccessor.java:103)
> ~[na:na]{color}
> {color:#00} {color}{color:#00}at
> java.base/java.lang.reflect.Method.invoke(Method.java:580) ~[na:na]{color}
> {color:#00} {color}{color:#00}at
> org.springframework.beans.factory.support.SimpleInstantiationStrategy.lambda$instantiate$0(SimpleInstantiationStrategy.java:171)
> ~[spring-beans-6.2.0.jar:6.2.0]{color}
> {color:#00} {color}{color:#00}... 24 common frames omitted{color}
> {color:#00}unless a ThreadPoolTaskExecutor is explicitly
> configured.{color}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (CAMEL-21526) camel-aws - Unable to set Timestamp in query parameters to initialize iterator of AT_TIMESTAMP type for AWS Kinesis component
[ https://issues.apache.org/jira/browse/CAMEL-21526?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Cosentino updated CAMEL-21526: - Fix Version/s: 4.8.3 > camel-aws - Unable to set Timestamp in query parameters to initialize > iterator of AT_TIMESTAMP type for AWS Kinesis component > - > > Key: CAMEL-21526 > URL: https://issues.apache.org/jira/browse/CAMEL-21526 > Project: Camel > Issue Type: Bug > Components: camel-aws2-kinesis >Affects Versions: 3.20.9, 4.9.0 >Reporter: Artem >Assignee: Andrea Cosentino >Priority: Minor > Fix For: 4.8.3, 4.10.0 > > Attachments: kinesis-timestamp-bug.zip > > > *Problem* > In AWS Kinesis, the iteratorType=AT_TIMESTAMP is an option that allows you to > start consuming records from a stream starting at a specific point in time. > To use iteratorType=AT_TIMESTAMP, we need to request the GetShardIterator > from AWS Kinesis API and specify Timestamp parameter for that request. > This message timestamp parameter must be set initially when we create AWS > Kinesis Consumer. > But in current Camel implementation unfortunately we don't have such ability. > You can see in docs > (https://camel.apache.org/components/next/aws2-kinesis-component.html) that > all we can is to set CamelMessageTimestamp message header. This way is not > suitable for initial setup of the iterator. > Apparently, the most suitable way is to set the timestamp in the URL options > (like for sequenceNumber). > *Steps to reproduce* > You can use the example project attached to this bug. > *Solution* > Possible solution you can find here: > https://github.com/apache/camel/commit/8772c5f2d4a57633447d2717dff53d87555b0e3b -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (CAMEL-21535) camel-groovy - Make it easier for low-code to validate scripts
[
https://issues.apache.org/jira/browse/CAMEL-21535?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17905097#comment-17905097
]
Raymond commented on CAMEL-21535:
-
Just for reference:
In Assimbly we have a validator package:
[https://github.com/assimbly/runtime/tree/develop/dil/src/main/java/org/assimbly/dil/validation]
This also include a script validator class. This is used in a low-code platform
Dovetail:
[https://academy.dovetail.world/docs/components/construction/script#example-of-script-evaluation]
A side note:
In general, the script validator works fine for us, but we do miss the line
number on the errors. So that would be a good gain. Also, in some rare cases
the script is validated correctly, but fails in a real route. For example, this
line:
{code:java}
GString host = “${serviceName}.${region}.amazonaws.com”{code}
This code validated correctly, but failed when setting the host variable to a
header with a Groovy script in a route.
This probably is because the validation method used implicitly a toString()
method on the GString object in the header, while when running in a route
(using direct as transport) the object stays as is, and was then represented as
'json' in the tracing. When putting a ActiveMQ queue after the script, it
worked, because probably there also a toString() kind of conversion is done.
Then I got the feedback from users: "your validation is not trustable, because
there is a difference between validating and real usage of the script." So it's
good to check/test if output of the validation is exactly the same as the
output of running the script in a route.
> camel-groovy - Make it easier for low-code to validate scripts
> --
>
> Key: CAMEL-21535
> URL: https://issues.apache.org/jira/browse/CAMEL-21535
> Project: Camel
> Issue Type: Improvement
> Components: camel-groovy
>Reporter: Claus Ibsen
>Assignee: Claus Ibsen
>Priority: Major
> Fix For: 4.10.0
>
>
> The Camel tool needs a bit easier way to validate that groovy scripts (and
> potential others) can be quickly validated - there is some APIs in
> camel-catalog but it does not fit as well to groovy as lack of camel context
> being present, and also lack of more precise line number error reporting.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Resolved] (CAMEL-21537) Camel-mongodb - Provide ppc64le arch support
[ https://issues.apache.org/jira/browse/CAMEL-21537?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen resolved CAMEL-21537. - Resolution: Fixed > Camel-mongodb - Provide ppc64le arch support > > > Key: CAMEL-21537 > URL: https://issues.apache.org/jira/browse/CAMEL-21537 > Project: Camel > Issue Type: Task > Components: camel-mongodb >Reporter: Anushka Juli >Priority: Minor > Fix For: 4.10.0 > > Attachments: ppc64le_mongodb_main_build_logs.txt, > ppc64le_mongodb_test_infra_logs.txt, x86_mongodb_test_infra_logs.txt > > > We want to provide ppc64le arch support to camel-mongodb in the camel > component -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (CAMEL-21537) Camel-mongodb - Provide ppc64le arch support
[ https://issues.apache.org/jira/browse/CAMEL-21537?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen updated CAMEL-21537: Fix Version/s: 4.10.0 > Camel-mongodb - Provide ppc64le arch support > > > Key: CAMEL-21537 > URL: https://issues.apache.org/jira/browse/CAMEL-21537 > Project: Camel > Issue Type: Task > Components: camel-mongodb >Reporter: Anushka Juli >Priority: Minor > Fix For: 4.10.0 > > Attachments: ppc64le_mongodb_main_build_logs.txt, > ppc64le_mongodb_test_infra_logs.txt, x86_mongodb_test_infra_logs.txt > > > We want to provide ppc64le arch support to camel-mongodb in the camel > component -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (CAMEL-21466) camel-jbang - camel k8s delete may not cleanup properly
[ https://issues.apache.org/jira/browse/CAMEL-21466?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17905143#comment-17905143 ] Thomas Diesler commented on CAMEL-21466: When loading resources from manifest, they may not be associated with a namespace. In this case, the client does not find the resources with its default configuration. Explicitly setting the "default" namespace fixes this. Whether this is intended behaviour or a bug I don't really know. For simple 'get pods' operations, the client does not seem to need an explicit namespace. As a fix, I propose to explicitly fall back to the "default" namespace after default settings did not find the resources from the manifest. > camel-jbang - camel k8s delete may not cleanup properly > --- > > Key: CAMEL-21466 > URL: https://issues.apache.org/jira/browse/CAMEL-21466 > Project: Camel > Issue Type: Bug > Components: camel-jbang >Reporter: Thomas Diesler >Assignee: Thomas Diesler >Priority: Major > > --cleanup=true is the default and should delete the deployment on ctrl+c -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Work started] (CAMEL-21538) [camel-tracing] Deprecate MDC in favour of implementation specific instrumentation
[ https://issues.apache.org/jira/browse/CAMEL-21538?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on CAMEL-21538 started by Pasquale Congiusti. -- > [camel-tracing] Deprecate MDC in favour of implementation specific > instrumentation > -- > > Key: CAMEL-21538 > URL: https://issues.apache.org/jira/browse/CAMEL-21538 > Project: Camel > Issue Type: Improvement >Affects Versions: 4.9.0 >Reporter: Pasquale Congiusti >Assignee: Pasquale Congiusti >Priority: Minor > Fix For: 4.10.0 > > > In camel-tracing component we're supporting a custom setting of MDC trace_id > and span_id. This is requiring a deep coupling between the core and the > tracing component and is very error prone as it requires a proper cleaning to > avoid that any traces set in the thread previously is not used afterwards. As > shown in CAMEL-21472 there are inconsistencies that would suggest to > deprecate this feature and favouring the specific tracing implementation (ie, > Opentelemetry, Micrometer Observability) instead. > These frameworks are already providing embedded mechanisms to set and clear > the MDC while they manage the related traces/spans. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (CAMEL-21466) camel-jbang - camel k8s delete may not cleanup properly
[ https://issues.apache.org/jira/browse/CAMEL-21466?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thomas Diesler updated CAMEL-21466: --- Summary: camel-jbang - camel k8s delete may not cleanup properly (was: camel-jbang - camel k8s delete does not cleanup properly) > camel-jbang - camel k8s delete may not cleanup properly > --- > > Key: CAMEL-21466 > URL: https://issues.apache.org/jira/browse/CAMEL-21466 > Project: Camel > Issue Type: Bug > Components: camel-jbang >Reporter: Thomas Diesler >Assignee: Thomas Diesler >Priority: Major > > --cleanup=true is the default and should delete the deployment on ctrl+c -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (CAMEL-21526) camel-aws - Unable to set Timestamp in query parameters to initialize iterator of AT_TIMESTAMP type for AWS Kinesis component
[ https://issues.apache.org/jira/browse/CAMEL-21526?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Cosentino resolved CAMEL-21526. -- Resolution: Fixed > camel-aws - Unable to set Timestamp in query parameters to initialize > iterator of AT_TIMESTAMP type for AWS Kinesis component > - > > Key: CAMEL-21526 > URL: https://issues.apache.org/jira/browse/CAMEL-21526 > Project: Camel > Issue Type: Bug > Components: camel-aws2-kinesis >Affects Versions: 3.20.9, 4.9.0 >Reporter: Artem >Assignee: Andrea Cosentino >Priority: Minor > Fix For: 4.8.3, 4.10.0 > > Attachments: kinesis-timestamp-bug.zip > > > *Problem* > In AWS Kinesis, the iteratorType=AT_TIMESTAMP is an option that allows you to > start consuming records from a stream starting at a specific point in time. > To use iteratorType=AT_TIMESTAMP, we need to request the GetShardIterator > from AWS Kinesis API and specify Timestamp parameter for that request. > This message timestamp parameter must be set initially when we create AWS > Kinesis Consumer. > But in current Camel implementation unfortunately we don't have such ability. > You can see in docs > (https://camel.apache.org/components/next/aws2-kinesis-component.html) that > all we can is to set CamelMessageTimestamp message header. This way is not > suitable for initial setup of the iterator. > Apparently, the most suitable way is to set the timestamp in the URL options > (like for sequenceNumber). > *Steps to reproduce* > You can use the example project attached to this bug. > *Solution* > Possible solution you can find here: > https://github.com/apache/camel/commit/8772c5f2d4a57633447d2717dff53d87555b0e3b -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (CAMEL-21535) camel-groovy - Make it easier for low-code to validate scripts
[ https://issues.apache.org/jira/browse/CAMEL-21535?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17905199#comment-17905199 ] Claus Ibsen commented on CAMEL-21535: - Thanks for the pointers. We have improved camel-groovy and its able to get "index" in some situations - the index is absolute pos in the script > camel-groovy - Make it easier for low-code to validate scripts > -- > > Key: CAMEL-21535 > URL: https://issues.apache.org/jira/browse/CAMEL-21535 > Project: Camel > Issue Type: Improvement > Components: camel-groovy >Reporter: Claus Ibsen >Assignee: Claus Ibsen >Priority: Major > Fix For: 4.10.0 > > > The Camel tool needs a bit easier way to validate that groovy scripts (and > potential others) can be quickly validated - there is some APIs in > camel-catalog but it does not fit as well to groovy as lack of camel context > being present, and also lack of more precise line number error reporting. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (CAMEL-21535) camel-groovy - Make it easier for low-code to validate scripts
[ https://issues.apache.org/jira/browse/CAMEL-21535?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen resolved CAMEL-21535. - Resolution: Fixed > camel-groovy - Make it easier for low-code to validate scripts > -- > > Key: CAMEL-21535 > URL: https://issues.apache.org/jira/browse/CAMEL-21535 > Project: Camel > Issue Type: Improvement > Components: camel-groovy >Reporter: Claus Ibsen >Assignee: Claus Ibsen >Priority: Major > Fix For: 4.10.0 > > > The Camel tool needs a bit easier way to validate that groovy scripts (and > potential others) can be quickly validated - there is some APIs in > camel-catalog but it does not fit as well to groovy as lack of camel context > being present, and also lack of more precise line number error reporting. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (CAMEL-21539) Vector Database capabilities - Infinispan
[ https://issues.apache.org/jira/browse/CAMEL-21539?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zineb Bendhiba updated CAMEL-21539: --- Description: Implement Vector search capabilities for Infinispan. Also add the langchain4j Embeddings DataFormat for Infinispan + an Integration test in the langchain4j embeddings directory https://github.com/apache/camel/tree/main/components/camel-ai/camel-langchain4j-embeddings/src/test/java/org/apache/camel/component/langchain4j/embeddings was: Implement Vector search capabilities for Infinispan. Also add the langchain4j Embeddings DataFormat for Infinispan. > Vector Database capabilities - Infinispan > - > > Key: CAMEL-21539 > URL: https://issues.apache.org/jira/browse/CAMEL-21539 > Project: Camel > Issue Type: New Feature >Reporter: Zineb Bendhiba >Priority: Major > > Implement Vector search capabilities for Infinispan. > Also add the langchain4j Embeddings DataFormat for Infinispan + an > Integration test in the langchain4j embeddings directory > https://github.com/apache/camel/tree/main/components/camel-ai/camel-langchain4j-embeddings/src/test/java/org/apache/camel/component/langchain4j/embeddings -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (CAMEL-21539) Vector Database capabilities - Infinispan
Zineb Bendhiba created CAMEL-21539: -- Summary: Vector Database capabilities - Infinispan Key: CAMEL-21539 URL: https://issues.apache.org/jira/browse/CAMEL-21539 Project: Camel Issue Type: New Feature Reporter: Zineb Bendhiba Implement Vector search capabilities for Infinispan. Also add the langchain4j Embeddings DataFormat for Infinispan. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (CAMEL-21540) Vector Database capabilities - PostgreSQL
[ https://issues.apache.org/jira/browse/CAMEL-21540?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zineb Bendhiba updated CAMEL-21540: --- Description: Implement Vector search capabilities for PostgreSQL. Also add the langchain4j Embeddings DataFormat for PostgreSQL + an Integration test in the langchain4j embeddings directory [https://github.com/apache/camel/tree/main/components/camel-ai/camel-langchain4j-embeddings/src/test/java/org/apache/camel/component/langchain4j/embeddings] was: Implement Vector search capabilities for Infinispan. Also add the langchain4j Embeddings DataFormat for Infinispan + an Integration test in the langchain4j embeddings directory https://github.com/apache/camel/tree/main/components/camel-ai/camel-langchain4j-embeddings/src/test/java/org/apache/camel/component/langchain4j/embeddings > Vector Database capabilities - PostgreSQL > - > > Key: CAMEL-21540 > URL: https://issues.apache.org/jira/browse/CAMEL-21540 > Project: Camel > Issue Type: New Feature >Reporter: Zineb Bendhiba >Priority: Major > > Implement Vector search capabilities for PostgreSQL. > Also add the langchain4j Embeddings DataFormat for PostgreSQL + an > Integration test in the langchain4j embeddings directory > [https://github.com/apache/camel/tree/main/components/camel-ai/camel-langchain4j-embeddings/src/test/java/org/apache/camel/component/langchain4j/embeddings] -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (CAMEL-21540) Vector Database capabilities - PostgreSQL
Zineb Bendhiba created CAMEL-21540: -- Summary: Vector Database capabilities - PostgreSQL Key: CAMEL-21540 URL: https://issues.apache.org/jira/browse/CAMEL-21540 Project: Camel Issue Type: New Feature Reporter: Zineb Bendhiba Implement Vector search capabilities for Infinispan. Also add the langchain4j Embeddings DataFormat for Infinispan + an Integration test in the langchain4j embeddings directory https://github.com/apache/camel/tree/main/components/camel-ai/camel-langchain4j-embeddings/src/test/java/org/apache/camel/component/langchain4j/embeddings -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (CAMEL-21541) Neo4j - investigate on ingesting data with Neo4j and Langchain4j
Zineb Bendhiba created CAMEL-21541: -- Summary: Neo4j - investigate on ingesting data with Neo4j and Langchain4j Key: CAMEL-21541 URL: https://issues.apache.org/jira/browse/CAMEL-21541 Project: Camel Issue Type: New Feature Reporter: Zineb Bendhiba Assignee: Zineb Bendhiba -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (CAMEL-21538) [camel-tracing] Deprecate MDC in favour of implementation specific instrumentation
Pasquale Congiusti created CAMEL-21538: -- Summary: [camel-tracing] Deprecate MDC in favour of implementation specific instrumentation Key: CAMEL-21538 URL: https://issues.apache.org/jira/browse/CAMEL-21538 Project: Camel Issue Type: Improvement Affects Versions: 4.9.0 Reporter: Pasquale Congiusti Assignee: Pasquale Congiusti Fix For: 4.10.0 In camel-tracing component we're supporting a custom setting of MDC trace_id and span_id. This is requiring a deep coupling between the core and the tracing component and is very error prone as it requires a proper cleaning to avoid that any traces set in the thread previously is not used afterwards. As shown in CAMEL-21472 there are inconsistencies that would suggest to deprecate this feature and favouring the specific tracing implementation (ie, Opentelemetry, Micrometer Observability) instead. These frameworks are already providing embedded mechanisms to set and clear the MDC while they manage the related traces/spans. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (CAMEL-21542) camel-jbang - Detect known beans from Java imports
Claus Ibsen created CAMEL-21542: --- Summary: camel-jbang - Detect known beans from Java imports Key: CAMEL-21542 URL: https://issues.apache.org/jira/browse/CAMEL-21542 Project: Camel Issue Type: Improvement Components: camel-jbang Reporter: Claus Ibsen Assignee: Claus Ibsen Fix For: 4.10.0 When using Java code you may write some code that uses Camel beans such as a Kafka repository. This code cannot compile because you need camel-kafka on classpath, and the user may need to add this manually in jbang. We should try to detect this and auto download the JAR -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (CAMEL-21542) camel-jbang - Detect known beans from Java imports
[ https://issues.apache.org/jira/browse/CAMEL-21542?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen resolved CAMEL-21542. - Resolution: Fixed > camel-jbang - Detect known beans from Java imports > -- > > Key: CAMEL-21542 > URL: https://issues.apache.org/jira/browse/CAMEL-21542 > Project: Camel > Issue Type: Improvement > Components: camel-jbang >Reporter: Claus Ibsen >Assignee: Claus Ibsen >Priority: Major > Fix For: 4.10.0 > > > When using Java code you may write some code that uses Camel beans such as a > Kafka repository. > This code cannot compile because you need camel-kafka on classpath, and the > user may need to add this manually in jbang. > We should try to detect this and auto download the JAR > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (CAMEL-21478) camel-rest-openapi: Input and output types binding to java classes using $ref or title of the schema
[
https://issues.apache.org/jira/browse/CAMEL-21478?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17905276#comment-17905276
]
Chamodya Dias commented on CAMEL-21478:
---
Thanks, will do asap!
> camel-rest-openapi: Input and output types binding to java classes using $ref
> or title of the schema
>
>
> Key: CAMEL-21478
> URL: https://issues.apache.org/jira/browse/CAMEL-21478
> Project: Camel
> Issue Type: Improvement
> Components: camel-rest-openapi
>Affects Versions: 4.8.0, 4.8.1
>Reporter: Chamodya Dias
>Priority: Minor
> Fix For: 4.10.0
>
>
> Currently, camel resolves the Java class names for RestBindingConfiguration
> from Schema XML attribute.
> Implemented at: org.apache.camel.component.rest.openapi.RestOpenApiProcessor
> ```
> private RestBindingConfiguration createRestBindingConfiguration(Operation o)
> throws Exception {
> ...
> ...
> Schema s = m.getValue().getSchema();
> // $ref is null, so we need to know the schema name via XML
> if (s != null && s.getXml() != null) {
> String ref = s.getXml().getName();
> ...
> ```
>
> But the documentation says Camel can resolve the schema from the schema name:
> [https://camel.apache.org/manual/rest-dsl-openapi.html#_binding_to_pojo_classes]
>
> This improvement suggests adding an `else-if` condition that to above code
> that uses `$ref` to resolve the schema name if available and another
> `else-if` condition that uses the `title` attribute
> (https://github.com/OAI/OpenAPI-Specification/blob/3.0.2/versions/3.0.2.md#schema-object)
> of the schema to get the class name if available.
>
> Also, the current implementation doesn't resolve class names when using the
> `requestBodies` component directly in the OAS. It only uses `content`
> attribute.
>
> example:
> ```
> requestBody:
> $ref: '#/components/requestBodies/createProduct'
> ```
> This improvement suggests the capability to add this also.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Resolved] (CAMEL-21466) camel-jbang - camel k8s delete may not cleanup properly
[ https://issues.apache.org/jira/browse/CAMEL-21466?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thomas Diesler resolved CAMEL-21466. Resolution: Fixed Done > camel-jbang - camel k8s delete may not cleanup properly > --- > > Key: CAMEL-21466 > URL: https://issues.apache.org/jira/browse/CAMEL-21466 > Project: Camel > Issue Type: Bug > Components: camel-jbang >Reporter: Thomas Diesler >Assignee: Thomas Diesler >Priority: Major > > --cleanup=true is the default and should delete the deployment on ctrl+c -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (CAMEL-21533) Backport Knative test coverage to 4.8.x
[ https://issues.apache.org/jira/browse/CAMEL-21533?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thomas Diesler resolved CAMEL-21533. Resolution: Fixed Done > Backport Knative test coverage to 4.8.x > --- > > Key: CAMEL-21533 > URL: https://issues.apache.org/jira/browse/CAMEL-21533 > Project: Camel > Issue Type: Task > Components: camel-jbang >Reporter: Thomas Diesler >Assignee: Thomas Diesler >Priority: Major > Fix For: 4.8.3 > > > The backport for knative test coverage was not strait forward because there > was no target to apply the changes too. Hence, they have been left out in the > backport PR. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (CAMEL-21530) camel-jbang - Remove deps on runtime and cluster-type where no longer needed
[ https://issues.apache.org/jira/browse/CAMEL-21530?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thomas Diesler resolved CAMEL-21530. Resolution: Fixed Done > camel-jbang - Remove deps on runtime and cluster-type where no longer needed > > > Key: CAMEL-21530 > URL: https://issues.apache.org/jira/browse/CAMEL-21530 > Project: Camel > Issue Type: Task > Components: camel-jbang >Reporter: Thomas Diesler >Assignee: Thomas Diesler >Priority: Major > Fix For: 4.8.3, 4.10.0 > > > Now, that every runtime and cluster-type uses JKube to generate the k8s > resources. It is no longer needed to switch behaviour depending on runtime or > cluster-type. Some API methods still carry those parameters. -- This message was sent by Atlassian Jira (v8.20.10#820010)
