DanielLeens commented on code in PR #11557: URL: https://github.com/apache/seatunnel/pull/11557#discussion_r3836493737
########## docs/zh/engines/zeta/managed-source-runtime.md: ########## @@ -0,0 +1,206 @@ +--- +sidebar_position: 16 +--- + +# 引擎受管 Source 运行时 + +<!-- +Licensed to the Apache Software Foundation (ASF) under one or more +contributor license agreements. See the NOTICE file distributed with +this work for additional information regarding copyright ownership. +The ASF licenses this file to You 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. +--> + +引擎受管 Source 运行时是 [STIP-31](https://github.com/apache/seatunnel/issues/11558) +引入的实验性 Zeta 执行通道。它把 Reader 和 Split Enumerator 的 checkpoint 可见状态统一放入 +引擎拥有的事件循环中串行执行，使连接器不再需要自行用 checkpoint lock 协调引擎回调。 + +该功能默认关闭。只有以下条件同时满足，现有作业才会在新部署时进入受管通道： + +1. `managed-source-runtime.enabled` 为 `true`。 +2. 连接器名称在 `connector-allowlist` 中。 Review Comment: Aligned with this direction in 8dfbf773206. The managed runtime no longer exposes `connector-allowlist`. Lane selection is now gated only by `managed-source-runtime.enabled` plus the connector-declared `ManagedSourceCapability`. When the feature flag is enabled, a source without a compatible capability now fails closed during deployment instead of silently weakening the contract. I also updated the parser, defaults, E2E config, and both docs to match that behavior. The PR still has a merge conflict with `dev`, so I kept conflict resolution out of this update. -- 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]
