Re: job id mismatched in response body after add a new job by API

[Kevin Yao <ah...@gmail.com>]

Hi Woods,

First, when you add a new job, id in  response body is job config id, not
job id. Therefore it is not matched job id in get jobs API.

Second, for the problem that  job id and measure id increment number is not
by 1, that's because postgersql self-increment strategy is not increased by
1. It's different from mysql. If you use mysql as your default database,
you can see job id and measure id increment is by 1.

Thanks,
Kevin


On Fri, Jun 1, 2018 at 10:59 AM crazy woods <cr...@outlook.com>
wrote:

> hi ,
>
> Another issue found when add new job, the job id returned in the create
> response body is not matched with jobId in get jobs API.
>
> here is one example,
>
> create new job with POST /api/v1/jobs:  job id returned is 1030.
> get job list with GET /api/v1/jobs: job id returned 1029.
>
> and the jobid and  measure id increment number is not by 1.
>
> Thanks, Woods
>