You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@kylin.apache.org by "ASF GitHub Bot (Jira)" <ji...@apache.org> on 2019/12/06 10:25:00 UTC
[jira] [Commented] (KYLIN-4080) Project schema update event casues
error reload NEW DataModelDesc
[ https://issues.apache.org/jira/browse/KYLIN-4080?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16989615#comment-16989615 ]
ASF GitHub Bot commented on KYLIN-4080:
---------------------------------------
zhangayqian commented on pull request #976: KYLIN-4080 Project schema update event casues error reload NEW DataModelDesc
URL: https://github.com/apache/kylin/pull/976
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
> Project schema update event casues 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
>
> 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)