[ 
https://issues.apache.org/jira/browse/KYLIN-1020?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Shaofeng SHI updated KYLIN-1020:
--------------------------------
    Description: 
Kylin allows user to configure "kylin.query.scan.threshold" in 
kylin.properties, and the default value is 10 million; But in 
org.apache.kylin.storage.StorageContext, it has a hard-coded "HARD_THRESHOLD" 
which is 4 million, and "kylin.query.scan.threshold" couldn't exceed this 
threshold, this is wrong.

The correct behavior should be, remove HARD_THRESHOLD and always use 
"kylin.query.scan.threshold" as the threshold.

  was:
Kylin allows user to configure "kylin.query.scan.threshold" in 
kylin.properties, and the default value is 10 million; But in 
org.apache.kylin.storage.StorageContext, it has a hard-coded "HARD_THRESHOLD" 
which is 4 million, and "kylin.query.scan.threshold" could exceed this 
threshold, this is wrong.

The correct behavior should be, remove HARD_THRESHOLD and always use 
"kylin.query.scan.threshold" as the threshold.


> Although "kylin.query.scan.threshold" is set, it still be restricted to less 
> than 4 million 
> --------------------------------------------------------------------------------------------
>
>                 Key: KYLIN-1020
>                 URL: https://issues.apache.org/jira/browse/KYLIN-1020
>             Project: Kylin
>          Issue Type: Bug
>    Affects Versions: v1.0, v0.7.2
>            Reporter: Shaofeng SHI
>            Assignee: Shaofeng SHI
>             Fix For: v1.1
>
>
> Kylin allows user to configure "kylin.query.scan.threshold" in 
> kylin.properties, and the default value is 10 million; But in 
> org.apache.kylin.storage.StorageContext, it has a hard-coded "HARD_THRESHOLD" 
> which is 4 million, and "kylin.query.scan.threshold" couldn't exceed this 
> threshold, this is wrong.
> The correct behavior should be, remove HARD_THRESHOLD and always use 
> "kylin.query.scan.threshold" as the threshold.



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

Reply via email to