hive-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Thai Bui (JIRA)" <>
Subject [jira] [Commented] (HIVE-18513) Query results caching
Date Wed, 01 Aug 2018 18:03:01 GMT


Thai Bui commented on HIVE-18513:

The timeout parameters specially for the external tables make a lot of
sense to limit potential misuse.

I don’t know how the cache is invalidated internally in Hive, but if the
API for cache invalidation is available at the Hive hooks level, we could
potentially implement a custom hook to check/tell Hive to invalidate the
cache as needed (at table / partition level), in conjunction to the timeout


> Query results caching
> ---------------------
>                 Key: HIVE-18513
>                 URL:
>             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

View raw message