You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@kylin.apache.org by "Shaofeng SHI (JIRA)" <ji...@apache.org> on 2018/12/14 09:34:00 UTC
[jira] [Resolved] (KYLIN-3715) ProjectL2Cache don't be invalidated
when adding override config in cube level
[ https://issues.apache.org/jira/browse/KYLIN-3715?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Shaofeng SHI resolved KYLIN-3715.
---------------------------------
Resolution: Fixed
> ProjectL2Cache don't be invalidated when adding override config in cube level
> -----------------------------------------------------------------------------
>
> Key: KYLIN-3715
> URL: https://issues.apache.org/jira/browse/KYLIN-3715
> Project: Kylin
> Issue Type: Bug
> Components: Metadata
> Affects Versions: v2.4.1
> Reporter: walhl.liu
> Assignee: walhl.liu
> Priority: Major
> Labels: pull-request-available
> Fix For: v2.6.0
>
> Attachments: image-2018-12-10-23-24-53-754.png
>
>
> In kylin versin 2.4.1, I can not get new configs by config object from cubesegment after adding some configs needed to be overrided in cube page.
> For example, I add "kylin.storage.partition.aggr-spill-enabled=false" in cube page, then I send a query. I find the result of "cubeSeg.getConfig().getQueryCoprocessorSpillEnabled()" is not the new value.
> !image-2018-12-10-23-24-53-754.png!
> I find the root cause is that ProjectL2Cache don't be invalidated after broadcasting for cubemanager.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)