You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@kylin.apache.org by "Billy Liu (JIRA)" <ji...@apache.org> on 2016/12/23 09:52:58 UTC

[jira] [Commented] (KYLIN-1863) Discard the Jobs while Droping/Purging the Cube

    [ https://issues.apache.org/jira/browse/KYLIN-1863?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15772441#comment-15772441 ] 

Billy Liu commented on KYLIN-1863:
----------------------------------

In 1.6+ version, the Drop will check if some unfinished jobs first. User has to discard the job first, then drop. 

> Discard the Jobs while Droping/Purging the Cube
> -----------------------------------------------
>
>                 Key: KYLIN-1863
>                 URL: https://issues.apache.org/jira/browse/KYLIN-1863
>             Project: Kylin
>          Issue Type: Bug
>            Reporter: Richard Calaba
>
> I have observed that following scenario on UI leaves uncleaned meta-data in Kylin:
> 1) I have an error status job in Monitor for my Cube. I drop the cube from UI. I still see the error status jobs in Monitor after Dropping the Cube. If I try to Discard the job -> I am getting NPE. Didn't test the same if Purge used instead of Drop - but this needs to be checked as well.
> 2) Not 100% sure - but I have a feeling that if I Drop cube from UI before Purging it 1st - some job execution metadata (finished build jobs) stay in the system ... (intermediate tables/HDFS folders/...). It is hard to find a prove now when my system is polluted with old job executions. This could be checked while working on 1) above.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)