when you have hfile-size-gb, you re-split HFile using max-region-count and
region-cut-gb ?

--> Yes; Kylin will estimate the total size, then divide by "regino-cut-gb"
to get the region number; If the region number exceeds "max-region-count",
it will do a cap.

Medium , small, . ..  is deprecated (KYLIN-1669
<https://issues.apache.org/jira/browse/KYLIN-1669>)?
--> Yes, that marker has been removed; Will use same split configuration
for all cubes; If user want to customize, he can overwrite the config
values at cube level.

2016-12-08 21:27 GMT+08:00 Alberto Ramón <[email protected]>:

> I'm reading this MailList
> <http://apache-kylin.74782.x6.nabble.com/Update-default-config-for-sandbox-environment-td6561.html>
> and have some doubts (Example
> <https://github.com/apache/kylin/blob/master/examples/test_case_data/sandbox/kylin.properties#L99>
> ):
>
> region-cut-gb
> max-region-count
> hfile-size-gb
>
> when you have hfile-size-gb, you re-split HFile using max-region-count and
> region-cut-gb ?? or is for normal ingest, Kylin 1323?
>
> Medium , small, . ..  is deprecated (KYLIN-1669
> <https://issues.apache.org/jira/browse/KYLIN-1669>)? "# E.g, for cube
> whose capacity be marked as "SMALL", split region per 10GB by default"
> (From Example)
>



-- 
Best regards,

Shaofeng Shi 史少锋

Reply via email to