[
https://issues.apache.org/jira/browse/KYLIN-5498?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17709230#comment-17709230
]
longfeiJiang edited comment on KYLIN-5498 at 4/6/23 7:12 AM:
-------------------------------------------------------------
*Root Cause*
By observing the debugging in chrome, it can be found that the models/semantic
interface is called after clicking Save and building the index
!image-2023-04-06-14-55-29-775.png!
Then break the break point in the models/semantic API to debug ,
when the addRelatedIndexJob(JobParam jobParam) method is executed,
since the segment was deleted and no new segment was created, So noNeed is true
at this time,
the following log is output: no successful job is added
the index construction task will not be generated in the end.
!image-2023-04-06-15-06-03-402.png!
!image-2023-04-06-15-06-21-786.png!
It is found that in the models/semantic API, the
ModelSemanticHelper##doHandleSemanticUpdate method will be called, and the
handleReloadData method will be called in this method to update the partition
column information.
Since the original model is a multi-level partition model, the code will go to
the red box. Obviously, the code in the red box does not involve any assignment
operation of Segment.
However, the time partition column of the model has also changed, from time
partition to no time partition.
Because the if else structure is not used correctly, no new segment is
generated for the new full model, and the old segment is deleted, so the
construction task will not be produced in the end.
!image-2023-04-06-15-12-54-584.png!
was (Author: JIRAUSER298472):
*Root Cause*
By observing the debugging in chrome, it can be found that the models/semantic
interface is called after clicking Save and building the index
!image-2023-04-06-14-55-29-775.png!
Then break the break point in the models/semantic API to debug ,
when the addRelatedIndexJob(JobParam jobParam) method is executed,
since the segment was deleted and no new segment was created, So noNeed is true
at this time,
the following log is output: no successful job is added
the index construction task will not be generated in the end.
!image-2023-04-06-15-06-03-402.png!
!image-2023-04-06-15-06-21-786.png!
It is found that in the models/semantic API, the
ModelSemanticHelper##doHandleSemanticUpdate method will be called, and the
handleReloadData method will be called in this method to update the partition
column information.
Since the original model is a multi-level partition model, the code will go to
the red box. Obviously, the code in the red box does not involve any assignment
operation of Segment.
However, the time partition column of the model has also changed, from time
partition to no time partition.
Because the if else structure is not used correctly, no new segment is
generated for the new full model, and the old segment is deleted, so the
construction task will not be produced in the end.
> When the multi-level partition is enabled, changing model from incremental
> build to full build and select 'Save and Build', but there is no building job
> generated
> ------------------------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: KYLIN-5498
> URL: https://issues.apache.org/jira/browse/KYLIN-5498
> Project: Kylin
> Issue Type: Bug
> Reporter: longfeiJiang
> Assignee: longfeiJiang
> Priority: Major
> Attachments: image-2023-04-06-14-55-29-775.png,
> image-2023-04-06-15-06-03-402.png, image-2023-04-06-15-06-21-786.png,
> image-2023-04-06-15-12-54-584.png
>
>
> When the multi-level partition is enabled, changing model from incremental
> build to full build and select 'Save and Build', but there is no building job
> generated
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
