Skip to content

Remove unused variable#38360

Closed
Amar3tto wants to merge 1 commit intomasterfrom
fix-kafka-unused
Closed

Remove unused variable#38360
Amar3tto wants to merge 1 commit intomasterfrom
fix-kafka-unused

Conversation

@Amar3tto
Copy link
Copy Markdown
Collaborator

@Amar3tto Amar3tto commented May 1, 2026

Please add a meaningful description for your change here


Thank you for your contribution! Follow this checklist to help us incorporate your contribution quickly and easily:

  • Mention the appropriate issue in your description (for example: addresses #123), if applicable. This will automatically add a link to the pull request in the issue. If you would like the issue to automatically close on merging the pull request, comment fixes #<ISSUE NUMBER> instead.
  • Update CHANGES.md with noteworthy changes.
  • If this contribution is large, please file an Apache Individual Contributor License Agreement.

See the Contributor Guide for more tips on how to make review process smoother.

To check the build health, please visit https://github.com/apache/beam/blob/master/.test-infra/BUILD_STATUS.md

GitHub Actions Tests Status (on master branch)

Build python source distribution and wheels
Python tests
Java tests
Go tests

See CI.md for more information about GitHub Actions CI or the workflows README to see a list of phrases to trigger workflows.

@Amar3tto Amar3tto requested a review from Abacn May 1, 2026 19:53
@gemini-code-assist
Copy link
Copy Markdown
Contributor

Summary of Changes

Hello, I'm Gemini Code Assist1! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request performs a minor cleanup by removing an unused variable that was no longer serving a purpose in the KafkaIO source descriptor logic. This helps reduce code clutter and improves maintainability.

Highlights

  • Code Cleanup: Removed the unused logTopicVerification variable from the GenerateKafkaSourceDescriptor class in KafkaIO.java.

🧠 New Feature in Public Preview: You can now enable Memory to help Gemini Code Assist learn from your team's feedback. This makes future code reviews more consistent and personalized to your project's style. Click here to enable Memory in your admin console.

Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature Command Description
Code Review /gemini review Performs a code review for the current pull request in its current state.
Pull Request Summary /gemini summary Provides a summary of the current pull request in its current state.
Comment @gemini-code-assist Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help /gemini help Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for GitHub and other Google products, sign up here.

Footnotes

  1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution.

Copy link
Copy Markdown
Contributor

@gemini-code-assist gemini-code-assist Bot left a comment

Choose a reason for hiding this comment

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

Code Review

This pull request removes the logTopicVerification field and its initialization from the GenerateKafkaSourceDescriptor class. The reviewer suggests that if the variable is unused throughout the KafkaIO transform, it should also be removed from the Read class for consistency. Furthermore, it is recommended to group field declarations at the beginning of the class to enhance maintainability.

this.topicPattern = read.getTopicPattern();
this.startReadTime = read.getStartReadTime();
this.stopReadTime = read.getStopReadTime();
this.logTopicVerification = read.getLogTopicVerification();
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

medium

The logTopicVerification variable and its associated configuration methods (e.g., withLogTopicVerification, getLogTopicVerification) likely still exist in the KafkaIO.Read class. If this variable is truly unused across the entire KafkaIO transform, it should also be removed from the Read class to maintain a clean and consistent public API.

@VisibleForTesting final @Nullable List<String> topics;

private final @Nullable Pattern topicPattern;
private final @Nullable Boolean logTopicVerification;
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

medium

The remaining field declarations in this class (such as topics and topicPattern) are scattered after the constructor. For better maintainability, these should be grouped together at the beginning of the class.

@derrickaw
Copy link
Copy Markdown
Collaborator

derrickaw commented May 1, 2026

Hi @Amar3tto, I think John reverted the PR - #38361 to fix this. We collectively opened 3 prs to fix. Good response from everyone :)

@Amar3tto Amar3tto closed this May 1, 2026
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.

2 participants