MartijnVisser opened a new pull request, #28567:
URL: https://github.com/apache/flink/pull/28567
## What is the purpose of the change
Documents how to run the S3 end-to-end tests, which was previously
undocumented (the `IT_CASE_S3_*` environment variables only appeared inside the
shell scripts). The new "Testing against S3" section in
`flink-end-to-end-tests/README.md`:
- distinguishes the two mechanisms: tests that run against a **real S3
bucket** (source `common_s3.sh`, require
`IT_CASE_S3_BUCKET/ACCESS_KEY/SECRET_KEY`, and are silently skipped when those
are unset) versus tests that start a **local SeaweedFS S3 gateway in Docker**
(source `common_s3_seaweedfs.sh`, need Docker but no AWS credentials);
- lists the concrete `run-single-test.sh` commands for each;
- clarifies the existing `<flink dir>` placeholder (e.g. `build-target`
after building from source).
Docs-only change, hence submitted as a `[hotfix]`.
## Brief change log
- Add a "Testing against S3" subsection to
`flink-end-to-end-tests/README.md` and clarify the `<flink dir>` placeholder.
## Verifying this change
This change is a trivial documentation update without any test coverage.
## Does this pull request potentially affect one of the following parts:
- Dependencies (does it add or upgrade a dependency): no
- The public API, i.e., is any changed class annotated with
`@Public(Evolving)`: no
- The serializers: no
- The runtime per-record code paths (performance sensitive): no
- Anything that affects deployment or recovery: no
- The S3 file system connector: no
## Documentation
- Does this pull request introduce a new feature? no
---
##### Was generative AI tooling used to co-author this PR?
- [X] Yes (Claude Code, Opus 4.8)
Generated-by: Claude Code (Opus 4.8)
--
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]
