Commit 28df4ec
authored
fix: Interpret s3tables warehouse as table_location not metadata loca… (#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 #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.1 parent 7c2d5d1 commit 28df4ec
1 file changed
Lines changed: 6 additions & 5 deletions
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
448 | 448 | | |
449 | 449 | | |
450 | 450 | | |
451 | | - | |
| 451 | + | |
452 | 452 | | |
453 | | - | |
| 453 | + | |
454 | 454 | | |
455 | 455 | | |
456 | 456 | | |
| |||
467 | 467 | | |
468 | 468 | | |
469 | 469 | | |
470 | | - | |
471 | | - | |
| 470 | + | |
472 | 471 | | |
473 | 472 | | |
474 | 473 | | |
475 | 474 | | |
476 | | - | |
| 475 | + | |
477 | 476 | | |
478 | 477 | | |
479 | 478 | | |
| 479 | + | |
| 480 | + | |
480 | 481 | | |
481 | 482 | | |
482 | 483 | | |
| |||
0 commit comments