Skip to content

Conversation

@daiyy
Copy link
Contributor

@daiyy daiyy commented Aug 8, 2025

Which issue does this PR close?

What changes are included in this PR?

As S3Tables REST endpoint accept warehouse only in ARN format,
Current code logic will infer file io scheme through warehouse_path in ARN format as arn which is wrong and unable to be processed.

Changed the code logic to try infer file io scheme with metadata_location before warehouse_path,
This makes file io scheme infer as s3 correctly.

Are these changes tested?

Test only in load_table path for rest catalog implementation

Copy link
Contributor

@liurenjie1024 liurenjie1024 left a comment

Choose a reason for hiding this comment

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

Thanks @daiyy for this pr!

@liurenjie1024 liurenjie1024 merged commit 292304b into apache:main Aug 8, 2025
17 checks passed
Yiyang-C pushed a commit to Yiyang-C/iceberg-rust that referenced this pull request Aug 26, 2025
…th (apache#1590)

## Which issue does this PR close?

- Closes apache#1589

## What changes are included in this PR?

As S3Tables REST endpoint accept `warehouse` only in ARN format,
Current code logic will infer file io scheme through `warehouse_path` in
ARN format as `arn` which is wrong and unable to be processed.

Changed the code logic to try infer file io scheme with
`metadata_location` before `warehouse_path`,
This makes file io scheme infer as `s3` correctly.

## Are these changes tested?

Test only in `load_table` path for rest catalog implementation
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 identify correct file io scheme for AWS S3Tables through REST endpoint

2 participants