goanpeca opened a new pull request, #19424: URL: https://github.com/apache/hudi/pull/19424
### Describe the issue this Pull Request addresses The AWS S3 page documents the `fs.s3a.*` settings for Amazon S3 but does not say that the same Hadoop S3A connector settings also work against other S3-compatible object stores. Readers pointing Hudi at a non-AWS S3 endpoint currently have to infer that `fs.s3a.endpoint` and `fs.s3a.path.style.access` are the two knobs they need. ### Summary and Changelog Adds one short paragraph to the AWS S3 page, right after the `core-site.xml` config block, noting that because Hudi reads and writes through the Hadoop S3A connector the same `fs.s3a.*` settings target Amazon S3 as well as other S3-compatible object stores (Backblaze B2, Cloudflare R2, and MinIO are listed as examples), and that a non-AWS provider needs `fs.s3a.endpoint` set to that provider's endpoint plus `fs.s3a.path.style.access` left at `true` where path-style addressing is required. Detailed changelog: - `website/docs/s3_hoodie.md`: two added lines (one paragraph plus a blank line). No existing prose, code block, or front matter was changed. The endpoint in the example is a placeholder, not a real host. One open item: `last_modified_at` in that page's front matter still reads its original 2019 value. Say the word if docs edits are expected to bump it and I will fold that in. ### Impact Documentation only. No public API, config, behavior, or performance change. ### Risk Level none ### Documentation Update This PR is the documentation update. No new feature or config is introduced, so no further docs changes are needed. ### Contributor's checklist - [x] Read through [contributor's guide](https://hudi.apache.org/contribute/how-to-contribute) - [x] Enough context is provided in the sections above - [ ] Adequate tests were added if applicable This change was drafted with AI assistance and reviewed by me before submission. -- 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]
