[
https://issues.apache.org/jira/browse/KYLIN-4379?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17067401#comment-17067401
]
Shao Feng Shi commented on KYLIN-4379:
--------------------------------------
I see it; If no available cube, Kylin should use system level configuration.
> Calculate column cardinality cannot use kylin config overwrite cause job
> failed
> -------------------------------------------------------------------------------
>
> Key: KYLIN-4379
> URL: https://issues.apache.org/jira/browse/KYLIN-4379
> Project: Kylin
> Issue Type: Bug
> Reporter: ZhouKang
> Assignee: ZhouKang
> Priority: Major
> Fix For: v3.0.2, v2.6.6
>
>
> Calculate column cardinality submit job to the default queue, which cause job
> failed.
> It seems this job cannot use kylin config overwrite.
> When you load or reload data from hive to kylin, there will be a checkbox as
> "Calculate column cardinality". If this checkbox is selected, Kylin will
> submit a MR/Spark job.
> When a MR job sumitted to yarn, it will use default queue. But in many
> environment, it's forbidden. You should use the queue in
> kylin.engine.mr.config-override.mapreduce.job.queuename
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
