Eliaaazzz commented on code in PR #39580: URL: https://github.com/apache/beam/pull/39580#discussion_r3717134065
########## contributor-docs/local-flink-python.md: ########## @@ -0,0 +1,204 @@ +<!-- +Licensed under the Apache License, Version 2.0 (the "License"); +you may not use this file except in compliance with the License. +You may obtain a copy of the License at + +http://www.apache.org/licenses/LICENSE-2.0 + +Unless required by applicable law or agreed to in writing, software +distributed under the License is distributed on an "AS IS" BASIS, +WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. +See the License for the specific language governing permissions and +limitations under the License. +--> + +# Running Python pipelines on a local Flink cluster + +This guide describes a contributor workflow for validating Python Beam pipelines +against a real local Flink standalone cluster. It is useful when embedded Flink +is not enough, for example when validating streaming source behavior, checkpoint +boundaries, or runner-visible job state in the Flink dashboard. + +The commands assume a Unix shell (Linux, macOS, or WSL2 on Windows) with `curl`, +`tar`, and `java` on the `PATH`. + +* [What this setup validates](#what-this-setup-validates) +* [Prerequisites](#prerequisites) +* [Start a local Flink cluster](#start-a-local-flink-cluster) +* [Run a Beam Python pipeline](#run-a-beam-python-pipeline) +* [Troubleshooting](#troubleshooting) +* [Stop the cluster](#stop-the-cluster) + +## What this setup validates + +This setup runs three separate processes: Review Comment: You are right, the cluster already has separate JobManager and TaskManager processes and LOOPBACK runs in the submitting Python process. Changed it to three components. Thanks for the review. -- 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]
