Skip to content

Fix #37894: Update yaml doc for composite transform changes#37901

Open
liferoad wants to merge 3 commits intomasterfrom
fix/beam-37894-yaml-composite-doc
Open

Fix #37894: Update yaml doc for composite transform changes#37901
liferoad wants to merge 3 commits intomasterfrom
fix/beam-37894-yaml-composite-doc

Conversation

@liferoad
Copy link
Contributor

@liferoad liferoad commented Mar 21, 2026

Issue: #37894

This PR updates the YAML documentation to reflect the implicit input chaining feature for composite transforms (introduced in PR #37861).

Changes

  • Added new section "Implicit Input Chaining for Composite Transforms" to yaml-schema.md
  • Documented that composite transforms can now omit explicit input specifications on sub-transforms
  • Added examples showing implicit chaining vs explicit chaining

Testing

  • Documentation only change, no code changes

liferoad added 3 commits March 13, 2026 20:04
@liferoad
Fix #37833: Use named logger instead of root logger in transforms/uti…
4115761 
…l.py

Replace root logger calls (logging.info, logging.warning, etc.) with a
module-level named logger (_LOGGER = logging.getLogger(__name__)) in
apache_beam.transforms.util. This allows sdk_harness_log_level_overrides
to properly control log levels for this module.
@liferoad
Merge branch 'apache:master' into master
c600ed6
@liferoad
Update yaml-schema.md with implicit input chaining documentation
1403781
@gemini-code-assist
Copy link
Contributor

gemini-code-assist bot commented Mar 21, 2026

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 enhances the YAML documentation to accurately describe the recently introduced implicit input chaining capability for composite transforms. It clarifies how sub-transforms can automatically connect without explicit input declarations, improving the readability and conciseness of pipeline definitions.

Highlights

  • Documentation Update: Updated the YAML documentation to reflect the new implicit input chaining feature for composite transforms.
  • New Section Added: Introduced a new section titled "Implicit Input Chaining for Composite Transforms" in yaml-schema.md.
  • Feature Explanation: Documented that sub-transforms within a composite transform can now omit explicit input specifications, automatically chaining them.
  • Examples Provided: Included examples illustrating both implicit and explicit chaining for composite transforms.

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

@liferoad liferoad requested a review from derrickaw March 21, 2026 13:33
@github-actions
Copy link
Contributor

github-actions bot commented Mar 21, 2026

Assigning reviewers:

R: @kennknowles for label website.

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

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

Reviewers

1 more reviewer

@derrickaw derrickaw derrickaw approved these changes

Reviewers whose approvals may not affect merge requirements

Assignees

No one assigned

Labels

Next Action: Reviewers website

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

2 participants

@liferoad @derrickaw