[
https://issues.apache.org/jira/browse/GRIFFIN-198?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16642725#comment-16642725
]
Kevin Yao commented on GRIFFIN-198:
-----------------------------------
[~chemikadze]
> Should we support disabling hive integration (by providing empty hive url,
> for example)?
Hive service api in backend is in order to make ui get hive data better. So at
present, the strategy we use is to connect hive when Griffin project starts.
Whether or not to disable hive integration needs to be discussed.
> cache is incomplete
Your understanding is right. What I mean is that when looping through tables
fails on one of those tables, we should not cache and throw exception.
> Evicting works as described, but population logic needs to be fixed.
I agree with you.
> HiveMetaStoreServiceImpl caches incorrect state of metastore
> ------------------------------------------------------------
>
> Key: GRIFFIN-198
> URL: https://issues.apache.org/jira/browse/GRIFFIN-198
> Project: Griffin (Incubating)
> Issue Type: Bug
> Reporter: Nikolay Sokolov
> Assignee: William Guo
> Priority: Major
>
> Currently, HiveMetaStoreServiceImpl is caching:
> * nulls and empty lists in some methods, when metastore request failed for
> some reason
> * empty list of tables as response to getAllTable(String) and getAllTable()
> calls
> Both problems result in confusing output on large amount of tables.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
