Skip to content

Fix OnWindowExpirationContext. - #38878

Merged
reuvenlax merged 3 commits into
apache:masterfrom
reuvenlax:implement_on_window_expiration_context
Jun 9, 2026
Merged

Fix OnWindowExpirationContext.#38878
reuvenlax merged 3 commits into
apache:masterfrom
reuvenlax:implement_on_window_expiration_context

Conversation

@reuvenlax

Copy link
Copy Markdown
Contributor

addresses #38875

@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 introduces support for the OnWindowExpirationContext parameter within Apache Beam's DoFn framework. By updating the reflection-based invoker factory and signature validation logic, it enables users to access context-specific information during window expiration events, improving the flexibility of stateful processing.

Highlights

  • Support for OnWindowExpirationContext: Added support for OnWindowExpirationContext as a parameter in DoFn methods, allowing access to window expiration information.
  • Infrastructure Updates: Updated ByteBuddyDoFnInvokerFactory, DoFnInvoker, and DoFnSignature to handle the new parameter type across the reflection and invocation layers.
  • Test Coverage: Updated ParDoTest and DoFnSignaturesTest to verify the correct injection and signature validation of OnWindowExpirationContext.
New Features

🧠 You can now enable Memory (public preview) 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 the 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 counterproductive. 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.

@github-actions github-actions Bot added the java label Jun 9, 2026
@reuvenlax

Copy link
Copy Markdown
Contributor Author

R: @ahmedabu98

@github-actions

github-actions Bot commented Jun 9, 2026

Copy link
Copy Markdown
Contributor

Stopping reviewer notifications for this pull request: review requested by someone other than the bot, ceding control. If you'd like to restart, comment assign set of reviewers

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

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.

Code Review

This pull request introduces support for the OnWindowExpirationContext parameter in @OnWindowExpiration methods of DoFn. It updates the reflection and code generation utilities, including ByteBuddyDoFnInvokerFactory, DoFnInvoker, and DoFnSignatures, to recognize, dispatch, and supply this parameter, and adds corresponding unit tests. There are no review comments, so I have no feedback to provide.

Important

The consumer version of Gemini Code Assist on GitHub is being sunset. Starting June 18, 2026, new organization installations will be blocked, and all code review activity will officially cease on July 17, 2026.
For more details on the timeline and next steps, please review the Help Documentation.

@reuvenlax

Copy link
Copy Markdown
Contributor Author

/gemini review

@reuvenlax
reuvenlax requested a review from ahmedabu98 June 9, 2026 19:54

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

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.

Code Review

This pull request adds support for the OnWindowExpirationContext parameter in @OnWindowExpiration methods of DoFn across runners, signature parsing, and invoker generation. The feedback suggests using JUnit's assertNotNull instead of Guava's Preconditions.checkNotNull in the unit tests to ensure idiomatic assertions and clearer test failures.

Important

The consumer version of Gemini Code Assist on GitHub is being sunset. Starting June 18, 2026, new organization installations will be blocked, and all code review activity will officially cease on July 17, 2026.
For more details on the timeline and next steps, please review the Help Documentation.

Integer currentValue = MoreObjects.firstNonNull(state.read(), 0);
// verify state
assertEquals(1, (int) currentValue);
Preconditions.checkNotNull(context);

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

In unit tests, it is more idiomatic to use JUnit's assertNotNull instead of Guava's Preconditions.checkNotNull. Preconditions.checkNotNull throws a NullPointerException (which JUnit treats as an unexpected error), whereas assertNotNull throws an AssertionError (which JUnit treats as a test failure), providing better integration with test runners and clearer test results.

Suggested change
Preconditions.checkNotNull(context);
assertNotNull(context);

@reuvenlax
reuvenlax merged commit a3cb642 into apache:master Jun 9, 2026
35 of 36 checks passed
ash6898 pushed a commit to ash6898/beam that referenced this pull request Jun 29, 2026
* foo

* fix compilation

* fix compilation
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