[
https://issues.apache.org/jira/browse/HIVE-335?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16790077#comment-16790077
]
Jim Huang commented on HIVE-335:
--------------------------------
I am also searching for this feature. It seems the workaround will be more
complicated now that Apache Ranger maybe another level of check being enforced.
If the dataset in question is small enough and Apache Ranger rules allows data
copy, the most naive way is to duplicate that dataset as a workaround to this
problem.
> External Tables should have the option to be marked Read Only
> -------------------------------------------------------------
>
> Key: HIVE-335
> URL: https://issues.apache.org/jira/browse/HIVE-335
> Project: Hive
> Issue Type: Improvement
> Components: Metastore, Query Processor
> Reporter: Richard Lee
> Priority: Major
>
> When creating an External Table, it'd be awesome to have the option of NOT
> allowing writes to it (disallow any INSERTs or if hive ever allows UPDATEs).
> Adding and Dropping Partitions should still be allowed.
> This will enable hive to "play well" with external data stores other than
> hdfs where data should be non-maleable.
> I'd recomend the following syntax, which applies ONLY to external tables:
> CREATE EXTERNAL [READONLY] TABLE ...
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
