[jira] [Created] (CAMEL-21587) Langchain4j : add similarity search
Zineb Bendhiba created CAMEL-21587: -- Summary: Langchain4j : add similarity search Key: CAMEL-21587 URL: https://issues.apache.org/jira/browse/CAMEL-21587 Project: Camel Issue Type: New Feature Reporter: Zineb Bendhiba Assignee: Zineb Bendhiba +*Problem:*+ Apache Camel Langchain4j and Vector databases (Qdrant/Pinecone) can't perform similarity search for RAG. This limitation hinders our ability to use Apache Camel with Vector databases with Langchain4j for robust search capabilities. While creating an example of RAG using Apache Camel Langchain4j and Apache Camel Vector databases, I realized that the Vector databases components cannot handle similarity search for the Langchain4j scenarios. Despite trying both Qdrant and Pinecone, I encountered issues when attempting to perform RAG (Relevance-based Active Learning) with these databases. +*Research*+ I've analyzed various existing issues related to Search with Qdrant and Pinecone. For example, the Camel Qdrant component doesn't provide similarity search capabilities. In contrast, Pinecone allows for searching based on similarity. However, when trying to use Pinecone with Apache Camel, I encountered a challenge: we need to convert text to Embeddings using Camel Langchain4j Embeddings Component. The resulting list of Embeddings cannot be used directly with RAG. +*Proposed Solution*+ To address this limitation, I propose implementing a new feature (or new camel AI component) that enables easy similarity search for RAG using Apache Camel and Vector databases. This could involve leveraging the abstraction from Embedding stores in Langchain4j to provide an easy way to perform similarity searches. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (CAMEL-21589) Make manual acknowledgements configurable in Paho-Mqtt5
[ https://issues.apache.org/jira/browse/CAMEL-21589?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rav Brar updated CAMEL-21589: - Issue Type: Improvement (was: New Feature) > Make manual acknowledgements configurable in Paho-Mqtt5 > --- > > Key: CAMEL-21589 > URL: https://issues.apache.org/jira/browse/CAMEL-21589 > Project: Camel > Issue Type: Improvement > Components: came-core >Reporter: Rav Brar >Priority: Major > > When using the Camel MQTT5 Source Kafka Connector, messages are automatically > acknowledged, which doesn't ensure they reach their final destination at > least once. Enabling manual acknowledgements ensures the connector is able to > provide at least once delivery to topics. > This new parameter would make it possible for the user to enable manual > acknowledgements in the client. By default, the parameter is set to false and > messages will be automatically acknowledged. If set to true, the > acknowledgement is added in the exchange's completion callback. > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (CAMEL-21438) tests: investigate flaky tests on alternative platforms
[ https://issues.apache.org/jira/browse/CAMEL-21438?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17909675#comment-17909675 ] Jang-Vijay Singh commented on CAMEL-21438: -- Please share some observations of currently flaky tests. Some of the camel-kafka BreakOnFirstError* tests that were enabled on those platforms after significant changes seemed quite stable. eg. https://issues.apache.org/jira/browse/CAMEL-20722 Not all were enabled but worth examining the enabled ones, and identifying some examples of ones that are flaky now. I’d like to look in to this if that’s ok > tests: investigate flaky tests on alternative platforms > --- > > Key: CAMEL-21438 > URL: https://issues.apache.org/jira/browse/CAMEL-21438 > Project: Camel > Issue Type: Test > Components: camel-core, camel-file, camel-lumberjack >Affects Versions: 4.9.0 >Reporter: Otavio Rodolfo Piske >Priority: Major > Labels: help-wanted > > We have multiple tests that run unreliably on platforms such as ppc64le, > s390x and aarch64. > At lot of these tests are related to concurrency and threading scenarios, > which could indicate incorrect assumptions about the memory model behavior on > these platforms. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (CAMEL-21438) tests: investigate flaky tests on alternative platforms
[ https://issues.apache.org/jira/browse/CAMEL-21438?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17909676#comment-17909676 ] Jang-Vijay Singh commented on CAMEL-21438: -- PS: Checking linked PRs for disabled tests > tests: investigate flaky tests on alternative platforms > --- > > Key: CAMEL-21438 > URL: https://issues.apache.org/jira/browse/CAMEL-21438 > Project: Camel > Issue Type: Test > Components: camel-core, camel-file, camel-lumberjack >Affects Versions: 4.9.0 >Reporter: Otavio Rodolfo Piske >Priority: Major > Labels: help-wanted > > We have multiple tests that run unreliably on platforms such as ppc64le, > s390x and aarch64. > At lot of these tests are related to concurrency and threading scenarios, > which could indicate incorrect assumptions about the memory model behavior on > these platforms. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (CAMEL-21583) Fix issue related to flaky Jetty tests "Exception occurred during execution on the exchange: Exchange[]"
Aurélien Pupier created CAMEL-21583:
---
Summary: Fix issue related to flaky Jetty tests "Exception
occurred during execution on the exchange: Exchange[]"
Key: CAMEL-21583
URL: https://issues.apache.org/jira/browse/CAMEL-21583
Project: Camel
Issue Type: Test
Components: camel-jetty
Affects Versions: 4.9.0
Reporter: Aurélien Pupier
with the last 5 builds on CI, there was at least one Jetty tests failing with
this kind of error:
{noformat}
org.apache.camel.CamelExecutionException: Exception occurred during execution
on the exchange: Exchange[]
at
org.apache.camel.CamelExecutionException.wrapCamelExecutionException(CamelExecutionException.java:45)
at
org.apache.camel.support.ExchangeHelper.extractResultBody(ExchangeHelper.java:698)
at
org.apache.camel.impl.engine.DefaultProducerTemplate.extractResultBody(DefaultProducerTemplate.java:591)
at
org.apache.camel.impl.engine.DefaultProducerTemplate.extractResultBody(DefaultProducerTemplate.java:587)
at
org.apache.camel.impl.engine.DefaultProducerTemplate.sendBodyAndHeader(DefaultProducerTemplate.java:221)
at
org.apache.camel.impl.engine.DefaultProducerTemplate.sendBodyAndHeader(DefaultProducerTemplate.java:213)
at
org.apache.camel.component.jetty.HttpsRouteTest.invokeHttpEndpoint(HttpsRouteTest.java:175)
at
org.apache.camel.component.jetty.HttpsRouteTest.testEndpoint(HttpsRouteTest.java:121)
at java.base/java.lang.reflect.Method.invoke(Method.java:580)
at
java.base/java.util.concurrent.ForkJoinTask.doExec(ForkJoinTask.java:387)
at
java.base/java.util.concurrent.ForkJoinPool$WorkQueue.topLevelExec(ForkJoinPool.java:1312)
at
java.base/java.util.concurrent.ForkJoinPool.scan(ForkJoinPool.java:1843)
at
java.base/java.util.concurrent.ForkJoinPool.runWorker(ForkJoinPool.java:1808)
at
java.base/java.util.concurrent.ForkJoinWorkerThread.run(ForkJoinWorkerThread.java:188)
Caused by: org.apache.hc.client5.http.HttpHostConnectException: Connect to
https://localhost:36391 [localhost/127.0.0.1, localhost/127.0.1.1] failed:
Connection refused
at java.base/sun.nio.ch.Net.pollConnect(Native Method)
at java.base/sun.nio.ch.Net.pollConnectNow(Net.java:682)
at
java.base/sun.nio.ch.NioSocketImpl.timedFinishConnect(NioSocketImpl.java:542)
at java.base/sun.nio.ch.NioSocketImpl.connect(NioSocketImpl.java:592)
at java.base/java.net.SocksSocketImpl.connect(SocksSocketImpl.java:327)
at java.base/java.net.Socket.connect(Socket.java:751)
at
org.apache.hc.client5.http.impl.io.DefaultHttpClientConnectionOperator.connect(DefaultHttpClientConnectionOperator.java:216)
at
org.apache.hc.client5.http.impl.io.PoolingHttpClientConnectionManager.connect(PoolingHttpClientConnectionManager.java:490)
at
org.apache.hc.client5.http.impl.classic.InternalExecRuntime.connectEndpoint(InternalExecRuntime.java:164)
at
org.apache.hc.client5.http.impl.classic.InternalExecRuntime.connectEndpoint(InternalExecRuntime.java:174)
at
org.apache.hc.client5.http.impl.classic.ConnectExec.execute(ConnectExec.java:144)
at
org.apache.hc.client5.http.impl.classic.ExecChainElement.execute(ExecChainElement.java:51)
at
org.apache.hc.client5.http.impl.classic.ProtocolExec.execute(ProtocolExec.java:192)
at
org.apache.hc.client5.http.impl.classic.ExecChainElement.execute(ExecChainElement.java:51)
at
org.apache.hc.client5.http.impl.classic.ContentCompressionExec.execute(ContentCompressionExec.java:150)
at
org.apache.hc.client5.http.impl.classic.ExecChainElement.execute(ExecChainElement.java:51)
at
org.apache.hc.client5.http.impl.classic.HttpRequestRetryExec.execute(HttpRequestRetryExec.java:113)
at
org.apache.hc.client5.http.impl.classic.ExecChainElement.execute(ExecChainElement.java:51)
at
org.apache.hc.client5.http.impl.classic.InternalHttpClient.doExecute(InternalHttpClient.java:174)
at
org.apache.hc.client5.http.impl.classic.CloseableHttpClient.execute(CloseableHttpClient.java:87)
at
org.apache.hc.client5.http.impl.classic.CloseableHttpClient.execute(CloseableHttpClient.java:55)
at
org.apache.hc.client5.http.classic.HttpClient.executeOpen(HttpClient.java:183)
at
org.apache.camel.component.http.HttpProducer.executeMethod(HttpProducer.java:491)
at
org.apache.camel.component.http.HttpProducer.process(HttpProducer.java:247)
at
org.apache.camel.support.AsyncProcessorConverterHelper$ProcessorToAsyncProcessorBridge.process(AsyncProcessorConverterHelper.java:65)
at
org.apache.camel.impl.engine.SharedCamelInternalProcessor.processNonTransacted(SharedCamelInternalProcessor.java:156)
at
org.apache.camel.impl.engine.SharedCamelInternalProcessor.process
[jira] [Updated] (CAMEL-21583) Fix issue related to flaky Jetty tests "Exception occurred during execution on the exchange: Exchange[]"
[
https://issues.apache.org/jira/browse/CAMEL-21583?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Aurélien Pupier updated CAMEL-21583:
Description:
with the last 5 builds on CI, there was at least one Jetty tests failing with
this kind of error:
{noformat}
org.apache.camel.CamelExecutionException: Exception occurred during execution
on the exchange: Exchange[]
at
org.apache.camel.CamelExecutionException.wrapCamelExecutionException(CamelExecutionException.java:45)
at
org.apache.camel.support.ExchangeHelper.extractResultBody(ExchangeHelper.java:698)
at
org.apache.camel.impl.engine.DefaultProducerTemplate.extractResultBody(DefaultProducerTemplate.java:591)
at
org.apache.camel.impl.engine.DefaultProducerTemplate.extractResultBody(DefaultProducerTemplate.java:587)
at
org.apache.camel.impl.engine.DefaultProducerTemplate.sendBodyAndHeader(DefaultProducerTemplate.java:221)
at
org.apache.camel.impl.engine.DefaultProducerTemplate.sendBodyAndHeader(DefaultProducerTemplate.java:213)
at
org.apache.camel.component.jetty.HttpsRouteTest.invokeHttpEndpoint(HttpsRouteTest.java:175)
at
org.apache.camel.component.jetty.HttpsRouteTest.testEndpoint(HttpsRouteTest.java:121)
at java.base/java.lang.reflect.Method.invoke(Method.java:580)
at
java.base/java.util.concurrent.ForkJoinTask.doExec(ForkJoinTask.java:387)
at
java.base/java.util.concurrent.ForkJoinPool$WorkQueue.topLevelExec(ForkJoinPool.java:1312)
at
java.base/java.util.concurrent.ForkJoinPool.scan(ForkJoinPool.java:1843)
at
java.base/java.util.concurrent.ForkJoinPool.runWorker(ForkJoinPool.java:1808)
at
java.base/java.util.concurrent.ForkJoinWorkerThread.run(ForkJoinWorkerThread.java:188)
Caused by: org.apache.hc.client5.http.HttpHostConnectException: Connect to
https://localhost:36391 [localhost/127.0.0.1, localhost/127.0.1.1] failed:
Connection refused
at java.base/sun.nio.ch.Net.pollConnect(Native Method)
at java.base/sun.nio.ch.Net.pollConnectNow(Net.java:682)
at
java.base/sun.nio.ch.NioSocketImpl.timedFinishConnect(NioSocketImpl.java:542)
at java.base/sun.nio.ch.NioSocketImpl.connect(NioSocketImpl.java:592)
at java.base/java.net.SocksSocketImpl.connect(SocksSocketImpl.java:327)
at java.base/java.net.Socket.connect(Socket.java:751)
at
org.apache.hc.client5.http.impl.io.DefaultHttpClientConnectionOperator.connect(DefaultHttpClientConnectionOperator.java:216)
at
org.apache.hc.client5.http.impl.io.PoolingHttpClientConnectionManager.connect(PoolingHttpClientConnectionManager.java:490)
at
org.apache.hc.client5.http.impl.classic.InternalExecRuntime.connectEndpoint(InternalExecRuntime.java:164)
at
org.apache.hc.client5.http.impl.classic.InternalExecRuntime.connectEndpoint(InternalExecRuntime.java:174)
at
org.apache.hc.client5.http.impl.classic.ConnectExec.execute(ConnectExec.java:144)
at
org.apache.hc.client5.http.impl.classic.ExecChainElement.execute(ExecChainElement.java:51)
at
org.apache.hc.client5.http.impl.classic.ProtocolExec.execute(ProtocolExec.java:192)
at
org.apache.hc.client5.http.impl.classic.ExecChainElement.execute(ExecChainElement.java:51)
at
org.apache.hc.client5.http.impl.classic.ContentCompressionExec.execute(ContentCompressionExec.java:150)
at
org.apache.hc.client5.http.impl.classic.ExecChainElement.execute(ExecChainElement.java:51)
at
org.apache.hc.client5.http.impl.classic.HttpRequestRetryExec.execute(HttpRequestRetryExec.java:113)
at
org.apache.hc.client5.http.impl.classic.ExecChainElement.execute(ExecChainElement.java:51)
at
org.apache.hc.client5.http.impl.classic.InternalHttpClient.doExecute(InternalHttpClient.java:174)
at
org.apache.hc.client5.http.impl.classic.CloseableHttpClient.execute(CloseableHttpClient.java:87)
at
org.apache.hc.client5.http.impl.classic.CloseableHttpClient.execute(CloseableHttpClient.java:55)
at
org.apache.hc.client5.http.classic.HttpClient.executeOpen(HttpClient.java:183)
at
org.apache.camel.component.http.HttpProducer.executeMethod(HttpProducer.java:491)
at
org.apache.camel.component.http.HttpProducer.process(HttpProducer.java:247)
at
org.apache.camel.support.AsyncProcessorConverterHelper$ProcessorToAsyncProcessorBridge.process(AsyncProcessorConverterHelper.java:65)
at
org.apache.camel.impl.engine.SharedCamelInternalProcessor.processNonTransacted(SharedCamelInternalProcessor.java:156)
at
org.apache.camel.impl.engine.SharedCamelInternalProcessor.process(SharedCamelInternalProcessor.java:133)
at
org.apache.camel.impl.engine.SharedCamelInternalProcessor$1.process(SharedCamelInternalProcessor.java:89)
at
org.apache.camel.impl.engine.DefaultAsyncProcessorAwaitManager.process(Defaul
[jira] [Work started] (CAMEL-21560) Create a HugginFace Embedding Model builder acting as Java Bean for a Kamelet
[ https://issues.apache.org/jira/browse/CAMEL-21560?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on CAMEL-21560 started by Zineb Bendhiba. -- > Create a HugginFace Embedding Model builder acting as Java Bean for a Kamelet > - > > Key: CAMEL-21560 > URL: https://issues.apache.org/jira/browse/CAMEL-21560 > Project: Camel > Issue Type: New Feature > Components: camel-kamelet >Reporter: Zineb Bendhiba >Assignee: Zineb Bendhiba >Priority: Major > > Create a HugginFace Embedding Model builder acting as Java Bean for a Kamelet. > > Details : > * Main issue : [https://github.com/apache/camel-kamelets/issues/2247] > * Specific issue: [https://github.com/apache/camel-kamelets/issues/2323] -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (CAMEL-21560) Create a HugginFace Embedding Model builder acting as Java Bean for a Kamelet
[ https://issues.apache.org/jira/browse/CAMEL-21560?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zineb Bendhiba updated CAMEL-21560: --- Fix Version/s: 4.10.0 > Create a HugginFace Embedding Model builder acting as Java Bean for a Kamelet > - > > Key: CAMEL-21560 > URL: https://issues.apache.org/jira/browse/CAMEL-21560 > Project: Camel > Issue Type: New Feature > Components: camel-kamelet >Reporter: Zineb Bendhiba >Assignee: Zineb Bendhiba >Priority: Major > Fix For: 4.10.0 > > > Create a HugginFace Embedding Model builder acting as Java Bean for a Kamelet. > > Details : > * Main issue : [https://github.com/apache/camel-kamelets/issues/2247] > * Specific issue: [https://github.com/apache/camel-kamelets/issues/2323] -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (CAMEL-21584) Camel 4.8.x build is failing on CI for camel-kotlin-api module
Aurélien Pupier created CAMEL-21584:
---
Summary: Camel 4.8.x build is failing on CI for camel-kotlin-api
module
Key: CAMEL-21584
URL: https://issues.apache.org/jira/browse/CAMEL-21584
Project: Camel
Issue Type: Bug
Components: camel-kotlin
Affects Versions: 4.8.2
Reporter: Aurélien Pupier
It is failing at least since the 19th December. The last "successful" (without
build error) in the CI history is the 23th September. Last release is the
[4.8.2 on 1st
December|[https://github.com/apache/camel/releases/tag/camel-4.8.2]] so I guess
it broke between the 1st and 19th December
{noformat}
[INFO] --- kotlin:1.9.24:compile (compile) @ camel-kotlin-api ---
[WARNING] Source root doesn't exist:
/home/jenkins/712657a4/workspace/_Core_Build_and_test_camel-4.8.x/dsl/camel-kotlin-api/src/main/java
[WARNING] Source root doesn't exist:
/home/jenkins/712657a4/workspace/_Core_Build_and_test_camel-4.8.x/dsl/camel-kotlin-api/src/generated/java
[WARNING] Using experimental Kotlin incremental compilation
script returned exit code 143 {noformat}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (CAMEL-21584) Camel 4.8.x build is failing on CI for camel-kotlin-api module
[
https://issues.apache.org/jira/browse/CAMEL-21584?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Aurélien Pupier updated CAMEL-21584:
Fix Version/s: 4.8.3
> Camel 4.8.x build is failing on CI for camel-kotlin-api module
> --
>
> Key: CAMEL-21584
> URL: https://issues.apache.org/jira/browse/CAMEL-21584
> Project: Camel
> Issue Type: Bug
> Components: camel-kotlin
>Affects Versions: 4.8.2
>Reporter: Aurélien Pupier
>Priority: Major
> Fix For: 4.8.3
>
>
> It is failing at least since the 19th December. The last "successful"
> (without build error) in the CI history is the 23th September. Last release
> is the [4.8.2 on 1st
> December|https://github.com/apache/camel/releases/tag/camel-4.8.2] so I guess
> it broke between the 1st and 19th December
> {noformat}
> [INFO] --- kotlin:1.9.24:compile (compile) @ camel-kotlin-api ---
> [WARNING] Source root doesn't exist:
> /home/jenkins/712657a4/workspace/_Core_Build_and_test_camel-4.8.x/dsl/camel-kotlin-api/src/main/java
> [WARNING] Source root doesn't exist:
> /home/jenkins/712657a4/workspace/_Core_Build_and_test_camel-4.8.x/dsl/camel-kotlin-api/src/generated/java
> [WARNING] Using experimental Kotlin incremental compilation
> script returned exit code 143 {noformat}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (CAMEL-21584) Camel 4.8.x build is failing on CI for camel-kotlin-api module
[
https://issues.apache.org/jira/browse/CAMEL-21584?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Aurélien Pupier updated CAMEL-21584:
Description:
It is failing at least since the 19th December. The last "successful" (without
build error) in the CI history is the 23th September. Last release is the
[4.8.2 on 1st
December|https://github.com/apache/camel/releases/tag/camel-4.8.2] so I guess
it broke between the 1st and 19th December
{noformat}
[INFO] --- kotlin:1.9.24:compile (compile) @ camel-kotlin-api ---
[WARNING] Source root doesn't exist:
/home/jenkins/712657a4/workspace/_Core_Build_and_test_camel-4.8.x/dsl/camel-kotlin-api/src/main/java
[WARNING] Source root doesn't exist:
/home/jenkins/712657a4/workspace/_Core_Build_and_test_camel-4.8.x/dsl/camel-kotlin-api/src/generated/java
[WARNING] Using experimental Kotlin incremental compilation
script returned exit code 143 {noformat}
was:
It is failing at least since the 19th December. The last "successful" (without
build error) in the CI history is the 23th September. Last release is the
[4.8.2 on 1st
December|[https://github.com/apache/camel/releases/tag/camel-4.8.2]] so I guess
it broke between the 1st and 19th December
{noformat}
[INFO] --- kotlin:1.9.24:compile (compile) @ camel-kotlin-api ---
[WARNING] Source root doesn't exist:
/home/jenkins/712657a4/workspace/_Core_Build_and_test_camel-4.8.x/dsl/camel-kotlin-api/src/main/java
[WARNING] Source root doesn't exist:
/home/jenkins/712657a4/workspace/_Core_Build_and_test_camel-4.8.x/dsl/camel-kotlin-api/src/generated/java
[WARNING] Using experimental Kotlin incremental compilation
script returned exit code 143 {noformat}
> Camel 4.8.x build is failing on CI for camel-kotlin-api module
> --
>
> Key: CAMEL-21584
> URL: https://issues.apache.org/jira/browse/CAMEL-21584
> Project: Camel
> Issue Type: Bug
> Components: camel-kotlin
>Affects Versions: 4.8.2
>Reporter: Aurélien Pupier
>Priority: Major
>
> It is failing at least since the 19th December. The last "successful"
> (without build error) in the CI history is the 23th September. Last release
> is the [4.8.2 on 1st
> December|https://github.com/apache/camel/releases/tag/camel-4.8.2] so I guess
> it broke between the 1st and 19th December
> {noformat}
> [INFO] --- kotlin:1.9.24:compile (compile) @ camel-kotlin-api ---
> [WARNING] Source root doesn't exist:
> /home/jenkins/712657a4/workspace/_Core_Build_and_test_camel-4.8.x/dsl/camel-kotlin-api/src/main/java
> [WARNING] Source root doesn't exist:
> /home/jenkins/712657a4/workspace/_Core_Build_and_test_camel-4.8.x/dsl/camel-kotlin-api/src/generated/java
> [WARNING] Using experimental Kotlin incremental compilation
> script returned exit code 143 {noformat}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Resolved] (CAMEL-21580) Potential ConcurrentModificationException in MessageSupport.copyFromWithNewBody(MessageSupport.java:226)
[
https://issues.apache.org/jira/browse/CAMEL-21580?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen resolved CAMEL-21580.
-
Resolution: Fixed
> Potential ConcurrentModificationException in
> MessageSupport.copyFromWithNewBody(MessageSupport.java:226)
>
>
> Key: CAMEL-21580
> URL: https://issues.apache.org/jira/browse/CAMEL-21580
> Project: Camel
> Issue Type: Bug
> Components: camel-core
>Affects Versions: 4.9.0
>Reporter: Aurélien Pupier
>Assignee: Claus Ibsen
>Priority: Minor
> Fix For: 4.10.0
>
>
> {noformat}
> org.apache.camel.CamelExecutionException: Exception occurred during execution
> on the exchange: Exchange[]
> at
> org.apache.camel.CamelExecutionException.wrapCamelExecutionException(CamelExecutionException.java:45)
> at
> org.apache.camel.support.ExchangeHelper.extractResultBody(ExchangeHelper.java:698)
> at
> org.apache.camel.impl.engine.DefaultProducerTemplate.extractResultBody(DefaultProducerTemplate.java:591)
> at
> org.apache.camel.impl.engine.DefaultProducerTemplate.extractResultBody(DefaultProducerTemplate.java:587)
> at
> org.apache.camel.impl.engine.DefaultProducerTemplate.requestBody(DefaultProducerTemplate.java:414)
> at
> org.apache.camel.component.jms.issues.JmsInOutIssueTest.testInOutTwoTimes(JmsInOutIssueTest.java:57)
> at java.base/java.lang.reflect.Method.invoke(Method.java:569)
> at
> java.base/java.util.concurrent.ForkJoinTask.doExec(ForkJoinTask.java:373)
> at
> java.base/java.util.concurrent.ForkJoinPool$WorkQueue.topLevelExec(ForkJoinPool.java:1182)
> at
> java.base/java.util.concurrent.ForkJoinPool.scan(ForkJoinPool.java:1655)
> at
> java.base/java.util.concurrent.ForkJoinPool.runWorker(ForkJoinPool.java:1622)
> at
> java.base/java.util.concurrent.ForkJoinWorkerThread.run(ForkJoinWorkerThread.java:165)
> Caused by: java.util.ConcurrentModificationException
> at
> java.base/java.util.TreeMap$PrivateEntryIterator.nextEntry(TreeMap.java:1486)
> at java.base/java.util.TreeMap$EntryIterator.next(TreeMap.java:1522)
> at java.base/java.util.TreeMap$EntryIterator.next(TreeMap.java:1517)
> at java.base/java.util.TreeMap.buildFromSorted(TreeMap.java:2879)
> at java.base/java.util.TreeMap.buildFromSorted(TreeMap.java:2871)
> at java.base/java.util.TreeMap.buildFromSorted(TreeMap.java:2871)
> at java.base/java.util.TreeMap.buildFromSorted(TreeMap.java:2871)
> at java.base/java.util.TreeMap.buildFromSorted(TreeMap.java:2828)
> at java.base/java.util.TreeMap.putAll(TreeMap.java:319)
> at
> org.apache.camel.support.MessageSupport.copyFromWithNewBody(MessageSupport.java:226)
> at
> org.apache.camel.support.processor.ConvertBodyProcessor.process(ConvertBodyProcessor.java:129)
> at
> org.apache.camel.impl.engine.SharedCamelInternalProcessor$InternalCallback.done(SharedCamelInternalProcessor.java:216)
> at
> org.apache.camel.component.jms.reply.ReplyManagerSupport.processReply(ReplyManagerSupport.java:221)
> at
> org.apache.camel.component.jms.reply.TemporaryQueueReplyHandler.onReply(TemporaryQueueReplyHandler.java:54)
> at
> org.apache.camel.component.jms.reply.TemporaryQueueReplyManager.handleReplyMessage(TemporaryQueueReplyManager.java:85)
> at
> org.apache.camel.component.jms.reply.ReplyManagerSupport.onMessage(ReplyManagerSupport.java:164)
> at
> org.springframework.jms.listener.AbstractMessageListenerContainer.doInvokeListener(AbstractMessageListenerContainer.java:790)
> at
> org.springframework.jms.listener.AbstractMessageListenerContainer.invokeListener(AbstractMessageListenerContainer.java:747)
> at
> org.springframework.jms.listener.AbstractMessageListenerContainer.doExecuteListener(AbstractMessageListenerContainer.java:725)
> at
> org.springframework.jms.listener.AbstractPollingMessageListenerContainer.doReceiveAndExecute(AbstractPollingMessageListenerContainer.java:333)
> at
> org.springframework.jms.listener.AbstractPollingMessageListenerContainer.receiveAndExecute(AbstractPollingMessageListenerContainer.java:270)
> at
> org.springframework.jms.listener.DefaultMessageListenerContainer$AsyncMessageListenerInvoker.invokeListener(DefaultMessageListenerContainer.java:1420)
> at
> org.springframework.jms.listener.DefaultMessageListenerContainer$AsyncMessageListenerInvoker.executeOngoingLoop(DefaultMessageListenerContainer.java:1410)
> at
> org.springframework.jms.listener.DefaultMessageListenerContainer$AsyncMessageListenerInvoker.run(DefaultMessageListenerContainer.java:1287)
> at java.base/java.lang.Thread.run(Thread.java:840)
> {noformat}
[jira] [Updated] (CAMEL-21584) Camel 4.8.x build is failing on CI for camel-kotlin-api module
[
https://issues.apache.org/jira/browse/CAMEL-21584?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen updated CAMEL-21584:
Affects Version/s: (was: 4.8.2)
> Camel 4.8.x build is failing on CI for camel-kotlin-api module
> --
>
> Key: CAMEL-21584
> URL: https://issues.apache.org/jira/browse/CAMEL-21584
> Project: Camel
> Issue Type: Task
> Components: camel-kotlin
>Reporter: Aurélien Pupier
>Priority: Major
> Fix For: 4.8.3
>
>
> It is failing at least since the 19th December. The last "successful"
> (without build error) in the CI history is the 23th September. Last release
> is the [4.8.2 on 1st
> December|https://github.com/apache/camel/releases/tag/camel-4.8.2] so I guess
> it broke between the 1st and 19th December
> {noformat}
> [INFO] --- kotlin:1.9.24:compile (compile) @ camel-kotlin-api ---
> [WARNING] Source root doesn't exist:
> /home/jenkins/712657a4/workspace/_Core_Build_and_test_camel-4.8.x/dsl/camel-kotlin-api/src/main/java
> [WARNING] Source root doesn't exist:
> /home/jenkins/712657a4/workspace/_Core_Build_and_test_camel-4.8.x/dsl/camel-kotlin-api/src/generated/java
> [WARNING] Using experimental Kotlin incremental compilation
> script returned exit code 143 {noformat}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (CAMEL-21584) Camel 4.8.x build is failing on CI for camel-kotlin-api module
[
https://issues.apache.org/jira/browse/CAMEL-21584?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen updated CAMEL-21584:
Issue Type: Task (was: Bug)
> Camel 4.8.x build is failing on CI for camel-kotlin-api module
> --
>
> Key: CAMEL-21584
> URL: https://issues.apache.org/jira/browse/CAMEL-21584
> Project: Camel
> Issue Type: Task
> Components: camel-kotlin
>Affects Versions: 4.8.2
>Reporter: Aurélien Pupier
>Priority: Major
> Fix For: 4.8.3
>
>
> It is failing at least since the 19th December. The last "successful"
> (without build error) in the CI history is the 23th September. Last release
> is the [4.8.2 on 1st
> December|https://github.com/apache/camel/releases/tag/camel-4.8.2] so I guess
> it broke between the 1st and 19th December
> {noformat}
> [INFO] --- kotlin:1.9.24:compile (compile) @ camel-kotlin-api ---
> [WARNING] Source root doesn't exist:
> /home/jenkins/712657a4/workspace/_Core_Build_and_test_camel-4.8.x/dsl/camel-kotlin-api/src/main/java
> [WARNING] Source root doesn't exist:
> /home/jenkins/712657a4/workspace/_Core_Build_and_test_camel-4.8.x/dsl/camel-kotlin-api/src/generated/java
> [WARNING] Using experimental Kotlin incremental compilation
> script returned exit code 143 {noformat}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (CAMEL-21584) Camel 4.8.x build is failing on CI for camel-kotlin-api module
[
https://issues.apache.org/jira/browse/CAMEL-21584?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen updated CAMEL-21584:
Priority: Minor (was: Major)
> Camel 4.8.x build is failing on CI for camel-kotlin-api module
> --
>
> Key: CAMEL-21584
> URL: https://issues.apache.org/jira/browse/CAMEL-21584
> Project: Camel
> Issue Type: Task
> Components: camel-kotlin
>Reporter: Aurélien Pupier
>Priority: Minor
> Fix For: 4.8.3
>
>
> It is failing at least since the 19th December. The last "successful"
> (without build error) in the CI history is the 23th September. Last release
> is the [4.8.2 on 1st
> December|https://github.com/apache/camel/releases/tag/camel-4.8.2] so I guess
> it broke between the 1st and 19th December
> {noformat}
> [INFO] --- kotlin:1.9.24:compile (compile) @ camel-kotlin-api ---
> [WARNING] Source root doesn't exist:
> /home/jenkins/712657a4/workspace/_Core_Build_and_test_camel-4.8.x/dsl/camel-kotlin-api/src/main/java
> [WARNING] Source root doesn't exist:
> /home/jenkins/712657a4/workspace/_Core_Build_and_test_camel-4.8.x/dsl/camel-kotlin-api/src/generated/java
> [WARNING] Using experimental Kotlin incremental compilation
> script returned exit code 143 {noformat}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (CAMEL-21584) Camel 4.8.x build is failing on CI for camel-kotlin-api module
[
https://issues.apache.org/jira/browse/CAMEL-21584?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17909523#comment-17909523
]
Claus Ibsen commented on CAMEL-21584:
-
Works locally and its deprecated module that is removed in 4.9.
The 4.8.2 release is not affected.
> Camel 4.8.x build is failing on CI for camel-kotlin-api module
> --
>
> Key: CAMEL-21584
> URL: https://issues.apache.org/jira/browse/CAMEL-21584
> Project: Camel
> Issue Type: Task
> Components: camel-kotlin
>Reporter: Aurélien Pupier
>Priority: Minor
> Fix For: 4.8.3
>
>
> It is failing at least since the 19th December. The last "successful"
> (without build error) in the CI history is the 23th September. Last release
> is the [4.8.2 on 1st
> December|https://github.com/apache/camel/releases/tag/camel-4.8.2] so I guess
> it broke between the 1st and 19th December
> {noformat}
> [INFO] --- kotlin:1.9.24:compile (compile) @ camel-kotlin-api ---
> [WARNING] Source root doesn't exist:
> /home/jenkins/712657a4/workspace/_Core_Build_and_test_camel-4.8.x/dsl/camel-kotlin-api/src/main/java
> [WARNING] Source root doesn't exist:
> /home/jenkins/712657a4/workspace/_Core_Build_and_test_camel-4.8.x/dsl/camel-kotlin-api/src/generated/java
> [WARNING] Using experimental Kotlin incremental compilation
> script returned exit code 143 {noformat}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (CAMEL-21585) camel-test-infra: select platform-specific containers dynamically
[
https://issues.apache.org/jira/browse/CAMEL-21585?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Otavio Rodolfo Piske updated CAMEL-21585:
-
Component/s: camel-test-infra
> camel-test-infra: select platform-specific containers dynamically
> -
>
> Key: CAMEL-21585
> URL: https://issues.apache.org/jira/browse/CAMEL-21585
> Project: Camel
> Issue Type: Task
> Components: camel-test-infra
>Reporter: Otavio Rodolfo Piske
>Priority: Major
>
> Ref: [https://github.com/apache/camel/pull/16688]
>
> We should consolidate this logic in the {color:#00}LocalPropertyResolver
> so we don't end up with multiple magic strings and duplicated code all over
> the place.
> {color}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (CAMEL-21585) camel-test-infra: select platform-specific containers dynamically
[
https://issues.apache.org/jira/browse/CAMEL-21585?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Otavio Rodolfo Piske updated CAMEL-21585:
-
Labels: help-wanted (was: )
> camel-test-infra: select platform-specific containers dynamically
> -
>
> Key: CAMEL-21585
> URL: https://issues.apache.org/jira/browse/CAMEL-21585
> Project: Camel
> Issue Type: Task
> Components: camel-test-infra
>Reporter: Otavio Rodolfo Piske
>Priority: Major
> Labels: help-wanted
>
> Ref: [https://github.com/apache/camel/pull/16688]
>
> We should consolidate this logic in the {color:#00}LocalPropertyResolver
> so we don't end up with multiple magic strings and duplicated code all over
> the place.
> {color}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Created] (CAMEL-21585) camel-test-infra: select platform-specific containers dynamically
Otavio Rodolfo Piske created CAMEL-21585:
Summary: camel-test-infra: select platform-specific containers
dynamically
Key: CAMEL-21585
URL: https://issues.apache.org/jira/browse/CAMEL-21585
Project: Camel
Issue Type: Task
Reporter: Otavio Rodolfo Piske
Ref: [https://github.com/apache/camel/pull/16688]
We should consolidate this logic in the {color:#00}LocalPropertyResolver so
we don't end up with multiple magic strings and duplicated code all over the
place.
{color}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (CAMEL-21585) camel-test-infra: select platform-specific containers dynamically
[
https://issues.apache.org/jira/browse/CAMEL-21585?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Otavio Rodolfo Piske updated CAMEL-21585:
-
Estimated Complexity: Novice (was: Unknown)
> camel-test-infra: select platform-specific containers dynamically
> -
>
> Key: CAMEL-21585
> URL: https://issues.apache.org/jira/browse/CAMEL-21585
> Project: Camel
> Issue Type: Task
> Components: camel-test-infra
>Reporter: Otavio Rodolfo Piske
>Priority: Major
> Labels: help-wanted
>
> Ref: [https://github.com/apache/camel/pull/16688]
>
> We should consolidate this logic in the {color:#00}LocalPropertyResolver
> so we don't end up with multiple magic strings and duplicated code all over
> the place.
> {color}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Assigned] (CAMEL-21585) camel-test-infra: select platform-specific containers dynamically
[
https://issues.apache.org/jira/browse/CAMEL-21585?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Otavio Rodolfo Piske reassigned CAMEL-21585:
Assignee: Otavio Rodolfo Piske
> camel-test-infra: select platform-specific containers dynamically
> -
>
> Key: CAMEL-21585
> URL: https://issues.apache.org/jira/browse/CAMEL-21585
> Project: Camel
> Issue Type: Task
> Components: camel-test-infra
>Reporter: Otavio Rodolfo Piske
>Assignee: Otavio Rodolfo Piske
>Priority: Major
> Labels: help-wanted
>
> Ref: [https://github.com/apache/camel/pull/16688]
>
> We should consolidate this logic in the {color:#00}LocalPropertyResolver
> so we don't end up with multiple magic strings and duplicated code all over
> the place.
> {color}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (CAMEL-21352) camel-smb - Based on camel-file to have many more features
[ https://issues.apache.org/jira/browse/CAMEL-21352?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen updated CAMEL-21352: Fix Version/s: 4.10.0 (was: 4.x) > camel-smb - Based on camel-file to have many more features > -- > > Key: CAMEL-21352 > URL: https://issues.apache.org/jira/browse/CAMEL-21352 > Project: Camel > Issue Type: Improvement > Components: camel-smb >Reporter: Claus Ibsen >Assignee: Jono Morris >Priority: Major > Fix For: 4.10.0 > > > Maybe we could let camel-smb extend camel-file (like camel-ftp / camel-jsch) > and then have a lot more file related features out of the box. > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (CAMEL-21582) PropertiesComponent requires LoadablePropertiesSource which was removed by CAMEL-21480 and CAMEL-21484
[ https://issues.apache.org/jira/browse/CAMEL-21582?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen updated CAMEL-21582: Component/s: camel-microprofile-config (was: camel-core) > PropertiesComponent requires LoadablePropertiesSource which was removed by > CAMEL-21480 and CAMEL-21484 > -- > > Key: CAMEL-21582 > URL: https://issues.apache.org/jira/browse/CAMEL-21582 > Project: Camel > Issue Type: Improvement > Components: camel-microprofile-config >Affects Versions: 4.10.0 >Reporter: Jiri Ondrusek >Priority: Major > Fix For: 4.10.0 > > > Here are 2 recent fixes CAMEL-21480 and CAMEL-21480, which made properties > loaded by microprofile as not loadable. > Unfortunately some parts of PropertiesComponent requires > `LoadablePropertiesSource` (i.e. this > [code|https://github.com/apache/camel/blob/main/core/camel-base/src/main/java/org/apache/camel/component/properties/PropertiesComponent.java#L287]). > The issue can be simulated by running camel-quarkus test > [CamelAutowiredDisabledTest|https://github.com/apache/camel-quarkus/blob/camel-main/extensions-core/core/deployment/src/test/java/org/apache/camel/quarkus/core/deployment/main/CamelAutowiredDisabledTest.java] > from branch `camel-main`. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (CAMEL-21582) PropertiesComponent requires LoadablePropertiesSource which was removed by CAMEL-21480 and CAMEL-21484
[ https://issues.apache.org/jira/browse/CAMEL-21582?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen updated CAMEL-21582: Fix Version/s: 4.10.0 > PropertiesComponent requires LoadablePropertiesSource which was removed by > CAMEL-21480 and CAMEL-21484 > -- > > Key: CAMEL-21582 > URL: https://issues.apache.org/jira/browse/CAMEL-21582 > Project: Camel > Issue Type: Improvement > Components: camel-core >Affects Versions: 4.10.0 >Reporter: Jiri Ondrusek >Priority: Major > Fix For: 4.10.0 > > > Here are 2 recent fixes CAMEL-21480 and CAMEL-21480, which made properties > loaded by microprofile as not loadable. > Unfortunately some parts of PropertiesComponent requires > `LoadablePropertiesSource` (i.e. this > [code|https://github.com/apache/camel/blob/main/core/camel-base/src/main/java/org/apache/camel/component/properties/PropertiesComponent.java#L287]). > The issue can be simulated by running camel-quarkus test > [CamelAutowiredDisabledTest|https://github.com/apache/camel-quarkus/blob/camel-main/extensions-core/core/deployment/src/test/java/org/apache/camel/quarkus/core/deployment/main/CamelAutowiredDisabledTest.java] > from branch `camel-main`. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (CAMEL-21589) Make manual acknowledgements configurable in Paho-Mqtt5
Rav Brar created CAMEL-21589: Summary: Make manual acknowledgements configurable in Paho-Mqtt5 Key: CAMEL-21589 URL: https://issues.apache.org/jira/browse/CAMEL-21589 Project: Camel Issue Type: New Feature Components: came-core Reporter: Rav Brar When using the Camel MQTT5 Source Kafka Connector, messages are automatically acknowledged, which doesn't ensure they reach their final destination at least once. Enabling manual acknowledgements ensures the connector is able to provide at least once delivery to topics. This new parameter would make it possible for the user to enable manual acknowledgements in the client. By default, the parameter is set to false and messages will be automatically acknowledged. If set to true, the acknowledgement is added in the exchange's completion callback. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (CAMEL-20968) camel-langchain4j: Add RAG option
[ https://issues.apache.org/jira/browse/CAMEL-20968?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zineb Bendhiba resolved CAMEL-20968. Fix Version/s: 4.9.0 (was: 4.x) Resolution: Fixed > camel-langchain4j: Add RAG option > - > > Key: CAMEL-20968 > URL: https://issues.apache.org/jira/browse/CAMEL-20968 > Project: Camel > Issue Type: New Feature > Components: camel-langchain4j >Reporter: Zineb Bendhiba >Assignee: Zineb Bendhiba >Priority: Major > Fix For: 4.9.0 > > > I was thinking of adding an option to enrich the prompt properly with content > retrieved via a custom Camel RAG pipeline > > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (CAMEL-21087) camel-jbang: Kubernetes plugin: Add jolokia/prometheus trait
[ https://issues.apache.org/jira/browse/CAMEL-21087?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen updated CAMEL-21087: Fix Version/s: 4.x > camel-jbang: Kubernetes plugin: Add jolokia/prometheus trait > > > Key: CAMEL-21087 > URL: https://issues.apache.org/jira/browse/CAMEL-21087 > Project: Camel > Issue Type: New Feature > Components: camel-jbang >Reporter: Christoph Deppisch >Priority: Major > Fix For: 4.x > > > The jolokia/prometheus trait seems to be valuable for users. Add them to the > Kubernetes plugin for Camel JBang -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (CAMEL-21121) camel-jbang - Tests should use target folder as tmp to avoid filling up disk space
[ https://issues.apache.org/jira/browse/CAMEL-21121?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen resolved CAMEL-21121. - Resolution: Implemented Assume its fixed/better now > camel-jbang - Tests should use target folder as tmp to avoid filling up disk > space > -- > > Key: CAMEL-21121 > URL: https://issues.apache.org/jira/browse/CAMEL-21121 > Project: Camel > Issue Type: Test > Components: camel-jbang, tests >Reporter: Claus Ibsen >Priority: Minor > Fix For: 4.x > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (CAMEL-21589) Make manual acknowledgements configurable in Paho-Mqtt5
[ https://issues.apache.org/jira/browse/CAMEL-21589?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rav Brar updated CAMEL-21589: - I have a fix for this in the works. Just working on the relevant tests. > Make manual acknowledgements configurable in Paho-Mqtt5 > --- > > Key: CAMEL-21589 > URL: https://issues.apache.org/jira/browse/CAMEL-21589 > Project: Camel > Issue Type: New Feature > Components: came-core >Reporter: Rav Brar >Priority: Major > > When using the Camel MQTT5 Source Kafka Connector, messages are automatically > acknowledged, which doesn't ensure they reach their final destination at > least once. Enabling manual acknowledgements ensures the connector is able to > provide at least once delivery to topics. > This new parameter would make it possible for the user to enable manual > acknowledgements in the client. By default, the parameter is set to false and > messages will be automatically acknowledged. If set to true, the > acknowledgement is added in the exchange's completion callback. > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (CAMEL-21588) Pinecone: configurations exclusive in the headers are not user friendly
Zineb Bendhiba created CAMEL-21588:
--
Summary: Pinecone: configurations exclusive in the headers are not
user friendly
Key: CAMEL-21588
URL: https://issues.apache.org/jira/browse/CAMEL-21588
Project: Camel
Issue Type: Improvement
Components: camel-pinecone
Affects Versions: 4.8.2
Reporter: Zineb Bendhiba
While playing with Camel Pinecone, I realized that some properties are supposed
to be set only by setting headers.
Some of those are kind of mandatory (index name, cloud region...). I was using
a Cloud account.
These are the list headers that I wish they can be set as properties instead
{code:java}
.setHeader(PineconeVectorDb.Headers.INDEX_NAME,
simple("{{pinecone.index-name}}"))
.setHeader(PineconeVectorDb.Headers.COLLECTION_SIMILARITY_METRIC,
constant("cosine"))
.setHeader(PineconeVectorDb.Headers.COLLECTION_DIMENSION, constant(1536))
.setHeader(PineconeVectorDb.Headers.COLLECTION_CLOUD, constant("aws"))
.setHeader(PineconeVectorDb.Headers.COLLECTION_CLOUD_REGION,
simple("{{pinecone.region}}"))
{code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Resolved] (CAMEL-21582) PropertiesComponent requires LoadablePropertiesSource which was removed by CAMEL-21480 and CAMEL-21484
[ https://issues.apache.org/jira/browse/CAMEL-21582?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen resolved CAMEL-21582. - Resolution: Fixed > PropertiesComponent requires LoadablePropertiesSource which was removed by > CAMEL-21480 and CAMEL-21484 > -- > > Key: CAMEL-21582 > URL: https://issues.apache.org/jira/browse/CAMEL-21582 > Project: Camel > Issue Type: Improvement > Components: camel-microprofile-config >Affects Versions: 4.10.0 >Reporter: Jiri Ondrusek >Priority: Major > Fix For: 4.10.0 > > > Here are 2 recent fixes CAMEL-21480 and CAMEL-21480, which made properties > loaded by microprofile as not loadable. > Unfortunately some parts of PropertiesComponent requires > `LoadablePropertiesSource` (i.e. this > [code|https://github.com/apache/camel/blob/main/core/camel-base/src/main/java/org/apache/camel/component/properties/PropertiesComponent.java#L287]). > The issue can be simulated by running camel-quarkus test > [CamelAutowiredDisabledTest|https://github.com/apache/camel-quarkus/blob/camel-main/extensions-core/core/deployment/src/test/java/org/apache/camel/quarkus/core/deployment/main/CamelAutowiredDisabledTest.java] > from branch `camel-main`. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (CAMEL-21582) PropertiesComponent requires LoadablePropertiesSource which was removed by CAMEL-21480 and CAMEL-21484
[ https://issues.apache.org/jira/browse/CAMEL-21582?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen reassigned CAMEL-21582: --- Assignee: Jiri Ondrusek > PropertiesComponent requires LoadablePropertiesSource which was removed by > CAMEL-21480 and CAMEL-21484 > -- > > Key: CAMEL-21582 > URL: https://issues.apache.org/jira/browse/CAMEL-21582 > Project: Camel > Issue Type: Improvement > Components: camel-microprofile-config >Affects Versions: 4.10.0 >Reporter: Jiri Ondrusek >Assignee: Jiri Ondrusek >Priority: Major > Fix For: 4.10.0 > > > Here are 2 recent fixes CAMEL-21480 and CAMEL-21480, which made properties > loaded by microprofile as not loadable. > Unfortunately some parts of PropertiesComponent requires > `LoadablePropertiesSource` (i.e. this > [code|https://github.com/apache/camel/blob/main/core/camel-base/src/main/java/org/apache/camel/component/properties/PropertiesComponent.java#L287]). > The issue can be simulated by running camel-quarkus test > [CamelAutowiredDisabledTest|https://github.com/apache/camel-quarkus/blob/camel-main/extensions-core/core/deployment/src/test/java/org/apache/camel/quarkus/core/deployment/main/CamelAutowiredDisabledTest.java] > from branch `camel-main`. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (CAMEL-21352) camel-smb - Based on camel-file to have many more features
[
https://issues.apache.org/jira/browse/CAMEL-21352?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17909616#comment-17909616
]
Claus Ibsen commented on CAMEL-21352:
-
We should have a streamDownload or some similar name so we can support reading
the file using InputStream directly ( and have some logic that auto-close
stream on UoW done on the exchange)
As today the SmbFile reads the entire content into memory as byte[] and that
does not work great for big files.
@Override
public Object getBody() {
// use operations so smb file can be closed
return operations.getBody(this.getAbsoluteFilePath());
}
> camel-smb - Based on camel-file to have many more features
> --
>
> Key: CAMEL-21352
> URL: https://issues.apache.org/jira/browse/CAMEL-21352
> Project: Camel
> Issue Type: Improvement
> Components: camel-smb
>Reporter: Claus Ibsen
>Assignee: Jono Morris
>Priority: Major
> Fix For: 4.10.0
>
>
> Maybe we could let camel-smb extend camel-file (like camel-ftp / camel-jsch)
> and then have a lot more file related features out of the box.
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (CAMEL-21586) Create a OpenAI Embedding Model builder acting as Java Bean for a Kamelet
[ https://issues.apache.org/jira/browse/CAMEL-21586?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zineb Bendhiba updated CAMEL-21586: --- Description: Create a HugginFace Embedding Model builder acting as Java Bean for a Kamelet. Details : * Main issue : [https://github.com/apache/camel-kamelets/issues/2247] * Specific issue: [https://github.com/apache/camel-kamelets/issues/2323 |https://github.com/apache/camel-kamelets/issues/2324] was: Create a HugginFace Embedding Model builder acting as Java Bean for a Kamelet. Details : * Main issue : [https://github.com/apache/camel-kamelets/issues/2247] * Specific issue: [https://github.com/apache/camel-kamelets/issues/2323] > Create a OpenAI Embedding Model builder acting as Java Bean for a Kamelet > -- > > Key: CAMEL-21586 > URL: https://issues.apache.org/jira/browse/CAMEL-21586 > Project: Camel > Issue Type: New Feature > Components: camel-kamelet >Reporter: Zineb Bendhiba >Assignee: Zineb Bendhiba >Priority: Major > Fix For: 4.10.0 > > > Create a HugginFace Embedding Model builder acting as Java Bean for a Kamelet. > > Details : > * Main issue : [https://github.com/apache/camel-kamelets/issues/2247] > * Specific issue: [https://github.com/apache/camel-kamelets/issues/2323 > |https://github.com/apache/camel-kamelets/issues/2324] -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (CAMEL-20919) Introduce Producer based Health for any SFTPs
[ https://issues.apache.org/jira/browse/CAMEL-20919?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen updated CAMEL-20919: Priority: Minor (was: Major) > Introduce Producer based Health for any SFTPs > - > > Key: CAMEL-20919 > URL: https://issues.apache.org/jira/browse/CAMEL-20919 > Project: Camel > Issue Type: New Feature > Components: camel-sftp, camel-spring-boot > Environment: Camel Springboot > Camel SFTP >Reporter: Adityakrishnan >Priority: Minor > Labels: features > Fix For: 4.x > > Original Estimate: 336h > Remaining Estimate: 336h > > Producer based SFTP Health is not available for regular SFTPs, it is only > accessible by some components (like AWS and Kafka). This has been a need from > some time in work-spaces. > When SFTPs have inconsistent down-times Observability and Monitoring comes > handy for all those who uses Apache Camel. This Producer based Health Check > should also be included in regular SFTPs. > Consumer based and Producer based health check and alerting can prevent an > outage before it occurs. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (CAMEL-21151) Build is failing on os MacOS with multiple tests failing
[
https://issues.apache.org/jira/browse/CAMEL-21151?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17909541#comment-17909541
]
Claus Ibsen commented on CAMEL-21151:
-
Adriano did you look more into this, especially the one about timezone
> Build is failing on os MacOS with multiple tests failing
>
>
> Key: CAMEL-21151
> URL: https://issues.apache.org/jira/browse/CAMEL-21151
> Project: Camel
> Issue Type: Test
> Components: camel-jms, camel-openapi-java, camel-opentelemetry
>Affects Versions: 4.8.0
>Reporter: Adriano Machado
>Priority: Minor
>
> Multiple tests are failing on MacOS using Java 21.0.4 on the main branch.
> {code:java}
> Apache Maven 3.9.9 (8e8579a9e76f7d015ee5ec7bfcdc97d260186937)
> Maven home: /Users/admachad/.sdkman/candidates/maven/current
> Java version: 21.0.4, vendor: Eclipse Adoptium, runtime:
> /Users/admachad/.sdkman/candidates/java/21.0.4-tem
> Default locale: en_US, platform encoding: UTF-8
> OS name: "mac os x", version: "14.6.1", arch: "aarch64", family: "mac" {code}
> For `camel-openapi-java`, it seems that there's a problem with timezones on
> my machine, I'm checking what's happening.
> For `camel-jms`, it is apparently failing due to connection issues to the
> container used in the test.
> For `camel-opentelemetry`, I think the issue is related to CAMEL-19667, which
> [https://github.com/apache/camel/pull/15182] introduced test improvements.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Work started] (CAMEL-21586) Create a OpenAI Embedding Model builder acting as Java Bean for a Kamelet
[ https://issues.apache.org/jira/browse/CAMEL-21586?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on CAMEL-21586 started by Zineb Bendhiba. -- > Create a OpenAI Embedding Model builder acting as Java Bean for a Kamelet > -- > > Key: CAMEL-21586 > URL: https://issues.apache.org/jira/browse/CAMEL-21586 > Project: Camel > Issue Type: New Feature > Components: camel-kamelet >Reporter: Zineb Bendhiba >Assignee: Zineb Bendhiba >Priority: Major > Fix For: 4.10.0 > > > Create a HugginFace Embedding Model builder acting as Java Bean for a Kamelet. > > Details : > * Main issue : [https://github.com/apache/camel-kamelets/issues/2247] > * Specific issue: [https://github.com/apache/camel-kamelets/issues/2323 > |https://github.com/apache/camel-kamelets/issues/2324] -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (CAMEL-20908) camel-debug - Support `pause` of all route exchanges
[
https://issues.apache.org/jira/browse/CAMEL-20908?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen updated CAMEL-20908:
Priority: Minor (was: Major)
> camel-debug - Support `pause` of all route exchanges
>
>
> Key: CAMEL-20908
> URL: https://issues.apache.org/jira/browse/CAMEL-20908
> Project: Camel
> Issue Type: New Feature
> Components: camel-management
>Reporter: Aurélien Pupier
>Priority: Minor
> Fix For: 4.x
>
>
> it would convenient for investigation to be able to pause all current route
> exchange at the nearest point (surely next step) to investigate what is going
> on with the routes.
> It would be convenient to be able to pause all exchanges and also to be able
> to pause for a Route definition or a Camel context.
> Currently, suspend is no more starting new routes but finishes the current
> exchanges. The stop is no more starting the routes and not finishing the
> current exchange.
>
> Technical:
> it would likely be some option you turn on|off to have this behaviour - we
> can debate whether it should be on as default (new) or off (like now). To
> checked that it is not breaking other flow, like in Hawt.io to use the new
> behavior as default.
> {color:#262626}or a parameter on the suspend/stop methods?{color}
> {color:#262626}or create another one, as pause{color}
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (CAMEL-20919) Introduce Producer based Health for any SFTPs
[ https://issues.apache.org/jira/browse/CAMEL-20919?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17909546#comment-17909546 ] Adityakrishnan commented on CAMEL-20919: [~davsclaus] any specific reason it was deprioritized? > Introduce Producer based Health for any SFTPs > - > > Key: CAMEL-20919 > URL: https://issues.apache.org/jira/browse/CAMEL-20919 > Project: Camel > Issue Type: New Feature > Components: camel-sftp, camel-spring-boot > Environment: Camel Springboot > Camel SFTP >Reporter: Adityakrishnan >Priority: Minor > Labels: features > Fix For: 4.x > > Original Estimate: 336h > Remaining Estimate: 336h > > Producer based SFTP Health is not available for regular SFTPs, it is only > accessible by some components (like AWS and Kafka). This has been a need from > some time in work-spaces. > When SFTPs have inconsistent down-times Observability and Monitoring comes > handy for all those who uses Apache Camel. This Producer based Health Check > should also be included in regular SFTPs. > Consumer based and Producer based health check and alerting can prevent an > outage before it occurs. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (CAMEL-20497) camel-quickfix - FIX session reconnect delay
[ https://issues.apache.org/jira/browse/CAMEL-20497?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen resolved CAMEL-20497. - Resolution: Information Provided > camel-quickfix - FIX session reconnect delay > > > Key: CAMEL-20497 > URL: https://issues.apache.org/jira/browse/CAMEL-20497 > Project: Camel > Issue Type: New Feature > Components: camel-quickfix >Affects Versions: 3.20.9 >Reporter: Alexander Anpilov >Priority: Minor > > I have fix-session as "initiator role" created using camel-quickfix component. > When some network troubles happens, session automatically reconnect (sending > 35=A). > But the server requires some timeout (for example 5 sec) before next logon > attempt for destroying previous session. > Is it possible to add some param to camel-quickfix component for reconnect > delay? -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (CAMEL-20497) camel-quickfix - FIX session reconnect delay
[ https://issues.apache.org/jira/browse/CAMEL-20497?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17909552#comment-17909552 ] Claus Ibsen commented on CAMEL-20497: - You configure this in QuickFix itself, see /** * Initiator setting for reconnect interval in seconds. Only valid when * session connection type is "initiator". * * @see quickfix.SessionFactory#SETTING_CONNECTION_TYPE */ String SETTING_RECONNECT_INTERVAL = "ReconnectInterval"; > camel-quickfix - FIX session reconnect delay > > > Key: CAMEL-20497 > URL: https://issues.apache.org/jira/browse/CAMEL-20497 > Project: Camel > Issue Type: New Feature > Components: camel-quickfix >Affects Versions: 3.20.9 >Reporter: Alexander Anpilov >Priority: Minor > > I have fix-session as "initiator role" created using camel-quickfix component. > When some network troubles happens, session automatically reconnect (sending > 35=A). > But the server requires some timeout (for example 5 sec) before next logon > attempt for destroying previous session. > Is it possible to add some param to camel-quickfix component for reconnect > delay? -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (CAMEL-21586) Create a OpenAI Embedding Model builder acting as Java Bean for a Kamelet
Zineb Bendhiba created CAMEL-21586: -- Summary: Create a OpenAI Embedding Model builder acting as Java Bean for a Kamelet Key: CAMEL-21586 URL: https://issues.apache.org/jira/browse/CAMEL-21586 Project: Camel Issue Type: New Feature Components: camel-kamelet Reporter: Zineb Bendhiba Assignee: Zineb Bendhiba Fix For: 4.10.0 Create a HugginFace Embedding Model builder acting as Java Bean for a Kamelet. Details : * Main issue : [https://github.com/apache/camel-kamelets/issues/2247] * Specific issue: [https://github.com/apache/camel-kamelets/issues/2323] -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (CAMEL-21352) camel-smb - Based on camel-file to have many more features
[ https://issues.apache.org/jira/browse/CAMEL-21352?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17909648#comment-17909648 ] Claus Ibsen commented on CAMEL-21352: - TODO: More constants in SmbConstants (see ftp component) TODO: streamDownload (see ftp component) TODO: local work dir (see ftp component) > camel-smb - Based on camel-file to have many more features > -- > > Key: CAMEL-21352 > URL: https://issues.apache.org/jira/browse/CAMEL-21352 > Project: Camel > Issue Type: Improvement > Components: camel-smb >Reporter: Claus Ibsen >Assignee: Jono Morris >Priority: Major > Fix For: 4.10.0 > > > Maybe we could let camel-smb extend camel-file (like camel-ftp / camel-jsch) > and then have a lot more file related features out of the box. > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (CAMEL-21576) camel-test-infra: container pulling adjustments
[ https://issues.apache.org/jira/browse/CAMEL-21576?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Otavio Rodolfo Piske updated CAMEL-21576: - Description: Reduce relying on docker hub: * Pull limits/restrictions cause tests to fail * May incur in costs when running them on corporate networks as it may account for corporate usage was:This is a work in progress and I'll share more details later after I finish the investigation and proposal. > camel-test-infra: container pulling adjustments > --- > > Key: CAMEL-21576 > URL: https://issues.apache.org/jira/browse/CAMEL-21576 > Project: Camel > Issue Type: Task > Components: camel-test-infra >Affects Versions: 4.4.4, 4.8.2, 4.10.0 >Reporter: Otavio Rodolfo Piske >Assignee: Otavio Rodolfo Piske >Priority: Major > Fix For: 4.4.5, 4.8.3, 4.10.0 > > > Reduce relying on docker hub: > * Pull limits/restrictions cause tests to fail > * May incur in costs when running them on corporate networks as it may > account for corporate usage > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
