Hi, xia Yanick:
Stop api doesn't do a delete action, so we use [POST] and jobid will be transferd as request body. For others,Is it more readable to add such 'start', 'stop' or 'progress'? ------------------ Original ------------------ From: "xia Yanick"<[email protected]>; Date: Wed, Dec 4, 2019 04:31 PM To: "dev"<[email protected]>; Subject: Re: [ShardingScaling][Discuss] Http request APIS about shardingscaling Hi Xiang: That's exactly what I needed, otherwise, do you want like a restful style? create a job: /shardingscaling/job/<job_id> [POST] query a job status: /shardingscaling/job/<job_id> [GET] stop a job /shardingscaling/job/<job_id> [DELETE] > On Dec 4, 2019, at 16:18, sushixiang <[email protected]> wrote: > > Hi, everybody: > > > Http request apis will be provided for shardingscaling to let people easily manager the scaling job. > > > Here are the definitions of such apis: > > > /shardingscaling/job/start [POST] > /shardingscaling/job/progress/${jobId} [GET] > /shardingscaling/job/stop [POST] > > > > Above apis will be used for starting job, get job process and stop job respectively. > > > Here are the related issue and pr: > [1] https://github.com/apache/incubator-shardingsphere/issues/3256 > [2] https://github.com/apache/incubator-shardingsphere/pull/3656 > > > Comments or Suggestions on it are welcome!&nbsp; > > > > Thanks!
