Fix #37833: Use named logger instead of root logger in transforms/util.py

[liferoad]

What

Fixes #37833

apache_beam.transforms.util was using the root logger (logging.info(...), logging.warning(...), etc.) instead of a module-level named logger. This prevented sdk_harness_log_level_overrides from controlling log levels for this module (e.g., suppressing the verbose BatchElements statistics message at line 1029).

Changes

• Added _LOGGER = logging.getLogger(__name__) after imports
• Replaced all 8 root logger calls with _LOGGER calls

This is consistent with other modules like apache_beam.transforms.core which already use _LOGGER = logging.getLogger(__name__).

How it was tested

Minimal change — only replaces the logger object used. No behavioral change unless sdk_harness_log_level_overrides is configured, in which case named logger overrides will now correctly apply to apache_beam.transforms.util.

---

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

• Addresses an existing issue: [Bug]: sdk_harness_log_level_overrides not applied because root logger instead of named logger is being used #37833
• Includes tests (not needed — no logic change)
• Updates documentation (not needed)

[gemini-code-assist]

Summary of Changes

Hello, I'm Gemini Code Assist¹! 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 refactors the logging implementation within apache_beam.transforms.util to utilize a named logger instead of the root logger. This change is crucial for allowing external configurations, such as sdk_harness_log_level_overrides, to effectively control the verbosity of logs originating from this module, thereby improving log management and debugging capabilities.

Highlights

• Logging Mechanism: Switched apache_beam.transforms.util from using the global root logger to a dedicated module-level named logger.
• Log Level Control: Enabled sdk_harness_log_level_overrides to properly manage log levels for this module, addressing an issue where verbose messages could not be suppressed.
• Code Consistency: Aligned logging practices in apache_beam.transforms.util with other modules like apache_beam.transforms.core for better consistency.

🧠 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.

Changelog

• sdks/python/apache_beam/transforms/util.py
  • Added a module-level named logger _LOGGER.
  • Replaced all instances of logging.info, logging.warning, logging.debug, logging.error, and logging.critical with their _LOGGER equivalents.

Activity

• Addressed issue [Bug]: sdk_harness_log_level_overrides not applied because root logger instead of named logger is being used #37833.
• Confirmed that tests are not needed due to no logic change.
• Confirmed that documentation updates are not needed.

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.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

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. ↩

[github-actions]

Assigning reviewers:

R: @damccorm for label python.

Note: If you would like to opt out of this review, comment assign to next reviewer.

Available commands:

• stop reviewer notifications - opt out of the automated review tooling
• remind me after tests pass - tag the comment author after tests pass
• waiting on author - shift the attention set back to the author (any comment or push by the author will return the attention set to the reviewers)

The PR bot will only process comments in the main thread (not review comments).