Hi when checking on consumer properties for idempotency fix for Druid 30.0.1v, I noticed that by default,

isolation.level

is set to

read_committed

https://druid.apache.org/docs/30.0.1/ingestion/kafka-ingestion/#consumer-properties But in latest version, I see default value is set to

read_uncommitted

. Is there any reason why default value is changed. I believe

read_commited

provides correct behaviour when producer uses transactions/idempotency and has no negative impact when it's not https://druid.apache.org/docs/latest/ingestion/kafka-ingestion/#consumer-properties

I think that's a mistake in the documentation. The code sets

isolation.level: read_committed

, see here https://github.com/apache/druid/blob/313ba8e3dc386b5d974739178e3d7b385a750b09/extensions-core/kafka-indexing-service/src/main/java/org/apache/druid/indexing/kafka/KafkaRecordSupplier.java#L385

I see, thanks @Gian Merlino for looking into this