Hi, Did the stop job mean we can resume the job, or just delete it forever?

------------------

Liang Zhang (John)
Apache ShardingSphere & Dubbo


sushixiang <[email protected]> 于2019年12月4日周三 下午4:42写道:

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

Reply via email to