You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@hive.apache.org by "Brock Noland (JIRA)" <ji...@apache.org> on 2014/11/21 22:55:33 UTC

[jira] [Commented] (HIVE-8945) Allow user to read encrypted read-only tables only if the scratch directory is encrypted

    [ https://issues.apache.org/jira/browse/HIVE-8945?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14221478#comment-14221478 ] 

Brock Noland commented on HIVE-8945:
------------------------------------

+1

> Allow user to read encrypted read-only tables only if the scratch directory is encrypted
> ----------------------------------------------------------------------------------------
>
>                 Key: HIVE-8945
>                 URL: https://issues.apache.org/jira/browse/HIVE-8945
>             Project: Hive
>          Issue Type: Sub-task
>            Reporter: Sergio Peña
>            Assignee: Sergio Peña
>         Attachments: HIVE-8945.1.patch
>
>
> With the changes for hdfs encryption, hive creates a staging directory inside table locations. If an user access a table as read-only access, then the staging directory is created in the old scratch directory (hive.exec.scratchdir). 
> This does not work if the table to access is encrypted for security reasons. We don't want that encrypted data is written to an unencrypted zone. But, if the scratch directory is encrypted? Then we should allow the access.
> This bug is to fix that.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)