[SPARK-53892][SS] Use DescribeTopicsResult.allTopicNames instead of the deprecated all API
#52597
+10
−9
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
dongjoon-hyun
changed the title
dongjoon-hyun
changed the title
DescribeTopicsResult
KAFKA-10774 Support Describe topic using topic IDs KAFKA-18289 Remove deprecated methods of DescribeTopicsResult
dongjoon-hyun
force-pushed
the
DescribeTopicsResult
branch
from
ea369c7 to
5003cd7
Compare
dongjoon-hyun
changed the title
DescribeTopicsResultDescribeTopicsResult.allTopicNames instead of the deprecated all API
HyukjinKwon
approved these changes
Oct 14, 2025
|
Thank you, @HyukjinKwon . Merged to master. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
What changes were proposed in this pull request?
This PR aims to use
DescribeTopicsResult.allTopicNamesAPI instead of the deprecatedallAPI.Why are the changes needed?
allAPI was deprecated at Apache Kafka 3.1.0 and removed at 4.0.0.Does this PR introduce any user-facing change?
No behavior change.
How was this patch tested?
Pass the CIs.
Was this patch authored or co-authored using generative AI tooling?
No.