arshadmohammad commented on PR #184:
URL: https://github.com/apache/seatunnel-web/pull/184#issuecomment-2290763827
**Yes, the job created by the new API is echoed to the canvas normally.**
Becuase this API is generating exactly same data as it was created by below
four APIs
POST seatunnel/api/v1/job/definition
POST seatunnel/api/v1/job/task/{jobVersionId}
PUT seatunnel/api/v1/job/config/{jobVersionId}
POST seatunnel/api/v1/job/dag/{jobVersionId}
The new API is taking below input
public class JobCreateReq {
private JobConfig jobConfig;
private List<PluginConfig> pluginConfigs;
private JobDAG jobDAG;
}
JobConfig is the input for "PUT seatunnel/api/v1/job/config/{jobVersionId}"
List<PluginConfig> pluginConfigs is the input for "POST
seatunnel/api/v1/job/task/{jobVersionId}"
JobDAG is the input for "POST seatunnel/api/v1/job/dag/{jobVersionId}"
JobReq is the input for "POST seatunnel/api/v1/job/definition" API, which is
taken indirectly.
JobReq attribtues name,description and jobType are available in JobConfig.
So JobReq is created from JobConfig and JobReq is handled the same way as it
handled in "POST seatunnel/api/v1/job/definition" API.
--
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]
