Details
-
Improvement
-
Status: Closed
-
Major
-
Resolution: Fixed
-
None
-
None
-
None
Description
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
Attachments
Issue Links
- is related to
-
KYLIN-1428 Scalable dictionary to support cardinality of billions
- Closed
-
KYLIN-1381 change RealizationCapacity from three profiles to specific numbers
- Closed