You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@camel.apache.org by "Otavio Rodolfo Piske (Jira)" <ji...@apache.org> on 2022/04/28 05:17:00 UTC

[jira] [Updated] (CAMEL-18024) camel-kafka: rework last processed offset tracking

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

Otavio Rodolfo Piske updated CAMEL-18024:
-----------------------------------------
    Component/s: camel-kafka

> camel-kafka: rework last processed offset tracking
> --------------------------------------------------
>
>                 Key: CAMEL-18024
>                 URL: https://issues.apache.org/jira/browse/CAMEL-18024
>             Project: Camel
>          Issue Type: Task
>          Components: camel-kafka
>            Reporter: Otavio Rodolfo Piske
>            Priority: Major
>
> The record fetcher keeps track of the last processed offset via HashMap that associates the partition+key pair to an offset. This is primarily used for rollbacks and commits when doing manual commit management.
> We should probably move this within the commit management code to further simplify the code.
>  
> Also, as [pointed here|https://github.com/apache/camel/pull/7503#issuecomment-1111119006], the data structure in use is not thread-safe.



--
This message was sent by Atlassian Jira
(v8.20.7#820007)