You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@kylin.apache.org by "Chao Long (JIRA)" <ji...@apache.org> on 2019/04/09 02:14:00 UTC

[jira] [Issue Comment Deleted] (KYLIN-3924) Build cube on step 'build Dimension Dictionary ', the contents of non-dimensional columns are also checked and built

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

Chao Long updated KYLIN-3924:
-----------------------------
    Comment: was deleted

(was: Hi, Kylin only build dictionary for dict-encoding columns and some columns in special measure(precisely count distinct, topN) which need global dictionary.)

> Build cube on step 'build Dimension Dictionary ', the contents of non-dimensional columns are also checked and built
> --------------------------------------------------------------------------------------------------------------------
>
>                 Key: KYLIN-3924
>                 URL: https://issues.apache.org/jira/browse/KYLIN-3924
>             Project: Kylin
>          Issue Type: Bug
>          Components: Job Engine, Tools, Build and Test
>    Affects Versions: v2.6.1
>            Reporter: wangxiaojing
>            Priority: Major
>              Labels: build, patch
>         Attachments: builderr.log
>
>
> Hi all,
>  I use version 2.6.1 , when build cube on step 'build Dimension Dictionary' for lookup tables ,it throws some exceptions,it seems checks the content size of each field in the table while building Dimension Dictionary, and build all fields in the table with a dictionary.
> Suggestion:
>  1. Large content fields may not be dimension columns, in fact, it is not necessary to check the value size of non-dimension columns,only check dimension columns.
> 2. If the value of some fields in the dimension table is too long, the exception is not clear, can not be located the problem column quickly.
> 3. There is no need to build dictionaries for non-dimensional columns



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