[
https://issues.apache.org/jira/browse/KYLIN-1031?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14803004#comment-14803004
]
Yerui Sun commented on KYLIN-1031:
----------------------------------
Yes, it's a bug.
In line 79 of UpdateCubeInfoAfterBuildStep.java, segmentReady was set to false
if no data generated in building job.
I changed code to confirm this issue, set segmentReady as true without checking
data size. After the second building job completed without data, a merge job
can be submitted normally.
> Can't build more segments with sample cube
> ------------------------------------------
>
> Key: KYLIN-1031
> URL: https://issues.apache.org/jira/browse/KYLIN-1031
> Project: Kylin
> Issue Type: Bug
> Components: Job Engine
> Affects Versions: v2.0
> Reporter: Yerui Sun
> Assignee: ZhouQianhao
>
> Create a new Kylin environment, and execute bin/sample.sh, created sample
> cube 'kylin_sales_cube'.
> Build this cube from 2012-01-01 to 2015-09-06 successfully, and build another
> segment from 2015-09-07 to 2015-09-08 successfully too.
> At this moment, click the build/merge on Web UI, a alarm pop with 'There
> exists a build request of this cube, the job may be running or error. If you
> need a new build, please wait for its complete or discard it.'.
> It's seems that cube state didn't updated after the second build job
> completed. Maybe because of that the data is empty for the second build job?
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
