[ 
https://issues.apache.org/jira/browse/KYLIN-1122?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15072499#comment-15072499
 ] 

Dong Li commented on KYLIN-1122:
--------------------------------

Hi Xiaoyu and Yang, I've pushed code to allow a MeasureType only aggregating in 
base cuboid. To enable this, you need to override onlyAggrInBaseCuboid() method 
in MeasureType class to "return true". Then these measures will not aggregate 
in cubing stage.(To hold the place, an initial value will be stored.) Also I 
changed logic of IdentifyCuboid of QueryEngine, BaseCuboid will always be 
returned if any metric has such MeasureType.
Please have some check and continue your work. For any questions, please let me 
know. Thanks.

> Kylin support detail data query from fact table
> -----------------------------------------------
>
>                 Key: KYLIN-1122
>                 URL: https://issues.apache.org/jira/browse/KYLIN-1122
>             Project: Kylin
>          Issue Type: New Feature
>          Components: Query Engine
>    Affects Versions: v1.2
>            Reporter: Xiaoyu Wang
>            Assignee: liyang
>             Fix For: v2.0, v1.3
>
>         Attachments: 
> 0001-KYLIN-1122-Kylin-support-detail-data-query-from-fact(2.x-staging).patch, 
> 0001-KYLIN-1122-Kylin-support-detail-data-query-from-fact(update-v2-1.x-staging).patch
>
>
> Now Kylin does not support query correct detail rows from fact table like:
> select column1,column2,column3 from fact_table
> The jira KYLIN-1075 add the "SUM" function on the measure column if defined.
> But only the column number type is support.
> I change some code to support this issue:
> Add a "VALUE" measure function : the same value and datatype in the input and 
> output of this function.
> If you want to query detail data from fact table
> *require*:
> 1.Configure the column which not dimensions to "VALUE" or "SUM" measure.(If 
> not configure measure function in the column will get NULL value)
> 2.The source table must has an unique value column and configure it as 
> dimension.
> If you have the better solution please comment here.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to