[jira] [Created] (CAMEL-18839) upgrade to kafka 3.3.x
Claus Ibsen created CAMEL-18839: --- Summary: upgrade to kafka 3.3.x Key: CAMEL-18839 URL: https://issues.apache.org/jira/browse/CAMEL-18839 Project: Camel Issue Type: Dependency upgrade Components: camel-kafka Reporter: Claus Ibsen Fix For: 3.21.0 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (CAMEL-18838) upgrade to debezium 2.1.x
Claus Ibsen created CAMEL-18838: --- Summary: upgrade to debezium 2.1.x Key: CAMEL-18838 URL: https://issues.apache.org/jira/browse/CAMEL-18838 Project: Camel Issue Type: Dependency upgrade Components: camel-debezium Reporter: Claus Ibsen Fix For: 3.21.0 There is a new google-cloud-spanner connector, so we should create a camel component for that. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (CAMEL-18837) Component for Opensearch
[
https://issues.apache.org/jira/browse/CAMEL-18837?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen updated CAMEL-18837:
Fix Version/s: 3.x
> Component for Opensearch
>
>
> Key: CAMEL-18837
> URL: https://issues.apache.org/jira/browse/CAMEL-18837
> Project: Camel
> Issue Type: Improvement
>Reporter: Federico Mariani
>Priority: Major
> Fix For: 3.x
>
>
> {code:java}
> OpenSearch is a community-driven, open source search and analytics suite
> derived from Apache 2.0 licensed Elasticsearch 7.10.2 & Kibana 7.10.2. It
> consists of a search engine daemon, OpenSearch, and a visualization and user
> interface, OpenSearch Dashboards.
> {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (CAMEL-18837) Component for Opensearch
[
https://issues.apache.org/jira/browse/CAMEL-18837?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen updated CAMEL-18837:
Issue Type: New Feature (was: Improvement)
> Component for Opensearch
>
>
> Key: CAMEL-18837
> URL: https://issues.apache.org/jira/browse/CAMEL-18837
> Project: Camel
> Issue Type: New Feature
>Reporter: Federico Mariani
>Priority: Major
> Fix For: 3.x
>
>
> {code:java}
> OpenSearch is a community-driven, open source search and analytics suite
> derived from Apache 2.0 licensed Elasticsearch 7.10.2 & Kibana 7.10.2. It
> consists of a search engine daemon, OpenSearch, and a visualization and user
> interface, OpenSearch Dashboards.
> {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (CAMEL-18837) Component for Opensearch
[
https://issues.apache.org/jira/browse/CAMEL-18837?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17651349#comment-17651349
]
Claus Ibsen commented on CAMEL-18837:
-
Yeah this is a good idea
> Component for Opensearch
>
>
> Key: CAMEL-18837
> URL: https://issues.apache.org/jira/browse/CAMEL-18837
> Project: Camel
> Issue Type: Improvement
>Reporter: Federico Mariani
>Priority: Major
>
> {code:java}
> OpenSearch is a community-driven, open source search and analytics suite
> derived from Apache 2.0 licensed Elasticsearch 7.10.2 & Kibana 7.10.2. It
> consists of a search engine daemon, OpenSearch, and a visualization and user
> interface, OpenSearch Dashboards.
> {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (CAMEL-18836) support resume cursor in camel azure storage blog changefeed operation
[
https://issues.apache.org/jira/browse/CAMEL-18836?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen updated CAMEL-18836:
Issue Type: Improvement (was: Bug)
> support resume cursor in camel azure storage blog changefeed operation
> --
>
> Key: CAMEL-18836
> URL: https://issues.apache.org/jira/browse/CAMEL-18836
> Project: Camel
> Issue Type: Improvement
> Components: camel-azure
>Affects Versions: 3.20.0
>Reporter: Andrea Tarocchi
>Priority: Major
>
> At the moment there is no reliable way to instruct {{getChangefeed}}
> operation of camel-azure-storage-blob component to resume processing the
> events from where the previous call finished. Theoretically the
> {{changeFeedStartTime}} and {{changeFeedEndTime}} could be used to somehow
> achieve that, but per the documentation those are not very precise (you can
> lose event if you don't round them at the hour) and the suggestion is to use
> the resume cursor mechanism see:
> https://learn.microsoft.com/en-us/azure/storage/blobs/storage-blob-change-feed-how-to#resume-reading-records-from-a-saved-position
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Resolved] (CAMEL-18834) camel-core - StringQuoteHelper should remove quotes for single element
[ https://issues.apache.org/jira/browse/CAMEL-18834?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen resolved CAMEL-18834. - Resolution: Fixed > camel-core - StringQuoteHelper should remove quotes for single element > -- > > Key: CAMEL-18834 > URL: https://issues.apache.org/jira/browse/CAMEL-18834 > Project: Camel > Issue Type: Bug > Components: camel-core >Affects Versions: 3.20.0 >Reporter: Claus Ibsen >Priority: Minor > Fix For: 3.21.0, 3.20.1 > > > Reported via > https://github.com/apache/camel/pull/8936 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (CAMEL-18837) Component for Opensearch
Federico Mariani created CAMEL-18837:
Summary: Component for Opensearch
Key: CAMEL-18837
URL: https://issues.apache.org/jira/browse/CAMEL-18837
Project: Camel
Issue Type: Improvement
Reporter: Federico Mariani
{code:java}
OpenSearch is a community-driven, open source search and analytics suite
derived from Apache 2.0 licensed Elasticsearch 7.10.2 & Kibana 7.10.2. It
consists of a search engine daemon, OpenSearch, and a visualization and user
interface, OpenSearch Dashboards.
{code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Created] (CAMEL-18836) support resume cursor in camel azure storage blog changefeed operation
Andrea Tarocchi created CAMEL-18836:
---
Summary: support resume cursor in camel azure storage blog
changefeed operation
Key: CAMEL-18836
URL: https://issues.apache.org/jira/browse/CAMEL-18836
Project: Camel
Issue Type: Bug
Components: camel-azure
Affects Versions: 3.20.0
Reporter: Andrea Tarocchi
At the moment there is no reliable way to instruct {{getChangefeed}} operation
of camel-azure-storage-blob component to resume processing the events from
where the previous call finished. Theoretically the {{changeFeedStartTime}} and
{{changeFeedEndTime}} could be used to somehow achieve that, but per the
documentation those are not very precise (you can lose event if you don't round
them at the hour) and the suggestion is to use the resume cursor mechanism see:
https://learn.microsoft.com/en-us/azure/storage/blobs/storage-blob-change-feed-how-to#resume-reading-records-from-a-saved-position
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (CAMEL-18835) camel-core-processor: OnCompletionProcessor#onFailure callback fires more than once
[ https://issues.apache.org/jira/browse/CAMEL-18835?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Babak Vahdat updated CAMEL-18835: - Summary: camel-core-processor: OnCompletionProcessor#onFailure callback fires more than once (was: camel-core: OnCompletionProcessor#onFailure callback fires more than once) > camel-core-processor: OnCompletionProcessor#onFailure callback fires more > than once > --- > > Key: CAMEL-18835 > URL: https://issues.apache.org/jira/browse/CAMEL-18835 > Project: Camel > Issue Type: Bug > Components: camel-core-processor >Affects Versions: 3.20.0 >Reporter: Babak Vahdat >Assignee: Babak Vahdat >Priority: Minor > Fix For: 3.18.5, 3.20.1 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (CAMEL-18835) camel-core: OnCompletionProcessor#onFailure callback fires more than once
[ https://issues.apache.org/jira/browse/CAMEL-18835?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Babak Vahdat updated CAMEL-18835: - Summary: camel-core: OnCompletionProcessor#onFailure callback fires more than once (was: OnCompletionProcessor#onFailure callback fires more than once) > camel-core: OnCompletionProcessor#onFailure callback fires more than once > - > > Key: CAMEL-18835 > URL: https://issues.apache.org/jira/browse/CAMEL-18835 > Project: Camel > Issue Type: Bug > Components: camel-core-processor >Affects Versions: 3.20.0 >Reporter: Babak Vahdat >Assignee: Babak Vahdat >Priority: Minor > Fix For: 3.18.5, 3.20.1 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (CAMEL-18835) OnCompletionProcessor#onFailure callback fires more than once
Babak Vahdat created CAMEL-18835: Summary: OnCompletionProcessor#onFailure callback fires more than once Key: CAMEL-18835 URL: https://issues.apache.org/jira/browse/CAMEL-18835 Project: Camel Issue Type: Bug Components: camel-core-processor Affects Versions: 3.20.0 Reporter: Babak Vahdat Assignee: Babak Vahdat Fix For: 3.18.5, 3.20.1 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (CAMEL-18834) camel-core - StringQuoteHelper should remove quotes for single element
Claus Ibsen created CAMEL-18834: --- Summary: camel-core - StringQuoteHelper should remove quotes for single element Key: CAMEL-18834 URL: https://issues.apache.org/jira/browse/CAMEL-18834 Project: Camel Issue Type: Bug Components: camel-core Affects Versions: 3.20.0 Reporter: Claus Ibsen Fix For: 3.20.1, 3.21.0 Reported via https://github.com/apache/camel/pull/8936 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (CAMEL-18783) camel-cxf - avoid referring Singleton bean instance(CxfEndpoint) while changing its state in different URIs
[
https://issues.apache.org/jira/browse/CAMEL-18783?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17651134#comment-17651134
]
Lukas Lowinger commented on CAMEL-18783:
[~ppalaga] It was automatically verified by upgrade to 3.20.0 in CQ repository
- eg. we have to apply those changes
https://github.com/apache/camel-quarkus/commit/b115a4b25013098af1024f201fa13e18eb441fb8
as we alter (which shouldn't be allowed) CXFEndpoint in ApplicationScope.
> camel-cxf - avoid referring Singleton bean instance(CxfEndpoint) while
> changing its state in different URIs
> ---
>
> Key: CAMEL-18783
> URL: https://issues.apache.org/jira/browse/CAMEL-18783
> Project: Camel
> Issue Type: Improvement
> Components: camel-cxf
>Affects Versions: 3.18.3
>Reporter: Lukas Lowinger
>Assignee: Freeman Yue Fang
>Priority: Minor
> Fix For: 3.20.0
>
>
> Having one `cxf:bean:soapClientEndpoint` (with Singleton scope) and following
> two routes
> {code}
> from("direct:simpleUriBean")
> .to("cxf:bean:soapClientEndpoint?dataFormat=PAYLOAD");
> from("direct:operandsAdd")
> .to("cxf:bean:soapClientEndpoint?dataFormat=POJO");
> {code}
> Leads to situation, that invoking route via `direct:simpleUriBean` will use
> `dataFormat=POJO` instead of PAYLOAD (which reader of that code could
> expect). Could we somehow detect those misuses of URI options ?
> Eg. printing WARNING: You are using URI option dataFormat which wasn't taken
> into account because you are using shared bean with Singleton scope.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
