You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@kylin.apache.org by "Shaofeng SHI (JIRA)" <ji...@apache.org> on 2015/09/29 11:14:04 UTC
[jira] [Updated] (KYLIN-198) Support same column name in different
lookup table
[ https://issues.apache.org/jira/browse/KYLIN-198?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Shaofeng SHI updated KYLIN-198:
-------------------------------
Fix Version/s: (was: v1.1)
v1.2
Postpone to future release
> Support same column name in different lookup table
> --------------------------------------------------
>
> Key: KYLIN-198
> URL: https://issues.apache.org/jira/browse/KYLIN-198
> Project: Kylin
> Issue Type: Improvement
> Components: Metadata
> Reporter: Luke Han
> Assignee: Shaofeng SHI
> Labels: github-import
> Fix For: v1.2
>
>
> When there are two lookup table using same name in one cube, the cube engine will raise exception since it do not know which column coming from which table.
> Using full qualified name with _database.tablename.columnname_ to unique identify column in row key.
> Workaround: duplicate lookup table with specified name and join with fact.
> For example: duplicate dw_countries to dw_countries_seller and dw_countries_buyer.
> ---------------- Imported from GitHub ----------------
> Url: https://github.com/KylinOLAP/Kylin/issues/307
> Created by: [lukehan|https://github.com/lukehan]
> Labels: bug,
> Milestone: v2.0 Release
> Assignee: [qhzhou|https://github.com/qhzhou]
> Created at: Fri Dec 26 15:02:51 CST 2014
> State: open
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)