athenawemmert opened a new pull request, #4166:
URL: https://github.com/apache/iceberg-python/pull/4166
<!--
Thanks for opening a pull request!
-->
<!-- In the case this PR will resolve an issue, please replace
${GITHUB_ISSUE_ID} below with the actual Github issue id. -->
<!-- Closes #${GITHUB_ISSUE_ID} -->
# Rationale for this change
The configuration docs reach Amazon S3 Tables only through the AWS Glue
example (`s3tablescatalog` warehouse). Connecting PyIceberg straight to the S3
Tables Iceberg REST endpoint needs two non-default keys that are easy to miss:
the warehouse is the table bucket ARN, and `rest.signing-name` must be
`s3tables` (PyIceberg defaults to `execute-api`).
This adds an `Amazon S3 Tables` entry under "Common Integrations &
Examples", next to AWS Glue, in the same shape as the other REST integrations:
a link to the AWS docs and the catalog YAML.
## Are these changes tested?
Docs only. I used this configuration against a real S3 Tables table bucket
in us-west-2 with PyIceberg 0.12.0 (`pyiceberg[pyarrow,rest-sigv4]`): create
namespace, create table, append, and scan all succeeded, with requests signed
for `s3tables`. markdownlint and codespell pass, and `mkdocs build --strict`
succeeds.
I used an AI assistant to draft the section and the test harness, then
reviewed the text and checked each key against the AWS docs, the PyIceberg
source, and the live run. I only tested us-west-2.
## Are there any user-facing changes?
Documentation only.
<!-- In the case of user-facing changes, please add the changelog label. -->
--
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]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
