You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@kylin.apache.org by "Zhong,Jason (JIRA)" <ji...@apache.org> on 2016/05/11 08:26:13 UTC
[jira] [Commented] (KYLIN-1584) Specify region cut size in cubedesc
and leave the RealizationCapacity in model as a hint
[ https://issues.apache.org/jira/browse/KYLIN-1584?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15279780#comment-15279780 ]
Zhong,Jason commented on KYLIN-1584:
------------------------------------
move this feature to CubeDesc.override_kylin_properties
will remove CubeDesc.region_size
> Specify region cut size in cubedesc and leave the RealizationCapacity in model as a hint
> ----------------------------------------------------------------------------------------
>
> Key: KYLIN-1584
> URL: https://issues.apache.org/jira/browse/KYLIN-1584
> Project: Kylin
> Issue Type: Improvement
> Reporter: hongbin ma
> Assignee: hongbin ma
> Fix For: v1.5.2
>
>
> currently the cube region's size is determined in model's capacity(RealizationCapacity), it will enforce different realizations under the same model having uniformed region size. This is not wanted feature because cube builder might need to try out different region size to tune performance. I'm suggesting to add a field called "region_size" (float type, 1.0 means 1G per region) in cube desc to explicitly indicate the cube's region size. The field "region_size" will not be included in cubedesc's signature calculation.
> when the region_size is not specified (this is the case for legacy cubes) the hint in model's capacity(RealizationCapacity) will be used to determine region size
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)