You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@kylin.apache.org by "Su Ralph (JIRA)" <ji...@apache.org> on 2016/02/03 04:09:40 UTC
[jira] [Created] (KYLIN-1397) Query result cached even when underly
HTABLE scan failed
Su Ralph created KYLIN-1397:
-------------------------------
Summary: Query result cached even when underly HTABLE scan failed
Key: KYLIN-1397
URL: https://issues.apache.org/jira/browse/KYLIN-1397
Project: Kylin
Issue Type: Bug
Components: Query Engine
Affects Versions: v2.0
Reporter: Su Ralph
Assignee: Edward Zhang
Query result cached even when underly HTABLE scan failed. When the HTABLE fixed, the query would still get the cached result.
In my case, there is an Hbase table(one hung htable in all of 14 htables involved) issue happened when user issue an query. The query hungs for long time. Later, when the the htable hung issue fixed. User still get the empty result.
But if user just simple change a query condition, the result would return correct result. The empty result fixed when kylin admin "Reload Metadata".
This indicates that kylin query cache are *incorrectly build* and util admin "Reload Metadata" we don't have an way invalidate the cache.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)