[
https://issues.apache.org/jira/browse/HIVE-18513?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16549661#comment-16549661
]
Lars Francke commented on HIVE-18513:
-------------------------------------
If I read the design doc correctly the decision to disallow EXTERNAL tables is
not a purely technical one but more one of expectations. EXTERNAL tables are
expected to be modified outside of Hive's control while MANAGED tables are not.
I agree with [~thai.bui] that it'd be great to give the user the choice to
still use this feature. In my experience both MANAGED and EXTERNAL tables are
frequently modified outside of Hive (ingestion directly via Sqoop, Flume, NiFi,
Spark etc.). Have you made any progress Thai Bui?
> 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)
