[WIP] NOT FOR MERGE

[arunpandianp]

No description provided.

[gemini-code-assist]

Summary of Changes

Hello @arunpandianp, 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 is a work in progress, marked as 'NOT FOR MERGE', and focuses on implementing a new version of Windmill tag encoding (V2) for Apache Beam's Dataflow runner. The primary goal of this new encoding is to establish a specific lexicographical order for state and timer tags, which is essential for optimizing range-based queries. The changes involve core API modifications, the introduction of the new encoding logic, and updates to the Dataflow worker to allow conditional activation of this feature through an experiment flag.

Highlights

• New Windmill Tag Encoding (V2): Introduced WindmillTagEncodingV2 to provide a new, lexicographically ordered encoding scheme for state and timer tags in Apache Beam's Dataflow runner. This new encoding facilitates efficient range filtering of tags.
• Conditional Activation via Experiment Flag: The WindmillTagEncodingV2 can be enabled in the Dataflow worker via an unstable_windmill_tag_encoding_v2 experiment flag, allowing for controlled rollout and testing of the new encoding.
• API Updates for Tag Encoding: Modified StateNamespaces, StateTags, and WindmillTagEncoding interfaces/classes to support the new encoding, including adding methods to retrieve window coders and check for system tags, and updating the timerHoldTag signature.
• Comprehensive Testing: Added a dedicated test suite (WindmillTagEncodingV2Test) to thoroughly validate the encoding and decoding logic, as well as the enforced lexicographical sort order for various tag types and namespaces.

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

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