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 2022/05/11 19:19:00 UTC
[jira] [Resolved] (CAMEL-17913) camel-kafka - Not able to set IsolationLevel using consumer parameters
[ https://issues.apache.org/jira/browse/CAMEL-17913?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Claus Ibsen resolved CAMEL-17913.
---------------------------------
Resolution: Fixed
> camel-kafka - Not able to set IsolationLevel using consumer parameters
> ----------------------------------------------------------------------
>
> Key: CAMEL-17913
> URL: https://issues.apache.org/jira/browse/CAMEL-17913
> Project: Camel
> Issue Type: Improvement
> Components: camel-kafka
> Affects Versions: 3.14.2
> Reporter: itachi uchiha
> Assignee: Claus Ibsen
> Priority: Minor
> Fix For: 3.17.0
>
> Attachments: image-2022-04-06-19-26-31-080.png
>
>
> When we initialize a KafkaConsumer, we can set the property called isolation.level to control what transaction records are exposed to the consumer. Two values are then possible, read_uncommitted to retrieve all records, independently on the transaction outcome (if any), and read_committed to get only the records from committed transactions.
>
> in,
> org.apache.kafka.clients.consumer.ConsumerConfig
> DEFAULT_ISOLATION_LEVEL is IsolationLevel.READ_UNCOMMITTED.toString().toLowerCase(Locale.ROOT);
>
> and there is no way we can change ISOLATION_LEVEL to IsolationLevel.READ_COMMITTED by camel-kafka
> ************************************************************************************************************************************************************
> org.apache.kafka.clients.consumer.ConsumerConfig
> ----------------------------------------------------------------
> !image-2022-04-06-19-26-31-080.png!
--
This message was sent by Atlassian Jira
(v8.20.7#820007)