Skip to content

Conversation

@ahmedabu98
Copy link
Contributor

@ahmedabu98 ahmedabu98 commented Sep 8, 2025

Fixes #32603

Avro was upgraded in iceberg module in #35981, but IO expansion service pins it to 1.11.4, causing a problem for Python/YAML pipelines

Copy link
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.

Summary of Changes

Hello @ahmedabu98, 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 addresses a critical dependency conflict by updating the Avro version used within the expansion service. The change ensures compatibility with other project modules, specifically Iceberg, which relies on a different Avro version. This resolution is vital for maintaining the stability and correct functioning of Python and YAML-based data processing pipelines.

Highlights

  • Avro Version Pinning: The Avro dependency in the expansion-service has been explicitly pinned to version 1.12.0. This change is crucial for resolving a version conflict with the iceberg module, which requires this specific Avro version, and addresses reported issues affecting Python/YAML pipelines.
  • Test Suite Trigger: A minor, trivial modification was made to the .github/trigger_files/beam_PostCommit_Python_Xlang_IO_Direct.json file. This change serves solely to trigger the associated beam_PostCommit_Python_Xlang_IO_Direct test suite, ensuring comprehensive testing of the updated dependency.
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 in your pull request via creating an issue comment (i.e. comment on the pull request page) using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands.

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

@ahmedabu98
Copy link
Contributor Author

R: @liferoad
R: @Amar3tto

@github-actions
Copy link
Contributor

github-actions bot commented Sep 8, 2025

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

@chamikaramj
Copy link
Contributor

LGTM

// cannot upgrade this to the latest version due to https://github.com/apache/beam/issues/34993
resolutionStrategy.force 'org.apache.avro:avro:1.11.4'
// iceberg needs avro:1.12.0
resolutionStrategy.force 'org.apache.avro:avro:1.12.0'
Copy link
Contributor

@liferoad liferoad Sep 8, 2025

Choose a reason for hiding this comment

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

Apache Avro 1.12.0 does not support Java 8. Will this cause the issue for our expansion service?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

We already worked through this when upgrading Iceberg (which also drops Java 8). Note we specify requireJavaVersion: JavaVersion.VERSION_11 at the top

Copy link
Contributor

Choose a reason for hiding this comment

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

Expansion service container already uses Java 11. So this should not be an issue.

@liferoad liferoad requested a review from Abacn September 8, 2025 23:09
@chamikaramj
Copy link
Contributor

Note that this also results in Iceberg failing for Dataflow Java.

Copy link
Contributor

@Abacn Abacn left a comment

Choose a reason for hiding this comment

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

Thank you!

@liferoad
Copy link
Contributor

liferoad commented Sep 8, 2025

fixes #34993

@ahmedabu98 ahmedabu98 merged commit a2f9fb8 into apache:master Sep 9, 2025
24 checks passed
@ahmedabu98
Copy link
Contributor Author

It doesn't fix #34993 just yet. We'd need to update avro in BeamModulePlugin to have all of Beam use avro 1.12.0:

// TODO: https://github.com/apache/beam/issues/34993 after stopping supporting Java 8
avro : "org.apache.avro:avro:1.11.4",

ahmedabu98 added a commit to ahmedabu98/beam that referenced this pull request Sep 9, 2025
Amar3tto added a commit that referenced this pull request Sep 9, 2025
Cherry-picking #36092 into release branch
ahmedabu98 added a commit that referenced this pull request Sep 10, 2025
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.

The PreCommit YAML Xlang Direct job is perma-red

4 participants