[KYLIN-968] CubeSegment.lastBuildJobID is null in new instance but used for rowkey_stats path

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: v0.7.2, v1.0
• Fix Version/s: v1.1
• Component/s: Job Engine
• Assignee: Shao Feng Shi
• Reporter: Yerui Sun
• Created: 26/Aug/15 11:54
• Updated: 29/Sep/15 09:35
• Resolved: 16/Sep/15 13:06

Description

CubeSegment.lastBuildJobID is used to record the id of job which building this segment last time.
When build or fresh a cube and append a new segment, the lastBuildingJobID remains as null until the segment build done and info updated. But in the segment building flow, lastBuildingJobID has been used for concat rowkey_stats path, in CubingJobBuilder.getRowkeyDistributionOutputPath, result in rowkey_stats path is like '/../kylin-null/../rowkey_stats', without job id in path.
If more than one segments were building concurrently, the rowkey_stats path will be conflicts and result in wrong split keys for tables in HBase.
Did anybody found this issue before? If not yet and we agreed with the analysis above, I'll apply a patch later.