Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

KAFKA-19055: Cleanup the 0.10.x information from clients module #19320

Open
wants to merge 3 commits into
base: trunk
Choose a base branch
from

Conversation

LoganZhuZzz
Copy link
Contributor

@LoganZhuZzz LoganZhuZzz commented Mar 31, 2025

Removes outdated references to Kafka 0.10.x in the clients module documentation. Since the baseline version is now 2.1, any mentions of versions earlier than this are unnecessary and have been removed or updated accordingly.

Changes:

  • Updated ClusterResource, ClusterResourceListener, and DescribeClusterResult Javadoc to reflect the minimum supported broker version as 2.1.
  • Updated TopicConfig documentation: Removed references to consumers older than 0.10.2.
  • Removed references to 0.10.x and adjusted explanations to remain relevant for newer versions.

Testing & Impact:

  • This PR only modifies Javadoc comments—no functional code changes.
  • No impact on existing functionality.

Reviewers: Chia-Ping Tsai [email protected]

@github-actions github-actions bot added triage PRs from the community clients small Small PRs labels Mar 31, 2025
@@ -24,7 +24,7 @@
* <p>
* <h4>Clients</h4>
* There will be one invocation of {@link ClusterResourceListener#onUpdate(ClusterResource)} after each metadata response.
* Note that the cluster id may be null when the Kafka broker version is below 0.10.1.0. If you receive a null cluster id, you can expect it to always be null unless you have a cluster with multiple broker versions which can happen if the cluster is being upgraded while the client is running.
* Note the minimum supported broker version is 2.1. If you receive a null cluster id, you can expect it to always be null unless you have a cluster with multiple broker versions which can happen if the cluster is being upgraded while the client is running.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It is impossible to have "null" cluster id for now, right?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It is impossible to have "null" cluster id for now, right?

I will remove the outdated part.

Copy link
Member

@FrankYang0529 FrankYang0529 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Not sure whether we can also remove these lines if we drop support for version below 2.1?

"If this is increased and there are consumers older than 0.10.2, the consumers' fetch " +
"size must also be increased so that they can fetch record batches this large. " +

@github-actions github-actions bot removed the triage PRs from the community label Apr 1, 2025
@LoganZhuZzz
Copy link
Contributor Author

Not sure whether we can also remove these lines if we drop support for version below 2.1?

"If this is increased and there are consumers older than 0.10.2, the consumers' fetch " +
"size must also be increased so that they can fetch record batches this large. " +

OffsetFetcherUtils also contains logic related to 0.10.x support. However, I’m not sure if it aligns with the scope of the JIRA issue. Should we clean it up in this PR as well?

@chia7712
Copy link
Member

chia7712 commented Apr 1, 2025

OffsetFetcherUtils also contains logic related to 0.10.x support. However, I’m not sure if it aligns with the scope of the JIRA issue. Should we clean it up in this PR as well?

yes, please revise it as well. Also, please add this changes to the PR description.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants