-
Notifications
You must be signed in to change notification settings - Fork 867
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
fix: Specify content length for gcp copy request #3921
Conversation
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.
FWIW this was originally included in https://github.com/apache/arrow-rs/pull/3236/files/2033d5aba91a15bda5d5f7d5f5151e96ac99a2f8#r1037123180 but was reverted as I couldn't find a way to reproduce it
Thank you for debugging this, I can reproduce this locally, wild 😅 |
Co-authored-by: Raphael Taylor-Davies <1781103+tustvold@users.noreply.github.com>
Yeah we were quite confused too. Still don't know why that happens though... |
Might be worth raising an issue on reqwest to see if they have any ideas what might be causing it |
Which issue does this PR close?
N/A
This fixes an issue where copy requests for the GCS object store would error due to a missing
content-length
header.Rationale for this change
We hit "Error 411 (Length Required)" on the copyTo endpoint when calling
copy_if_not_exists
for the GCS object store.An example error response that we get:
Getting a reproducible test case for this has been incredibly tricky. We believe that it comes down to whether or not the
object_store
crate gets compiled withnative-tls
orrust-tls
. See https://github.com/RustomMS/test-object-store for our best shot at reproducing.I also believe that this change would fix this issue delta-io/delta-rs#878.
What changes are included in this PR?
Explicitly sets content-length to 0 for GCS copyTo request.
Are there any user-facing changes?
No.