weiqingy opened a new issue, #829: URL: https://github.com/apache/flink-agents/issues/829
### Background Raised during review of #722. The Python side currently has two execution paths behind `AgentsExecutionEnvironment.get_execution_environment()`: - **Local / in-process** — `LocalExecutionEnvironment` + `LocalRunner` (`python/flink_agents/runtime/local_execution_environment.py`, `python/flink_agents/runtime/local_runner.py`), selected when no Flink `StreamExecutionEnvironment` is passed (`env is None`). This is a pure-Python, single-process path used for IDE runs, quickstarts, and tests — it does not run on a real Flink cluster. - **Remote / Flink-backed** — `RemoteExecutionEnvironment`, the actual production path, selected when a `StreamExecutionEnvironment` is provided. ### What's not ideal The local path re-implements execution semantics (runner context, memory, tool dispatch) separately from the Flink-backed path, but it is not the path users actually deploy. The practical cost shows up whenever we touch the execution layer: a change has to be made and validated against *both* paths even though only the remote path is production. #722 is a recent example — the structured tool-invocation assertions had to be carried through the local path as well. ### What to evaluate This issue is to scope (not yet commit to) deprecating `LocalRunner` / `LocalExecutionEnvironment`: - Who depends on the local path today — e2e tests, `python/flink_agents/e2e_tests/`, example/quickstart scripts, and any docs that assume `get_execution_environment(env=None)`. - Whether those can migrate to a `MiniCluster`-backed Flink environment, or whether a thin in-process harness is still worth keeping for fast tests. - Migration path and deprecation timeline (e.g. deprecation warning in one release, removal in a later one). Open for discussion on whether this is worth doing and at what priority. -- 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]
