You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@kylin.apache.org by "pengfei.zhan (Jira)" <ji...@apache.org> on 2023/02/10 11:20:00 UTC

[jira] [Resolved] (KYLIN-5309) Propose more flexible runtime join scenarios for Kylin

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

pengfei.zhan resolved KYLIN-5309.
---------------------------------
    Resolution: Fixed

> Propose more flexible runtime join scenarios for Kylin
> ------------------------------------------------------
>
>                 Key: KYLIN-5309
>                 URL: https://issues.apache.org/jira/browse/KYLIN-5309
>             Project: Kylin
>          Issue Type: New Feature
>          Components: Metadata, Query Engine
>    Affects Versions: 5.0-alpha
>            Reporter: pengfei.zhan
>            Assignee: pengfei.zhan
>            Priority: Major
>             Fix For: 5.0-alpha
>
>         Attachments: 5309-1.png, 5309-2.png, 5309-3.png, 5309-4.png, 5309-5.png, 5309-6.png, 5309-7.png, 5309-8.png
>
>
> At present, the kylin5 already provides a runtime join scenario: non-pre-computation which can be defined when creating a model. Usually, non-pre-computation is used for the scenario of many-to-many to avoid data blowing up dramatically when building the flat table.
> This issue will propose one more flexible runtime join scenario for kylin5. This feature is the excluded table.  More information will be introduced by the Chinese document in the following comments.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)