KAFKA-19669: Merge repartition topics when value-changing operations are present #20807
+415
−48
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.
Prior to KAFKA-19669, merge repartition topics optimization stops at value-changing operations (mapValues, flatMapValues, etc.) As a result, topology builder cannot merge repartition topics that are separated by value-changing operations, which results in inefficiency due to multiple repartition topics.
This patch introduces tracking value serdes at each node. This allows pushing repartition upstream past value-changing operations by switching to upstream serdes when resolving. As a result, it enables merging repartitions across value-changing boundaries. This merging will improve the overall processing efficiency.