Description
When we want to obtain the segments information of a cube through the REST API: "kylin/api/cubes/cubeName", we find that if the status of the segment is RUNNING or ERROR, the last_build_job_id is NULL, which I think is It is unreasonable. Once the CubeJob corresponding to the segment is submitted successfully, the last_build_job_id field should be updated, not only when it is FINISHED. After optimization, we can directly get all the segment information under Cube including last_build_job_id through "kylin/api/cubes/cubeName". Otherwise, to obtain the job id of ERROR and RUNNING status, it must be obtained by other means, which is obviously inconvenient.