You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@kylin.apache.org by "Huang Hua (JIRA)" <ji...@apache.org> on 2015/08/14 11:18:45 UTC
[jira] [Commented] (KYLIN-949) Query cache doesn't work properly
for prepareStatement queries
[ https://issues.apache.org/jira/browse/KYLIN-949?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14696751#comment-14696751 ]
Huang Hua commented on KYLIN-949:
---------------------------------
I am working on a patch for it and will post the patch soon here, thanks.
> Query cache doesn't work properly for prepareStatement queries
> --------------------------------------------------------------
>
> Key: KYLIN-949
> URL: https://issues.apache.org/jira/browse/KYLIN-949
> Project: Kylin
> Issue Type: Bug
> Components: REST Service
> Affects Versions: v0.7.2, v0.7.1
> Reporter: Huang Hua
> Assignee: Zhong,Jason
>
> There is a bug in searchQueryInCache() method, for PrepareSqlRequest, the cache logic is wrong which returns the same result for any PrepareSqlRequest with same sql no matter what the actual params are.
> For example, using "select LEAF_CATEG_ID from KYLIN_SALES where LEAF_CATEG_ID = ? group by LEAF_CATEG_ID;" with params=[65] to fire request, and kylin will return 65. Let's suppose that query is cached(we can modify kylin settings to enable it to cache every query).
> And then using the same sql but with params=[130], which returns 65 instead of 130.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)