Refactor event publishing to use null keys for Kafka messages - #164
Merged
Conversation
adityajoshi12
force-pushed
the
kafka-partition
branch
8 times, most recently
from
February 27, 2026 11:24
bc940f4 to
ccf1c35
Compare
Signed-off-by: adityajoshi12 <adityaprakashjoshi1@gmail.com> Signed-off-by: Aditya Joshi <adityaprakashjoshi1@gmail.com>
adityajoshi12
force-pushed
the
kafka-partition
branch
from
March 2, 2026 15:33
ccf1c35 to
a3e4060
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Refactor event publishing to use null keys for Kafka messages, ensuring even distribution across partitions.