You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@kylin.apache.org by "nichunen (JIRA)" <ji...@apache.org> on 2018/08/26 08:52:00 UTC

[jira] [Updated] (KYLIN-3515) Cubing jobs may interfere with each other if use same hive view

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

nichunen updated KYLIN-3515:
----------------------------
    Description: The root cause is for hive view, during cubing, kylin will materialize the view by creating an intermediate table(drop intermediate table first). The intermediate tables' name is like kylin_intermediate_\{view_name}, that means jobs will create tables with the same name if the same view is referenced. So one job's intermediate table may be dropped by another job, in such cases, error like "table not found" will happen  (was: The root cause is for hive view, during cubing, kylin will materialize the view by creating an intermediate table(drop intermediate table first). The intermediate tables' name is like kylin_intermediate_\{view_name}, that means jobs will create tables with the same name if the same view is referenced. So one job's intermediate table may be dropped by another job.)

> Cubing jobs may interfere with each other if use same hive view
> ----------------------------------------------------------------
>
>                 Key: KYLIN-3515
>                 URL: https://issues.apache.org/jira/browse/KYLIN-3515
>             Project: Kylin
>          Issue Type: Bug
>          Components: Job Engine
>    Affects Versions: v2.4.0
>            Reporter: nichunen
>            Assignee: nichunen
>            Priority: Major
>             Fix For: Future
>
>
> The root cause is for hive view, during cubing, kylin will materialize the view by creating an intermediate table(drop intermediate table first). The intermediate tables' name is like kylin_intermediate_\{view_name}, that means jobs will create tables with the same name if the same view is referenced. So one job's intermediate table may be dropped by another job, in such cases, error like "table not found" will happen



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