hackergin commented on issue #17086: URL: https://github.com/apache/dolphinscheduler/issues/17086#issuecomment-2791484548
@SbloodyS Thank you for your reply. 1. Regarding the monitoring mechanism: After submitting a refresh request, we can obtain an operation handle that provides both the jobId and clusterInfo. Using this information, we can monitor the job status through the [DESC JOB [jobId]](https://nightlies.apache.org/flink/flink-docs-master/docs/dev/table/sql/describe/#describe-job) command. The same task instance will continuously monitor until the job reaches a final state (either finished or failed). This approach effectively eliminates the need to create multiple task instances, simplifying the overall process. 2. Regarding the difference between batch and stream processing: Our current workflow implementation is specifically designed for scheduled batch jobs and does not address streaming job submissions. -- 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]
