Repository navigation
[cleanup][broker] Clean up scalable topic type references in ServerCnx - #25920
Merged
Merged
Conversation
void-ptr974
approved these changes
Jun 3, 2026
void-ptr974
left a comment
Contributor
There was a problem hiding this comment.
LGTM. Thanks for cleaning this up.
lhotari
approved these changes
Jun 3, 2026
merlimat
approved these changes
Jun 3, 2026
1 task
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.
Motivation
ServerCnxhandles several scalable topic commands and sessions, but the scalable topic related code used a mix of fully qualified class names and imported types. This made the code harder to scan and inconsistent with thesurrounding style.
Modifications
This PR cleans up scalable topic related type references in
ServerCnxby:ConcurrentHashMapusage with the existing imported type.There is no behavior change.
Verifying this change
This change is a trivial rework / code cleanup without any test coverage.
Does this pull request potentially affect one of the following parts: