[
https://issues.apache.org/jira/browse/KYLIN-2575?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16751067#comment-16751067
]
yuzhang qiu edited comment on KYLIN-2575 at 1/24/19 12:52 PM:
--------------------------------------------------------------
Our group add the computed column feature based on Kylin2.5.2. We define the
computed column on DataSource page and add the computed column data into table
detail metadata. We found that there was some commit for this feature in
history, but now it's reverted. So we have some questions:
1. what's the plan for develop the computed column feature.
2. Why the commits for computed column feature have been reverted?
3. Could we contribute the computed column feature to Apache Kylin?
was (Author: simpleyuzhang):
Our group add the computed column feature based on Kylin2.5.2. We define the
computed column on DataSource page and add the computed column data into table
detail metadata.
> Experimental feature: Computed Column
> -------------------------------------
>
> Key: KYLIN-2575
> URL: https://issues.apache.org/jira/browse/KYLIN-2575
> Project: Kylin
> Issue Type: New Feature
> Reporter: hongbin ma
> Assignee: hongbin ma
> Priority: Major
>
> Computed column is a virtual column that is calculated from an expression of
> existing columns. For example, TAX is computed from PRICE * TAX_RATE; TX_YEAR
> is from EXTRACT(year from TX_DATE).
> Currently user have to create a view to enrich these computed columns, then
> feed the view to cube. This has two inconvenience:
> Create a view is not easy.
> The query has to be rewritten to use view instead of the original table.
> Let Kylin directly support computed column will be a big step forward.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
