You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@kylin.apache.org by "Xiaoxiang Yu (Jira)" <ji...@apache.org> on 2021/04/13 06:15:00 UTC
[jira] [Updated] (KYLIN-4861) Wrong way to get CubeManager instance
in CubeInstance.latestCopyForWrite()
[ https://issues.apache.org/jira/browse/KYLIN-4861?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Xiaoxiang Yu updated KYLIN-4861:
--------------------------------
Fix Version/s: (was: v3.1.2)
> Wrong way to get CubeManager instance in CubeInstance.latestCopyForWrite()
> --------------------------------------------------------------------------
>
> Key: KYLIN-4861
> URL: https://issues.apache.org/jira/browse/KYLIN-4861
> Project: Kylin
> Issue Type: Bug
> Reporter: Zhong Yanghong
> Assignee: Xiaoxiang Yu
> Priority: Major
>
> Each cube can have its own KylinConfig. Then for the following code:
> {code}
> public CubeInstance latestCopyForWrite() {
> CubeManager mgr = CubeManager.getInstance(config);
> CubeInstance latest = mgr.getCube(name); // in case this object is out-of-date
> return mgr.copyForWrite(latest);
> }
> {code}
> Each cube can have a different CubeManager instance, which may easily cause map consistency issue.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)