[
https://issues.apache.org/jira/browse/KYLIN-4080?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17203848#comment-17203848
]
Zhong Yanghong edited comment on KYLIN-4080 at 9/29/20, 10:33 AM:
------------------------------------------------------------------
This fix will break cube migration when the destination project is different
from the source one because of the additional attribute *projectName* in
DataModelDesc
was (Author: yaho):
This fix will break cube migration when the destination project is different
from the source one.
> Project schema update event causes error reload NEW DataModelDesc
> -----------------------------------------------------------------
>
> Key: KYLIN-4080
> URL: https://issues.apache.org/jira/browse/KYLIN-4080
> Project: Kylin
> Issue Type: Bug
> Components: Metadata
> Affects Versions: v2.5.2
> Reporter: Yuzhang QIU
> Assignee: Yuzhang QIU
> Priority: Blocker
> Fix For: v2.6.5, v3.1.0, v3.0.1
>
>
> Hi, dear Kylin dev team:
> When create new DataModelDesc, DataModelManager.createDataModelDese:246
> will temporarily add the new model name into selected project(project1)
> cache, but won't persist it. The TEMPORARY ADD operation will make the model
> reloading successful, rather than throw "No project found for model ..."
> exception(at ProjectManager:391).
> However, If there have another threads are processing "Broadcasting
> update project_schema, project1", it will clean up cache of project1 and
> reload it, which will reset the "TEMPORARY ADD" operation. Meanwhile, the
> model saving thread has persisted the DataModelDesc and start to reload it,
> but will find there have "No project for this model".
> The new model can't be created again because the conflict timestamp and
> can't be reloaded into cache because the abrove problem.
> How do you think about this??
>
> Best regards
>
> yuzhang
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
