[
https://issues.apache.org/jira/browse/HIVE-19892?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16513167#comment-16513167
]
Jason Dere commented on HIVE-19892:
-----------------------------------
So the cache lookup has exception handling, but if Hive for some reason cannot
access or read the cached query directory, we can't really go back to the
non-cached path, we already exited query compilation once the cache lookup
found a usable cache entry.
Possibly the only option we would have for a failure here would be to invoke
whatever mechanism is used for the ReExecDriver, to re-run the query without
using the cache.
> Disable query results cache for for HiveServer2 doAs=true
> ---------------------------------------------------------
>
> Key: HIVE-19892
> URL: https://issues.apache.org/jira/browse/HIVE-19892
> Project: Hive
> Issue Type: Sub-task
> Reporter: Jason Dere
> Assignee: Jason Dere
> Priority: Major
> Fix For: 3.1.0
>
> Attachments: HIVE-19892.1.patch
>
>
> If running HS2 with doAs=true, the temp query results directory will have
> ownership/permissions based on the doAs user. A subsequent query running as a
> different user may not be able to access this query results directory.
> Results caching will have to be disabled in this case.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
