[ https://issues.apache.org/jira/browse/KYLIN-4080?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17032162#comment-17032162 ]
ASF subversion and git services commented on KYLIN-4080: -------------------------------------------------------- Commit 2634a7ec01fbc426ba3d21b708c7b13a3c07398b in kylin's branch refs/heads/2.6.x from yaqian.zhang [ https://gitbox.apache.org/repos/asf?p=kylin.git;h=2634a7e ] KYLIN-4080 Project schema update event casues error reload NEW DataModelDesc > 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 > > > 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)