From 5ec3c02855689dd5fd78601e3de5e87b36a70d5b Mon Sep 17 00:00:00 2001 From: gnodet Date: Wed, 21 Oct 2026 11:43:38 +0000 Subject: [PATCH] =?UTF-8?q?CAMEL-25781:=20camel-azure-eventhubs=20-=20add?= =?UTF-8?q?=20upgrade=20note=20to=20main's=204.22.2=E2=86=924.22.3=20guide?= =?UTF-8?q?=20section?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit --- .../ROOT/pages/camel-4x-upgrade-guide-4_22.adoc | 13 +++++++++++++ 1 file changed, 13 insertions(+) diff --git a/docs/user-manual/modules/ROOT/pages/camel-4x-upgrade-guide-4_22.adoc b/docs/user-manual/modules/ROOT/pages/camel-4x-upgrade-guide-4_22.adoc index f756002ec730b..fdffeeecdbe68 100644 --- a/docs/user-manual/modules/ROOT/pages/camel-4x-upgrade-guide-4_22.adoc +++ b/docs/user-manual/modules/ROOT/pages/camel-4x-upgrade-guide-4_22.adoc @@ -13,6 +13,19 @@ See the xref:camel-upgrade-recipes-tool.adoc[documentation] page for details. == Upgrading from 4.22.2 to 4.22.3 +=== camel-azure-eventhubs - an event that completes when the checkpoint timer of its window has run is checkpointed + +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. + +The `CamelAzureEventHubsCheckpointUpdatedBy` header can now be `timeout`. An event that completes after the +scheduled time of its window, but before the (late) timer has run, joins that window and gets `timeout`; its offset is +checkpointed by that timer. Before, such an event always started a new window, so `timeout` was practically never +set. Routes that read this header can now see `timeout` as well as `size`. + === camel-milo - the OPC UA client validates the server certificate When the endpoint it selects uses a security policy other than `None`, the `milo-client` and `milo-browse` components