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 subversion and git services (Jira)" <ji...@apache.org> on 2020/08/27 07:38:00 UTC
[jira] [Commented] (KYLIN-2971) Fix the wrong "Realization Names"
in logQuery when hit cache
[ https://issues.apache.org/jira/browse/KYLIN-2971?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17185685#comment-17185685 ]
ASF subversion and git services commented on KYLIN-2971:
--------------------------------------------------------
Commit ff338de3d3fcd30508b8973bc740d0daf5da597d in kylin's branch refs/heads/kylin-on-parquet-v2 from Zhichao Zhang
[ https://gitbox.apache.org/repos/asf?p=kylin.git;h=ff338de ]
KYLIN-2971 Fix the wrong "Realization Names" and missing "Cuboid Ids" in logQuery when hit cache
Problems:
1. The value of "Realization Names" in logQuery is wrong when query two different sqls within the same thread and second sql hits cache:
Example:
1). query Q1 hit project P1 and cube C1;
2). query Q2 hit project P2 and cube C2 in the same thread with Q1;
3). Q1 comes again and hits cache, it will show project P1 and cube C2. However, it should be cube C1.
2. Missing "Cuboid Ids" in logQuery when hit cache in a new thread which does not have OLAPContext;
Solutions:
1. Call 'OLAPContext.clearThreadLocalContexts()' before a query starts;
2. Get "Cuboid Ids" from SQLResponse when "OLAPContext.getThreadLocalContexts()" is null;
(cherry picked from commit b8d55d08301779885dd6418651c979ccaaaf6165)
> Fix the wrong "Realization Names" in logQuery when hit cache
> ------------------------------------------------------------
>
> Key: KYLIN-2971
> URL: https://issues.apache.org/jira/browse/KYLIN-2971
> Project: Kylin
> Issue Type: Bug
> Reporter: Zhong Yanghong
> Assignee: Zhichao Zhang
> Priority: Minor
> Fix For: v3.1.0
>
> Attachments: APACHE-KYLIN-2971.patch
>
>
> # The value of "Realization Names" in logQuery is wrong when query two different sqls within the same thread and second sql hits cache:
> Example:
> 1). query Q1 hit project P1 and cube C1;
> 2). query Q2 hit project P2 and cube C2 in the same thread with Q1;
> 3). Q1 comes again and hits cache, it will show project P1 and {color:#f79232}cube C2{color}. However, it should be {color:#f79232}cube C1{color}.
> # Missing "Cuboid Ids" in logQuery when hit cache in a new thread which does not have OLAPContext;
--
This message was sent by Atlassian Jira
(v8.3.4#803005)