You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Improve error handling on S3 HEAD requests. (TileDB-Inc#5380)
[SC-59519](https://app.shortcut.com/tiledb-inc/story/59519/s3-is-object-masks-failures)
[SC-59575](https://app.shortcut.com/tiledb-inc/story/59575/improve-error-message-when-headobject-fails-with-status-301)
* In `S3::is_object` we return that the object does not exist if the
`HeadObject` API call fails for any reason (like unauthorized or wrong
region). This PR changes to return `false` only if `HeadObject` fails
with a 404 status, and return the failure to the user in other cases.
* Azure and GCS already do that.
* In S3 operations that perform `HeadObject` (`is_object` and
`object_size`), if the operation returns a 301 (Permanent Redirect)
status, we add an explanatory note to the error message suggesting that
the configured region might be incorrect. This will be helpful because
while most operations return a detailed error message, `HeadObject`
cannot have a response body.
---
TYPE: BUG
DESC: Fixed `tiledb_vfs_is_file` masking failures on S3 by returning
false.
---
TYPE: IMPROVEMENT
DESC: Added additional context in the error messages of operations that
likely failed due to region mismatch.
0 commit comments