[
https://issues.apache.org/jira/browse/KYLIN-3713?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
walhl.liu updated KYLIN-3713:
-----------------------------
Description:
Sometimes, the size of new segment is always less than 1MB after
building job. In fact, size of new htable in hdfs is larger than 1MB. I find
the result of "regionLoad.getStorefileSizeMB()" always is 0. I think it is
unreasonable calculating segment size by "regionLoad.getStorefileSizeMB()"
method.
kylin version is 2.4.1 and kylin metadata is stored in hbase. hbase version
is hbase-1.2.0-cdh5.10.1. Relevant information is attached.
was:
Sometimes, the size of new segment is always less than 1MB after
building job. In fact, size of new htable in hdfs is larger than 1MB. I find
the result of "regionLoad.getStorefileSizeMB()" always is 0. I think it is
unreasonable calculating segment size by "regionLoad.getStorefileSizeMB()"
method
Relevant information is attached.
> Error size statis of segment
> ----------------------------
>
> Key: KYLIN-3713
> URL: https://issues.apache.org/jira/browse/KYLIN-3713
> Project: Kylin
> Issue Type: Bug
> Components: Metadata
> Affects Versions: v2.4.1
> Reporter: walhl.liu
> Priority: Major
> Attachments: cube.jpg, hdfs-size.jpg
>
>
> Sometimes, the size of new segment is always less than 1MB after
> building job. In fact, size of new htable in hdfs is larger than 1MB. I
> find the result of "regionLoad.getStorefileSizeMB()" always is 0. I think it
> is unreasonable calculating segment size by "regionLoad.getStorefileSizeMB()"
> method.
> kylin version is 2.4.1 and kylin metadata is stored in hbase. hbase
> version is hbase-1.2.0-cdh5.10.1. Relevant information is attached.
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
