[
https://issues.apache.org/jira/browse/HIVE-18513?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16484190#comment-16484190
]
Thai Bui commented on HIVE-18513:
---------------------------------
Thanks for the quick reply. That’s a good news . I can just enable that
flag for all the external tables. Our tables are immutable and the changing
ones are handled with new partitions so this should work.
However, we have a special case where we would drop the existing table and
recreate it with a new external location sometimes. Will that invalidate
the existing cache?
--
Thai
> 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)
