isolation.level
The consumer setting that decides whether records from open or aborted transactions are returned: read_uncommitted or read_committed.
In more detail
The default, read_uncommitted, returns records as soon as they are written. read_committed holds them back until their transaction commits and never returns aborted ones. Transactions only help if the consumers use read_committed.
Example
KafkaConsumer('results', isolation_level='read_committed')Related terms
- Kafka transaction — A group of writes, possibly across several partitions and topics, that Kafka makes visible all together on commit or not at all on abort.
- commit marker — A special record the broker writes into each partition of a transaction to mark it as committed or aborted.
- isolation level — A setting that controls how much concurrent transactions can see of each other's changes and how they may interleave.
Taught in
- The Payment That Was Charged Twice — Confluent Apache Kafka Certifications (CCDAK and CCAAK) Exam Prep
- The Error Storm That Fixes Itself — Confluent Apache Kafka Certifications (CCDAK and CCAAK) Exam Prep
- Two Copies Of One Service — Confluent Apache Kafka Certifications (CCDAK and CCAAK) Exam Prep
- Twenty Seconds Of Nothing — Confluent Apache Kafka Certifications (CCDAK and CCAAK) Exam Prep
- Seventy One Percent — Confluent Apache Kafka Certifications (CCDAK and CCAAK) Exam Prep
- Transactions And Exactly Once Semantics — Apache Kafka & Event Streaming