Following parameter works for Kylin 2.1
kylin.query.max-scan-bytes & kylin.storage.partition.max-scan-bytes

kylin.query.scan.threshold has been deprecated
And there is no kylin.query.mem.budget parameter.

2017-08-30 9:18 GMT+08:00 shendandan2015yeah <[email protected]>:

> Are these two attributes?
> kylin.query.scan.threshold=10000000
> kylin.query.mem.budget=3221225472
>
>
>
> 来自 魅族 PRO 6s
>
> -------- 原始邮件 --------
> 发件人:Billy Liu <[email protected]>
> 时间:周二 8月29日 19:42
> 收件人:dev <[email protected]>
> 主题:Re: use tableau connect to kylin
>
> >Queries like "select * from fact" tend to scan a lot of cube data. To make
> >them fail fast, you can decrease:
> >
> >   1. kylin.query.max-scan-bytes (by default INTEGER.MAX) to allow less
> >   bytes scanned at query level
> >   2. kylin.storage.partition.max-scan-bytes (by default 3221225472) to
> >   allow less bytes scanned at partition level
> >
> >
> >2017-08-29 18:48 GMT+08:00 shendandan2015yeah <[email protected]
> >:
> >
> >>
> >>
> >>
> >> 来自 魅族 PRO 6s
> >>
> >> -------- 原始邮件 --------
> >> 发件人:shendandan2015yeah <[email protected]>
> >> 时间:周二 8月29日 18:40
> >> 收件人:Billy Liu <[email protected]>
> >> 主题:Re: use tableau connect to kylin
> >>
> >> >in kylin.log, "select * from fact_table"  takes the most time,because
> >> there are millon records. Then how to optimize the cube?
> >> >
> >> >Thanks Billy.
> >> >
> >> >来自 魅族 PRO 6s
> >> >
> >> >-------- 原始邮件 --------
> >> >发件人:Billy Liu <[email protected]>
> >> >时间:周二 8月29日 10:27
> >> >收件人:dev <[email protected]>
> >> >主题:Re: use tableau connect to kylin
> >> >
> >> >1. Find the slow query sent from Tableau in kylin.log
> >> >2. Optimize the cube in Kylin
> >> >
> >> >2017-08-29 10:00 GMT+08:00 shendandan2015yeah <
> [email protected]
> >> >:
> >> >
> >> >> hello,I use tableau connect to kylin,and publish some reports to
> tableau
> >> >> server. But  these reports open slowly.
> >> >> How can I improve this situation?
> >> >> Thank you.
> >> >>
> >> >>
> >> >> 来自 魅族 PRO 6s
> >> >
> >>
> >
>

Reply via email to