[
https://issues.apache.org/jira/browse/KYLIN-1444?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Zhong Yanghong updated KYLIN-1444:
----------------------------------
Description: As mentioned in JIRA KYLIN-1264, current streaming build
engine doesn't update segment's metadata like sizeKB, etc. Then these
information will be stored as 0. When visualizing the "Cube Size", the backend
added the size of all the ready segments, which stored in metadata. Therefore,
the "Cube Size" doesn't include the real information of those segments created
by streaming build engine (was: As mentioned in JIRA KYLIN-1264, current
streaming build engine doesn't update segment's metadata like source record
count, sizeKB, etc. Then these information will be stored as 0. When
visualizing the "Cube Size", the backend added the size of all the ready
segments, which stored in metadata. Therefore, the "Cube Size" doesn't include
the real information of those segments created by streaming build engine)
> For streaming, when new segment finishes its building and added to the cube,
> the GUI doesn't update its visualization of "Cube Size"
> ------------------------------------------------------------------------------------------------------------------------------------
>
> Key: KYLIN-1444
> URL: https://issues.apache.org/jira/browse/KYLIN-1444
> Project: Kylin
> Issue Type: Bug
> Components: streaming
> Reporter: Zhong Yanghong
> Assignee: Zhong Yanghong
>
> As mentioned in JIRA KYLIN-1264, current streaming build engine doesn't
> update segment's metadata like sizeKB, etc. Then these information will be
> stored as 0. When visualizing the "Cube Size", the backend added the size of
> all the ready segments, which stored in metadata. Therefore, the "Cube Size"
> doesn't include the real information of those segments created by streaming
> build engine
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
