-
Notifications
You must be signed in to change notification settings - Fork 1.1k
[DO NOT MERGE] Validate Beam 2.69.0rc1 #2892
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
Summary of ChangesHello @Amar3tto, 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 is a "DO NOT MERGE" validation PR aimed at testing compatibility with the upcoming Apache Beam "2.69.0rc1" release. It involves updating the Beam version in the project's Maven "pom.xml" and all relevant Python dependency files ("default_base_python_requirements.txt", "default_base_yaml_requirements.txt", "base_requirements.txt", and "requirements.txt"). Additionally, the Maven profile activation for "validateCandidate" has been adjusted, and a new Python dependency, "google-cloud-secret-manager", has been introduced. The changes ensure the project can build and run with the new Beam release candidate, facilitating early detection of potential issues. Highlights
Using Gemini Code AssistThe 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
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 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
|
Codecov Report❌ Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## main #2892 +/- ##
============================================
- Coverage 50.06% 49.97% -0.09%
- Complexity 4967 5345 +378
============================================
Files 967 967
Lines 59298 59312 +14
Branches 6441 6442 +1
============================================
- Hits 29688 29642 -46
- Misses 27505 27567 +62
+ Partials 2105 2103 -2
🚀 New features to boost your workflow:
|
|
The reason is customGcsTempLocation parameter, which is bigQueryLoadingTemporaryDirectory in DataflowTemplates. We need to set it during staging |
This sounds a upstream breaking change. Any clue why "bigQueryLoadingTemporaryDirectory" becomes needed in Beam 2.69.0 ? checked that the check in Beam has always been there though: https://github.com/apache/beam/blob/af748d07a1a7ca244ff057554d68932c014d5eeb/sdks/java/io/google-cloud-platform/src/main/java/org/apache/beam/sdk/io/gcp/bigquery/BigQueryIO.java#L3100 |
It only relates to staging, I think it is because of apache/beam#36209. ( |
|
Thanks @Amar3tto, we should fix #36209 to (customGcsTempLocation.isAccessible() && customGcsTempLocation.get() == null). This essentially breaks BigQueryIO for runtime ValueProvider |
|
a good news is Python xlang template tests, used to fail on RC validations, now working after apache/beam#36199 |
No description provided.