MINOR: Correct broker dynamic configuration names in the documentation#22825
Open
popsunlake wants to merge 1 commit into
Open
MINOR: Correct broker dynamic configuration names in the documentation#22825popsunlake wants to merge 1 commit into
popsunlake wants to merge 1 commit into
Conversation
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.
The broker configuration documentation incorrectly uses the topic-level name
max.message.bytesin its list of dynamically updateable default topic settings. This changes it to the corresponding broker configuration name,message.max.bytes.The same documentation also lists
advertised.listenersas dynamically updateable, although it is not included in the authoritative dynamic broker configuration set and alter requests for it are rejected. This removes it from the per-broker dynamic listener configuration list.No tests or builds were run because this is a documentation-only change. The updates were checked against
ServerTopicConfigSynonyms, the dynamic broker configuration definitions, and the existing unit and Admin integration tests.