sunlishuo25 opened a new issue, #18672: URL: https://github.com/apache/dolphinscheduler/issues/18672
### What happened A SeaTunnel task created in a workflow is always initialized as a DolphinScheduler `BATCH` task. Setting SeaTunnel's `env.job.mode = "STREAMING"` does not change this: after execution, the task belongs to the Batch Task instance list and cannot be explicitly classified as a Stream Task in the form. The form offers no execution-type selection for SeaTunnel. This also affects resource-file configurations, whose contents are not available to the form. ### Version and reproduction Confirmed in current `dev` at `c63ecc9bf68919547fe69b5266e4040b113028e8`; the same initialization path exists in 3.3.2. 1. Create a workflow and add a SeaTunnel task. 2. Set its SeaTunnel configuration to streaming mode, or select a streaming configuration resource. 3. Save the node. The serialized definition has `taskExecuteType: "BATCH"`; there is no form control to choose `STREAM`. A local source-level reproduction executed the real SeaTunnel model, shared `useTask`, and `formatParams`: BATCH and STREAMING custom configurations both serialize as BATCH, as does a resource configuration. FLINK_STREAM is the control case and serializes as STREAM. Unrelated form widgets were mocked; this is not a claim of a live SeaTunnel engine test. ### Expected behavior / focused proposal Allow an explicit SeaTunnel Batch/Stream execution-type choice for workflow-managed tasks, defaulting to Batch for compatibility. Persist the existing taskExecuteType field and preserve it in the editor and DAG metadata. Do not parse arbitrary HOCON/resources in the browser or classify all SeaTunnel tasks as streams. This is limited to workflow-managed attached submission. It does not restore the removed standalone streaming runtime, add detached-job lifecycle tracking, or implement SeaTunnel savepoints. The existing savepoint action should be disabled for SeaTunnel because its task does not implement StreamTask. ### Related context The standalone Task Definition UI was removed in #16397 and the previous streaming executor was removed during #16327. This proposal uses the current workflow execution path instead. #17786 and #18492 concern engine cancellation and are separate from the creation/classification issue. Investigation and proposed implementation are AI-assisted. -- 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]
