[
https://issues.apache.org/jira/browse/HIVE-18513?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16484227#comment-16484227
]
Jason Dere commented on HIVE-18513:
-----------------------------------
So external tables are not allowed in the cache at all - sorry if my earlier
explanation did not make that clear. The setting I mentioned
(hive.query.results.cache.nontransactional.tables.enabled) is for managed
non-transactional tables only.
Dropping a table (or altering the table) should result in automatic
invalidation in the case of transactional tables.
For non-transactional tables, HIVE-19154 will poll the metastore for
notification events (if you have enabled the DbNotificationListener in your
Hive metastore). So it can eventually find out about changed non-transactional
tables and invalidate those cached results, but it might not be updated until
the next time the notification events are polled (default polling interval is
currently at 60s).
If you have other questions, you can post the question on the Hive user-list
rather than on this Jira.
> Query results caching
> ---------------------
>
> Key: HIVE-18513
> URL: https://issues.apache.org/jira/browse/HIVE-18513
> Project: Hive
> Issue Type: Bug
> Components: Query Planning
> Reporter: Jason Dere
> Assignee: Jason Dere
> Priority: Major
> Fix For: 3.0.0
>
> Attachments: HIVE-18513.1.patch, HIVE-18513.2.patch,
> HIVE-18513.3.patch, HIVE-18513.4.patch, HIVE-18513.5.patch, HIVE-18513.6.patch
>
>
> Add a query results cache that can save the results of an executed Hive query
> for reuse on subsequent queries. This may be useful in cases where the same
> query is issued many times, since Hive can return back the results of a
> cached query rather than having to execute the full query on the cluster.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
