You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@kylin.apache.org by "Shaofeng SHI (JIRA)" <ji...@apache.org> on 2016/12/12 06:19:58 UTC
[jira] [Commented] (KYLIN-2244)
"kylin.job.cuboid.size.memhungry.ratio" shouldn't be applied on measures
like TopN
[ https://issues.apache.org/jira/browse/KYLIN-2244?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15741102#comment-15741102 ]
Shaofeng SHI commented on KYLIN-2244:
-------------------------------------
Deprecate "kylin.cube.size-estimate-memhungry-ratio" and add new "kylin.cube.size-estimate-countdistinct-ratio" (with default 0.05). When estimate the cuboid size, for count distinct measure (both HLL and Bitmap), use this ration. For dimension and other measure value, use the ordinary "kylin.cube.size-estimate-ratio" (default 0.25).
> "kylin.job.cuboid.size.memhungry.ratio" shouldn't be applied on measures like TopN
> ----------------------------------------------------------------------------------
>
> Key: KYLIN-2244
> URL: https://issues.apache.org/jira/browse/KYLIN-2244
> Project: Kylin
> Issue Type: Improvement
> Components: Job Engine
> Reporter: Shaofeng SHI
> Fix For: v1.6.1
>
>
> The parameter "kylin.job.cuboid.size.memhungry.ratio" (new name " kylin.cube.size-estimate-memhungry-ratio") default value 0.05, is based on the compression ration on HyperLogLog; it doesn't fit for other memory hungry measures like TopN, Raw, etc;
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)