I noticed very large hbase region for one segment (more than 20GB and
kylin.storage.hbase.region-cut-gb=5). I don't know why it is so large, but
anyway it degraded performance a lot, so I decided to split it in hbase.

When the split has just started kylin started to return empty results for
queries to this segment.

Why can that happen?

It seams to me that kylin.storage.hbase.region-cut-gb doesn't work in case
if external hbase cluster is used.

Reply via email to