[
https://issues.apache.org/jira/browse/HIVE-18513?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16550096#comment-16550096
]
Thai Bui commented on HIVE-18513:
---------------------------------
[~lars_francke] I have not work on disabling this limitation on cache and
external table, but it's still on my agenda for one of the most important
features I wanted to implement for Hive. Ideally, I really want to blur the
boundary of managed vs. external table. I think most of the features that only
work with managed tables should work with external tables as well. By default,
they can be turned off but with an option to be turned on.
[~jdere] Should we consider opening up the cache for external table? If yes, I
can create a ticket and find sometime to work on it. Since you originally
design this feature, we would like to hear your opinions on this as well. Would
enabling this feature badly break a lot of assumptions in Hive that it's
untenable to be implemented in Hive?
> 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)
