goanpeca opened a new pull request, #19423: URL: https://github.com/apache/hudi/pull/19423
### Describe the issue this Pull Request addresses The `hudi-notebooks` Docker Compose environment ships MinIO as its object store, and the README only documents that setup. Nothing states that the storage layer is the Hadoop S3A connector, so it is not obvious that the same environment can point at Amazon S3 or any other S3-compatible store by changing configuration, or which settings need to change. ### Summary and Changelog Docs-only addition to `hudi-notebooks/README.md`, as a new "Using another S3-compatible object store" subsection under Configuration: - state that reads and writes go through the Hadoop S3A connector, so the same `fs.s3a.*` settings apply to Amazon S3 or a compatible provider (Backblaze B2, Cloudflare R2, MinIO) - point to `conf/hadoop/core-site.xml` and the matching Spark/Hive configs as the files to edit, with a placeholder `fs.s3a.endpoint` / access key / secret key / `path.style.access` snippet - note that Amazon S3 uses the region-default endpoint when `fs.s3a.endpoint` is omitted, while most other providers need an explicit endpoint and `fs.s3a.path.style.access=true` ### Impact None. Documentation only, no code, config, or behavior changes. The bundled demo still defaults to MinIO. ### Risk Level none ### Documentation Update This PR is itself the documentation update; only `hudi-notebooks/README.md` changes. No website update is needed since no new feature or configuration is introduced. ### 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 (not applicable; documentation-only change) -- 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]
