Repository navigation
fix(kafka): create and converge topics a broker refuses compression.type on - #928
Merged
Merged
Conversation
…ype on A topic-level compression.type is a preference, so a broker that answers INVALID_CONFIG to it (Redpanda Cloud does) now gets the topic, or the rest of the converge, without that key and keeps its own value. A refused required config such as max.message.bytes still fails the topic.
|
Released in v1.22.51 -- https://github.com/hyperi-io/dfe-engine/releases/tag/v1.22.51 |
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.
Redpanda Cloud answers INVALID_CONFIG to a topic-level compression.type, so a source deploy there failed with topics_not_created and its source never deployed.
Done when the Redpanda Cloud source suite deploys its source.