[jira] [Resolved] (KYLIN-3112) The job 'Pause' operation has logic bug in the kylin server.

["Billy Liu (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/KYLIN-3112?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Billy Liu resolved KYLIN-3112.
------------------------------
       Resolution: Fixed
    Fix Version/s: v2.3.0

Patch merged: [https://github.com/apache/kylin/commit/6acb3aba1310424f9048f5eccfa2bdb42731308a]

Thanks [~peng.jianhua]

> The job 'Pause' operation has logic bug in the kylin server.
> ------------------------------------------------------------
>
>                 Key: KYLIN-3112
>                 URL: https://issues.apache.org/jira/browse/KYLIN-3112
>             Project: Kylin
>          Issue Type: Bug
>          Components: General
>    Affects Versions: v2.2.0
>            Reporter: peng.jianhua
>            Assignee: peng.jianhua
>            Priority: Major
>              Labels: patch
>             Fix For: v2.3.0
>
>         Attachments: 0001-KYLIN-3112-The-job-Pause-operation-has-logic-bug-in-.patch, job_click_pause.png, job_click_pause_again.png
>
>
> 1. Click the 'Pause' item, although the result is successful, when you expand the action, you will also find the 'Pause' item. refer to [^job_click_pause.png]
> 2. When you click  'Pause' item again( the second click), when the result is successful, then you expand the action, you will find the 'Pause' item has changed to 'Resume'. refer to [^job_click_pause_again.png]
> I checked the logic code of job pause in kylin server, I found the job status changed to new status in the metadata storage, but not changed in JobInstance which would be sent to client, so the client got the old job status.
> Then you clicked 'Pause' item again, the JobInstance would be fetched from the metadata storage, so it was the new one, then the client woud get the new job status. 
> So I fixed it, please check the patch, thanks!



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)