[
https://issues.apache.org/jira/browse/KYLIN-5744?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17832162#comment-17832162
]
ASF subversion and git services commented on KYLIN-5744:
--------------------------------------------------------
Commit d13199db7407552226a58060ceb9b41a7f859c36 in kylin's branch
refs/heads/kylin5 from Pengfei Zhan
[ https://gitbox.apache.org/repos/asf?p=kylin.git;h=d13199db74 ]
KYLIN-5744 Answering snapshot first, then answering by metadata
Hitting snapshot has a higher priority than
answering min/max with metadata.
Change the default behavior of routing query to metadata to true
1. Fix timezone problem.
Given the fact of min(cal_dt) = '2012-01-01',
the result of `select min(cal_dt) from test_kylin_fact`
may give '2011-12-31' rather than '2012-01-01'.
2. Fix min/max query hit a index without any dimensions.
For example: `select min(cal_dt) as min_cal_dt from test_kylin_fact `
hits index just has a measure of min(cal_dt),
the SparkPlan is wrong: ` project --- project --- tableScan `;
but the desired SparkPlan is: ` aggregate --- project --- tableScan `.
> Enable the parameter kylin.query.using-metadata-answer-minmax-of-dimension by
> default, to answer the max/min query through metadata
> -----------------------------------------------------------------------------------------------------------------------------------
>
> Key: KYLIN-5744
> URL: https://issues.apache.org/jira/browse/KYLIN-5744
> Project: Kylin
> Issue Type: Bug
> Affects Versions: 5.0-beta
> Reporter: zhong.zhu
> Assignee: zhong.zhu
> Priority: Minor
> Fix For: 5.0.0
>
>
> Enable the parameter
> *_kylin.query.using-metadata-answer-minmax-of-dimension_* by default to
> answer max/min queries via metadata
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
