Skip to content

Merge upstream 20260213 v2#50

Merged
gbrgr merged 6 commits intomainfrom
gb/merge-upstream-20260213-v2
Feb 13, 2026
Merged

Merge upstream 20260213 v2#50
gbrgr merged 6 commits intomainfrom
gb/merge-upstream-20260213-v2

Conversation

@gbrgr
Copy link
Copy Markdown
Collaborator

@gbrgr gbrgr commented Feb 13, 2026

Which issue does this PR close?

  • Closes #.

What changes are included in this PR?

Are these changes tested?

blackmwk and others added 6 commits February 9, 2026 18:50
…2109)

## Which issue does this PR close?

- Closes #.

## What changes are included in this PR?
- Add a new module `storage` within `io` and put traits there

## Are these changes tested?
Relying on the existing tests
apache#2115)

## Which issue does this PR close?

AWS
[Docs](https://docs.aws.amazon.com/AmazonS3/latest/userguide/s3-tables-tables.html)
state:


> When you create a table, Amazon S3 automatically generates a warehouse
location for the table. This is a unique S3 location that stores objects
associated with the table. The following example shows the format of a
warehouse location:

```
s3://63a8e430-6e0b-46f5-k833abtwr6s8tmtsycedn8s4yc3xhuse1b--table-s3
```

We were previously interpreting this as as a metadata location (i.e. the
path to the metadata.json file), this changes the code use it as a table
location.

- Closes apache#2114

## What changes are included in this PR?

Change how we construct the MetadataLocation object.

## Are these changes tested?

There never appears to have been a test, and I don't have an AWS account
to verify this. Note the test was initially developed by Claude Code and
refined by me.
Starting with the current main branch state and integrating upstream changes
while preserving our fork's enhancements.
@gbrgr gbrgr changed the title Gb/merge upstream 20260213 v2 Merge upstream 20260213 v2 Feb 13, 2026
@gbrgr gbrgr marked this pull request as ready for review February 13, 2026 12:48
@gbrgr gbrgr merged commit c4598e0 into main Feb 13, 2026
2 checks passed
@gbrgr gbrgr deleted the gb/merge-upstream-20260213-v2 branch February 13, 2026 12:48
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.

5 participants