Skip to content

fix(s3tables): use 's3' as the default scheme#2313

Open
rchowell wants to merge 1 commit intoapache:mainfrom
rchowell:s3
Open

fix(s3tables): use 's3' as the default scheme#2313
rchowell wants to merge 1 commit intoapache:mainfrom
rchowell:s3

Conversation

@rchowell
Copy link
Copy Markdown

@rchowell rchowell commented Apr 2, 2026

Which issue does this PR close?

What changes are included in this PR?

Changes the s3tables default scheme to "s3://"

Are these changes tested?

With this change, I can read files resolved through an s3table catalog now.

@xanderbailey
Copy link
Copy Markdown
Contributor

Looks like Java uses s3: as the default https://github.com/apache/iceberg/blob/main/aws/src/main/java/org/apache/iceberg/aws/s3/S3FileIO.java

Copy link
Copy Markdown

@dannycjones dannycjones left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I believe this is the right change to make. It aligns with the Java catalog and with pre-0.9 behavior.

I'd like to try some testing of the following before a +1 here:

  • Trying to create a table or write to a table using 0.9
  • Then trying to read that table from this change.

I want to be more confident that we don't break anyone on 0.9.

Copy link
Copy Markdown

@dannycjones dannycjones left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM, tested this catalog (#2315) to verify it doesn't work at the moment so there shouldn't be anyone impacted upgrading from 0.9.0.

@rchowell
Copy link
Copy Markdown
Author

rchowell commented Apr 6, 2026

Thanks @dannycjones and @xanderbailey for checking this.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Unable to read S3 Tables due to incorrect URL scheme

4 participants