Hi community,
Let me repost this cause I don't get replies in github issue here
https://github.com/apache/camel-kafka-connector/issues/1568
I'm testing camel-azure-storage-blob-sink-kafka-connector from k8s.
So far, I've confirmed CamelHeader option works
Hi community,
I'm using camel-azure-storage-blob-sink-kafka-connector from k8s, and let
kafkaconnect upload the logs (Kafka messages) to Azure Blob.
I've used message header to specify the file path, and also use aggregation
options in Camel as follows
camel.aggregation.size: 2
Hello,
The aggregation works in the following way, if you have the message 1 and
2 and an aggregation size of 2, you'll get a file with 1,2 as content and
an exchange Id as file name if you don't specify the header, otherwise it
should be the last header you sent as file name.
It doesn't
Sure happy to give feedback. I plan to upgrade from 3.20.x to 4.x.
Currently, thus not migrating yet, but planning has started.
The things I need to consider:
- I first need to finish some stuff to upgrade from 2.x to 3.x (Currently
the docs for 2.0 are gone, is the archive to Camel 2.0
Hi
If you have been migrating to Camel 4 already, then any feedback is welcome.
You can comment in the PR, or post here in the mailing list
https://github.com/apache/camel-website/pull/1071
--
Claus Ibsen
-
@davsclaus
Camel in Action 2: https://www.manning.com/ibsen2
The reason for camel-atlasmap to be removed was the fact Atlasmap was
discontinued.
There were no releases since October.
Il giorno ven 6 ott 2023 alle ore 11:34 Gerald Kallas
ha scritto:
> Hi folks,
>
> what's the reason that camel-atlasmap has been removed in Camel 4. Is
> there any
Hi,
For me the biggest issues regarding Camel 4 have been when Karavan VS Code
extension updated itself to 4.0.0. I'm not sure things related to Karavan
are discussed in the blog post but here's couple things we've encountered.
In short, if you use Karavan 4.x.x to open a route which has been
Hi folks,
what's the reason that camel-atlasmap has been removed in Camel 4. Is there any
alternative planned for mapping processors that don't need to be coded?
Best
Gerald
> ski n hat am 06.10.2023 10:51 CEST geschrieben:
>
>
> Sure happy to give feedback. I plan to upgrade from 3.20.x
Hi Raymond
Thanks for the feedback. Yes you are not the typical Camel end user, so
your migration "work" is more than normal.
The note about using PluginHelper etc is something we should highlight in
the blog post, thanks.
On Fri, Oct 6, 2023 at 10:52 AM ski n wrote:
> Sure happy to give
Mark,
Scenario for service restart will cause any dynamic route from being removed.
It would require ReST to be idempotent and return or more complex -
persisting routes and reloading them.
ચિરાગ/चिराग/Chirag
--
Sent from My Gmail Account
On Thu, Oct 5,
On Fri, Oct 6, 2023 at 11:34 AM Mikael Koskinen wrote:
> Hi,
>
> For me the biggest issues regarding Camel 4 have been when Karavan VS Code
> extension updated itself to 4.0.0. I'm not sure things related to Karavan
> are discussed in the blog post but here's couple things we've encountered.
>
>
ya. was just saying you need a plan if you wanted to keep consuming the
route after restart.
anyway, like i said, you have all the pieces to do this. Anything more
would be writing it. But here is some pseudo code.
from(some Trigger)
to(http) // get the topic
one thing that got us was, since we were using kafka with security but not
using Kafka idempotency, we had to add the following flag. As usual, kafka
messages were not helpful.
camel.component.kafka.enable-idempotence=false
On Fri, Oct 6, 2023 at 3:49 AM Claus Ibsen wrote:
> Hi
>
> If you have
Not being the typical Camel user, I see that as a compliment :)
For the blog it may be also good to highlight not just how to upgrade
(migration path), but also why to upgrade.
There are technical reason like being up to date with Jakarta
EE/Spring/Quarkus, but I think most users are even more
14 matches
Mail list logo
