Uploaded image for project: 'Kylin'
  1. Kylin
  2. KYLIN-5031

The last_build_job_id of segment is null when the semgent status is RUNNING or ERROR.

Agile BoardAttach filesAttach ScreenshotVotersStop watchingWatchersCreate sub-taskLinkCloneUpdate Comment AuthorReplace String in CommentUpdate Comment VisibilityDelete Comments
    XMLWordPrintableJSON

Details

    • Improvement
    • Status: Resolved
    • Minor
    • Resolution: Fixed
    • v4.0.0-beta
    • v4.0.0
    • Metadata
    • None

    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.

      Attachments

        Activity

          This comment will be Viewable by All Users Viewable by All Users
          Cancel

          People

            jasonlee1017 Chuang Lee
            jasonlee1017 Chuang Lee
            Votes:
            0 Vote for this issue
            Watchers:
            3 Stop watching this issue

            Dates

              Created:
              Updated:
              Resolved:

              Slack

                Issue deployment