You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@camel.apache.org by "Claus Ibsen (Jira)" <ji...@apache.org> on 2026/07/19 08:42:00 UTC

[jira] [Resolved] (CAMEL-24198) camel-azure-eventhubs - Redesign checkpoint store to use per-partition batching

     [ https://issues.apache.org/jira/browse/CAMEL-24198?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Claus Ibsen resolved CAMEL-24198.
---------------------------------
    Resolution: Fixed

Fixed via https://github.com/apache/camel/pull/24903

> camel-azure-eventhubs - Redesign checkpoint store to use per-partition batching
> -------------------------------------------------------------------------------
>
>                 Key: CAMEL-24198
>                 URL: https://issues.apache.org/jira/browse/CAMEL-24198
>             Project: Camel
>          Issue Type: Improvement
>          Components: camel-azure-eventhubs
>            Reporter: Claus Ibsen
>            Priority: Major
>             Fix For: 4.22.0
>
>
> The EventHubs consumer currently uses a single lastTask/processedEvents/lastScheduledTask set of fields shared across all partitions. This means checkpoint commits from different partitions can interfere with each other, and the batch counter does not accurately reflect per-partition progress.
> The fix requires changing these single fields to per-partition maps (keyed by partitionId), so each partition independently tracks its processed event count and schedules its own checkpoint commit. This is an architectural change that needs focused review.
> Found during the CAMEL-24158 code review (finding #6).
> Affected file: EventHubsConsumer.java



--
This message was sent by Atlassian Jira
(v8.20.10#820010)