[
https://issues.apache.org/jira/browse/KYLIN-5031?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17383220#comment-17383220
]
ASF GitHub Bot commented on KYLIN-5031:
---------------------------------------
hit-lacus merged pull request #1687:
URL: https://github.com/apache/kylin/pull/1687
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
> 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
> Assignee: JasonLee
> Priority: Minor
> 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)
