aiwenmo opened a new issue, #10444:
URL: https://github.com/apache/dolphinscheduler/issues/10444

   ### Search before asking
   
   - [X] I had searched in the 
[issues](https://github.com/apache/dolphinscheduler/issues?q=is%3Aissue) and 
found no similar feature requirement.
   
   
   ### Description
   
   Dinky is an out of the box one-stop real-time computing platform dedicated 
to the construction and practice of Unified Batch & Streaming and Unified Data 
Lake & Data Warehouse. Based on Apache Flink, Dinky provides the ability to 
connect many big data frameworks including OLAP and Data Lake.
   
   1.Develop FlinkSQL on the computer and obtain the job ID from the API manual.
   
![image](https://user-images.githubusercontent.com/32723967/173720766-e6ca9c49-94c6-46b3-8ebe-bc5bc3dcc479.png)
   2.Add Dinky job node in workflow, and configure address and task ID.
   
![image](https://user-images.githubusercontent.com/32723967/173720880-7b8122e7-75f4-4ae3-a3a8-f2223da9693f.png)
   3.View job scheduling status from task instances.
   
![image](https://user-images.githubusercontent.com/32723967/173721004-cff3f43e-1e4a-4f2c-9cd7-649aa8357dfb.png)
   4.Query the metric information of jobs from dinky's operation and 
maintenance center.
   
![image](https://user-images.githubusercontent.com/32723967/173721077-5b21f8e2-a9d5-4211-9e64-82f8cf036145.png)
   
   
   ### Use case
   
   Add Dinky task to better support the development and execution of  FlinkSQL.
   
   ### Related issues
   
   _No response_
   
   ### Are you willing to submit a PR?
   
   - [X] Yes I am willing to submit a PR!
   
   ### Code of Conduct
   
   - [X] I agree to follow this project's [Code of 
Conduct](https://www.apache.org/foundation/policies/conduct)
   


-- 
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]

Reply via email to