This is an automated email from the ASF dual-hosted git repository.
gnodet pushed a commit to branch main
in repository https://gitbox.apache.org/repos/asf/camel.git
The following commit(s) were added to refs/heads/main by this push:
new 34af3c4a8723 docs: add camel-azure-eventhubs 4.18.5→4.18.6 upgrade
guide entry on main
34af3c4a8723 is described below
commit 34af3c4a87237543d0655b6d2ef05698a81f6caa
Author: gnodet <[email protected]>
AuthorDate: Wed Oct 21 11:43:30 2026 +0000
docs: add camel-azure-eventhubs 4.18.5→4.18.6 upgrade guide entry on main
---
.../ROOT/pages/camel-4x-upgrade-guide-4_18.adoc | 22 ++++++++++++++++++++++
1 file changed, 22 insertions(+)
diff --git
a/docs/user-manual/modules/ROOT/pages/camel-4x-upgrade-guide-4_18.adoc
b/docs/user-manual/modules/ROOT/pages/camel-4x-upgrade-guide-4_18.adoc
index d7592015ed91..a1eee73ded10 100644
--- a/docs/user-manual/modules/ROOT/pages/camel-4x-upgrade-guide-4_18.adoc
+++ b/docs/user-manual/modules/ROOT/pages/camel-4x-upgrade-guide-4_18.adoc
@@ -13,6 +13,28 @@ See the xref:camel-upgrade-recipes-tool.adoc[documentation]
page for details.
== Upgrading from 4.18.5 to 4.18.6
+=== camel-azure-eventhubs - per-partition checkpoint counters and timer;
checkpoint window boundary fix
+
+Several fixes from 4.22.x have been brought forward to 4.18.6 to give this
change a sound base.
+
+`checkpointBatchSize` and `checkpointBatchTimeout` now count events per
partition, not across all
+partitions. Each partition has its own `AtomicInteger` counter and its own
`ScheduledFuture` timer.
+A checkpoint on one partition no longer resets the count of another. Before
this change, the shared
+counter mixed events across partitions, so the batch size was reached across
all partitions combined
+and a checkpoint on a busy partition could reset the count for a quiet one.
+
+The `CamelAzureEventHubsCheckpointUpdatedBy` header can now be `timeout`. With
`checkpointBatchTimeout`,
+the consumer now starts a new checkpoint window when the timer of the current
window has run, and no
+longer when the wall clock passes the time the timer was scheduled for.
Before, an event that completed
+in the millisecond in which the timer ran (or while the timer was taking the
count) was counted in the
+window whose count had already been taken: it was checkpointed only with the
next event, and when the
+partition stayed quiet it was delivered again after a restart. Routes that
read this header may now see
+`timeout` more often.
+
+Checkpoint failures from the timer are now logged at `WARN` level with the
full stack trace instead of
+at `DEBUG` level with the message only. Checkpoint failures triggered by batch
size are still logged at
+`WARN`.
+
=== camel-lra - only an LRA hosted by the configured coordinator is joined
The LRA saga service now joins, completes or compensates an LRA only when its
URL is under the configured LRA
