zhibinF opened a new issue, #5047:
URL: https://github.com/apache/seatunnel/issues/5047

   ### Search before asking
   
   - [X] I had searched in the 
[feature](https://github.com/apache/seatunnel/issues?q=is%3Aissue+label%3A%22Feature%22)
 and found no similar feature requirement.
   
   
   ### Description
   
   From https://github.com/apache/seatunnel/issues/4955 ,  we design Seatunnel 
Http Client instead of Seatnnel CLI.
   At present, seatunnel has been implemented to query status and statistics of 
running jobs, as well as recent completed jobs through rest command. Now we try 
to design Zeta job submission via rest api.
   
   **Job Parameter Passing**
   Pass parameters as a POST request
   All the parameters in the config file are passed in json format in the body 
of the broken post.
   Other CLI job parameters are passed in parameter: clusterName, masterType, 
jobName, restoreJobId, async
   
   **URL entry**
   "/hazelcast/rest/maps/submit-job"
   
   **Implementation ideas**
   1. Under the rest folder to create RestHttpPostCommandProcessor. Java
   2. In NodeExtension. Register RestHttpPostCommandProcessor in Java
   3. Registered in RestConstant * SUBMIT_JOB_URL * for "/ 
hazelcast/rest/maps/submit-job",
   4. Registered in the handle RestHttpPostCommandProcessor handleSubmitJob 
function is used to submit the task
   5. Implement the submit task in the handleSubmitJob function
   
   ### Usage Scenario
   
   _No response_
   
   ### Related issues
   
   _No response_
   
   ### Are you willing to submit a PR?
   
   - [ ] 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