Closed akshatraika-moment closed 7 months ago
It shouldn't, the default partitioner uses the same logic, including murmur2 hashing. I don't know how to run (i.e. test) Java but I did transliterate the Java code directly. You're using records with the same key?
@akshatraika-moment, I think the Confluent client uses CRC32 by default as it's based on librdkafka. Take a look at https://github.com/confluentinc/librdkafka/blob/master/CONFIGURATION.md#topic-configuration-properties and search for 'partitioner'.
Ah, I would've figured confluent-kafka-go mirrored the Java codebase. ty @yianni.
If that's the case -- SaramaHasher with crc32 I think mirrors librdkafka, per #669
I see, I'll try that. Appreciate the quick response!
Let me know this isn't resolved, closing now
I was able to resolve this by switching the hash fn. thanks!
Does kgo have special partitioning logic if we are opting for default key based partitioning? I have 2 services that both write to the same kafka topic. One uses kgo and one uses confluent-kafka-go and the messages are ending up in different partitions.