bharathgunapati opened a new pull request, #29437: URL: https://github.com/apache/flink/pull/29437
## What is the purpose of the change The HTTP connector 1.0 documentation is already knitted into Flink master (`integrate_connector_docs http v1.0` in `docs/setup_docs.sh`, via #28508). The stable Flink 2 docs are built from `release-2.3`, and that branch does not pull the connector docs in, so https://nightlies.apache.org/flink/flink-docs-stable/docs/connectors/table/http/ 404s. This backports the same one-line docs wiring onto `release-2.3`. ## Brief change log - Call `integrate_connector_docs http v1.0` from `docs/setup_docs.sh` on `release-2.3`, matching master. ## Verifying this change This change is a trivial documentation build wiring change without test coverage. After the nightly docs build, the HTTP connector pages should be served under the Flink 2.3 docs: - `docs/connectors/table/http/` - `docs/connectors/datastream/http/` `release-2.2` already has the same change proposed in #28509. ## 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: JobManager (and its components), Checkpointing, Kubernetes/Yarn, ZooKeeper: no - The S3 file system connector: no ## Documentation - Does this pull request introduce a new feature? no - If yes, how is the feature documented? not applicable This pull request publishes the existing HTTP connector 1.0 documentation in the Flink 2.3 docs build. --- ##### Was generative AI tooling used to co-author this PR? - [x] Yes (please specify the tool below) Generated-by: Cursor Grok 4.7 -- 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]
