[
https://issues.apache.org/jira/browse/HIVE-4046?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13582772#comment-13582772
]
Carl Steinbach commented on HIVE-4046:
--------------------------------------
Here's what I meant:
{code}
CREATE TABLE emp (
name STRING,
title STRING,
salary INT
);
CREATE VIEW emp_masked AS
SELECT name, title, NULL
FROM emp;
{code}
Then use authorization to restrict access to the underlying emp table.
Regardless of which approach is used, I think it would be good to write up a
proposal explaining the functional and implementation details before writing
any code.
> Column masking
> --------------
>
> Key: HIVE-4046
> URL: https://issues.apache.org/jira/browse/HIVE-4046
> Project: Hive
> Issue Type: New Feature
> Components: Authorization, CLI, Metastore, Query Processor, Security
> Affects Versions: 0.11.0
> Reporter: Samuel Yuan
> Assignee: Samuel Yuan
>
> Sometimes data in a table needs to be kept around but made inaccessible.
> Right now it is possible to offline a table or a partition, but not a
> specific column of a partition. Also, accessing an offlined table results in
> an error. With this change, it will be possible to mask a column at the
> partition level, causing all further queries to that column to return null.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
