carloea2 opened a new issue, #8261: URL: https://github.com/apache/texera/issues/8261
### What happened? `LargeBinaryManager._ensure_bucket_exists` only catches the modeled `NoSuchBucket` exception. S3 `HeadBucket` reports a missing bucket as a generic `ClientError` with a 404 code, so Texera propagates the error and never creates the bucket needed for the first large binary upload. Before: a 404 from `HeadBucket` aborts bucket setup. Expected: missing-bucket responses create the bucket, while other S3 errors still propagate. ### How to reproduce? 1. Configure an S3 client whose `HeadBucket` response is HTTP 404. 2. Call `_ensure_bucket_exists` for that bucket. 3. Observe a botocore `ClientError` and no `CreateBucket` request. ### Version or branch 1.3.0-incubating-SNAPSHOT on main ### Commit hash 50321e403c82df299a13deb50a7f9849dd93bdba ### Relevant log output botocore.exceptions.ClientError: An error occurred (404) when calling the HeadBucket operation: Not Found -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
