-
Notifications
You must be signed in to change notification settings - Fork 3.6k
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
GH-35879: [C++] Bump bundled google-cloud-cpp to 2.12.0 #36119
Conversation
|
@coryan If we update bundled google-cloud-cpp to 2.12.0 from 2.8.0, our GCSFS tests are failed with "missing project id error": https://github.com/apache/arrow/actions/runs/5287300615/jobs/9567623572?pr=36119#step:11:223
Do we need to update our GCSFS? |
We need to update the tests. The client library now performs more validation, and the testbench is too forgiving. The test used to get away with a request that would have failed against production. We need to set the GOOGLE_CLOUD_PROJECT environment variable to some value good for testing. Alternatively, we need to expand the GCSFS configuration to accept the project id as one of the (optional) parameters and use that in the test. Should I send a separate PR or should we try to add these changes to this PR? |
Thanks!
If specifying the project ID from API is useful for Apache Arrow users, how about choosing the alternative approach? If it's only useful for testing, the
Could you send a separate PR? I think that it's easier for you. It seems that this PR still has a static linking related problem: https://github.com/apache/arrow/actions/runs/5287582940/jobs/9568250982?pr=36119#step:5:3381
So I think that a PR without google-cloud-cpp update will be easy for you. |
No problem. Happy to do that.
Gladly. It may take me until Tuesday, I am not working on Monday.
Ugh, it can be hard to debug the little library dependencies in Abseil. Good luck!
Sounds good, I will give it a try. |
Thanks!
No problem. |
5ef0e24
to
ac35574
Compare
It seems that the static linking problem is solved. |
You may have noticed, I created a PR to help with the problems here. |
### Rationale for this change This fixes #36227, originally motivated by the problems in #36119, but seems like a valuable feature in any case. ### What changes are included in this PR? - Refactor some code to make it testable. - Add a new `std::optional<std::string>` field to the `GcsOptions` class. ### Are these changes tested? Yes, I expanded the unit tests. ### Are there any user-facing changes? Yes. I updated the field documentation. If I missed some documentation please let me know. I am also not familiar with the steps required to update the Python wrappers, if there is some documentation to follow I would appreciate it. I can expand this PR or send a separate one, your call. * Closes: #36227 Authored-by: Carlos O'Ryan <coryan@google.com> Signed-off-by: Sutou Kouhei <kou@clear-code.com>
7ed1805
to
dc2c7b5
Compare
GH-36228 is merged and I've rebased on main. |
Quick reminder to also upload the new version to our artifactory! |
Oh. I forgot it. Thanks! |
6a26e76
to
a30087e
Compare
4edcebf
to
e36a091
Compare
+1 @paleolimbot @thisisnic This pull request changes the R part a bit. Could you review it? See also the context: #36228 |
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.
Thank you for updating the R bits! I can't spot anything that wouldn't have been caught by the tests.
Thanks! |
I am unsure if there's something else to be done but it seems the nightlies for: Failed with:
Is there something else to be done? Should I create a new issue for those failures? |
I probably missed making changes for Python in #36228. I do not know where to start with these changes, if somebody can point me to the right documentation, I will give it a shot. |
Hi @coryan ! |
Conbench analyzed the 6 benchmark runs on commit There were 7 benchmark results indicating a performance regression:
The full Conbench report has more details. |
Rationale for this change
The version will fix #35318.
What changes are included in this PR?
Use the latest released version.
Are these changes tested?
Yes.
Are there any user-facing changes?
Yes.