[
https://issues.apache.org/jira/browse/KYLIN-1122?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15203245#comment-15203245
]
Xiaoyu Wang commented on KYLIN-1122:
------------------------------------
for the {{SQLDigest.isRawQuery}} property .
I think it derive from both {{groupbyColumns}} and {{metricColumns}} will be
correct!
if only derive from {{groupbyColumns}}, the sql: "select sum(price) as GMV,
count(1) as TRANS_CNT from test_kylin_fact" will be identified "RawQuery". and
in "RawQuery",it will add RAW agg function on all column which defined RAW
measure,and remove SUM agg on the column which hack from {{OLAPEnumerator}}.
that is not expect! [[email protected]]
> 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: Backlog
>
> 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,
>
> 0001-KYLIN-1122-Kylin-support-detail-data-query-from-fact-new-impl-under-refactoring-2.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)