Fix Python Arm workflows

[Amar3tto]

Fixes #30760, #33065
Successful runs:
https://github.com/apache/beam/actions/runs/17045525888
https://github.com/apache/beam/actions/runs/17045530780

---

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

• Mention the appropriate issue in your description (for example: addresses #123), if applicable. This will automatically add a link to the pull request in the issue. If you would like the issue to automatically close on merging the pull request, comment fixes #<ISSUE NUMBER> instead.
• Update CHANGES.md with noteworthy changes.
• If this contribution is large, please file an Apache Individual Contributor License Agreement.

See the Contributor Guide for more tips on how to make review process smoother.

To check the build health, please visit https://github.com/apache/beam/blob/master/.test-infra/BUILD_STATUS.md

GitHub Actions Tests Status (on master branch)

See CI.md for more information about GitHub Actions CI or the workflows README to see a list of phrases to trigger workflows.

[gemini-code-assist]

Summary of Changes

Hello @Amar3tto, 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 updates Python dependency requirements across multiple Python versions (3.9-3.13) for both base and machine learning container images. Specifically, it replaces the 'milvus' package with 'milvus-lite' and 'pymilvus', and adds 'ujson'. These changes are intended to resolve issues with Python workflows on ARM architectures, as indicated by the PR title and linked successful CI runs.

Highlights

• Dependency Resolution: Replaced the 'milvus' package with 'milvus-lite' and 'pymilvus', and introduced 'ujson' in the Python 'requirements.txt' files.
• Multi-version Support: Applied these dependency updates consistently across Python versions 3.9, 3.10, 3.11, 3.12, and 3.13 for both base and machine learning container images.
• Workflow Stability: Addressed and fixed existing issues (#30760, #33065) related to Python ARM workflows, ensuring successful CI/CD runs.

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

[Abacn]

Thank you!

[Abacn]

requirements.txt are generated. The changes to them alone will gets overriden. Need to update setup.py then run ./gradlew :sdks:python:container:generatePythonRequirementsAll