Repository navigation
feat(ReloadingProducer): add concept of logical to physical topic - #581
Merged
Merged
Conversation
untitaker
approved these changes
Oct 19, 2026
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
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.
Ref STREAM-1922
This PR makes a breaking change to the config blob format, replacing
TopicEntrywithLogicalTopicEntrythat maps to aPhysicalTopicEntry.ReloadingKafkaProducerforwards messages produced to the logical topic to the correct physical topic.logical_topicentirely, which was used as an alias for the topic name. Users produce to the topic name listed inLogicalTopicEntry, and the reloading client abstracts the physical topic away from the user by swapping in the correct destination for the physical topic