You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@kylin.apache.org by "JasonLee (Jira)" <ji...@apache.org> on 2021/07/08 12:25:00 UTC

[jira] [Created] (KYLIN-5031) The last_build_job_id of segment is null when the semgent status is RUNNING or ERROR.

JasonLee created KYLIN-5031:
-------------------------------

             Summary: The last_build_job_id of segment is null when the  semgent status is RUNNING or ERROR.
                 Key: KYLIN-5031
                 URL: https://issues.apache.org/jira/browse/KYLIN-5031
             Project: Kylin
          Issue Type: Improvement
          Components: Metadata
    Affects Versions: v4.0.0-beta
            Reporter: JasonLee
             Fix For: v4.0.0
         Attachments: image-2021-07-08-20-18-19-129.png

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.

!image-2021-07-08-20-18-19-129.png|width=460,height=255!



--
This message was sent by Atlassian Jira
(v8.3.4#803005)