-
Notifications
You must be signed in to change notification settings - Fork 256
[Backport Fix to branch-3.1.x]: Prevent Hadoop directory copy failures by correctly setting generation id Preconditions #1463
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
dheerajsngh
commented
Aug 25, 2025
- Origin PR/
…ration ID preconditions (#1363)
There was a problem hiding this 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 @dheerajsngh, 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 backports a critical fix to prevent Hadoop directory copy failures. The core issue stemmed from incorrect handling of Google Cloud Storage object generation IDs, specifically when a generation ID of 0 was being treated as a valid generation match precondition, leading to unexpected behavior. The changes ensure that generation ID preconditions are only applied when the generation ID is a positive value, aligning with how GCS handles object versions. Additionally, a minor tracing improvement was made to better track upload IDs.
Highlights
- Generation ID Handling: Modified GCS read channels to correctly apply generation ID preconditions only when the generation ID is a positive value, preventing issues with zero or null generation IDs.
- Tracing Improvement: Updated the GoogleCloudStorageClientGrpcTracingInterceptor to use a specific constant for uninitialized streamUploadId instead of null, improving clarity and robustness in tracing.
- Comprehensive Testing: Added new unit tests to explicitly verify that generation match preconditions are correctly applied (or not applied) based on the generation ID's value (positive vs. zero).
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
-
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. ↩
/gcbrun |
There was a problem hiding this comment.
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 backports a fix to prevent Hadoop directory copy failures by ensuring that an invalid generation ID (specifically 0) is not used as a precondition in GCS requests. The changes correctly add a check for a positive generation ID before using it in generationMatch
preconditions in both GoogleCloudStorageClientReadChannel
and GoogleCloudStorageReadChannel
. The logic is sound and the accompanying tests effectively verify the new behavior for both positive and zero generation IDs. The changes in GoogleCloudStorageClientGrpcTracingInterceptor
to use a constant instead of null
for streamUploadId
are also a good improvement for robustness. Overall, the changes are correct and well-implemented.
Codecov Report❌ Patch coverage is Additional details and impacted files@@ Coverage Diff @@
## branch-3.1.x #1463 +/- ##
===============================================
Coverage ? 82.72%
Complexity ? 2238
===============================================
Files ? 119
Lines ? 9864
Branches ? 1201
===============================================
Hits ? 8160
Misses ? 1207
Partials ? 497
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|