-
Notifications
You must be signed in to change notification settings - Fork 701
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
deltalake.PyDeltaTableError: Failed to read delta log object: Generic S3 error: Missing region #2308
Comments
When using S3, DeltaTable requires AWS specific storage options. We attempt to pass some based on the boto3 session but the AWS region is not one of them. IMO this issue is better addressed by the delta lake team, so will reference it there. |
Sounds good, maybe we can add this to doc somewhere? I need to read through code to figure out what argument I need to pass in to add region information. |
Hi - coming from the issue in delta-rs to get some context :). I seem to remember that we were discussing if we should just default to I do also vaguely remember reading some docs somewhere, that this is no longer a recommended value to take as the default region, since the number of regions grew significantly, but I may also be completely off .. Do you know if there is a reasonable default for a region parameter that will serve most users? Otherwise I would think that choosing some more arbitrary default region is likely not something we would want to adopt, and one would just have to live with passing it in as a parameter 😄. |
Yeah I agree, passing in a default parameter might not be a good choice at this moment. We should provide an instruction on how to pass region in the |
absolutely do! |
@isunli and @roeap, I believe I understand the underlying issue a bit better after some testing. In short this is due to the difference between how boto3 and the deltalake packages obtain the AWS region information. In Correct me if I am wrong @roeap, but the deltalake package only looks at the OS env variables, but not the .aws/config file.
and it raised: After setting the I see three options here:
We can easily implement #2 on our end, but the underlying issue won't be fixed in the deltalake package |
just realized that in the object store 0.6.1 release, reading the region from the profile is fixed, and with that also available in deltalake, once we updated. Nut sure if that would have implications here, since boto3 gets the information from the same source? |
With the PR fix we would always pass |
I am querying an delta table from sagemaker notebook. If I use all default argument like
Then it will return following error message:
version I am using:
EDIT:
following works, I need to set aws region manually
The text was updated successfully, but these errors were encountered: