Return-Path: X-Original-To: apmail-hive-dev-archive@www.apache.org Delivered-To: apmail-hive-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 06A62F307 for ; Thu, 2 May 2013 14:06:17 +0000 (UTC) Received: (qmail 32569 invoked by uid 500); 2 May 2013 14:06:16 -0000 Delivered-To: apmail-hive-dev-archive@hive.apache.org Received: (qmail 32326 invoked by uid 500); 2 May 2013 14:06:16 -0000 Mailing-List: contact dev-help@hive.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@hive.apache.org Delivered-To: mailing list dev@hive.apache.org Received: (qmail 32310 invoked by uid 500); 2 May 2013 14:06:16 -0000 Delivered-To: apmail-hadoop-hive-dev@hadoop.apache.org Received: (qmail 32307 invoked by uid 99); 2 May 2013 14:06:16 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 02 May 2013 14:06:16 +0000 Date: Thu, 2 May 2013 14:06:16 +0000 (UTC) From: "Michael Koehnlein (JIRA)" To: hive-dev@hadoop.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (HIVE-335) External Tables should have the option to be marked Read Only MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/HIVE-335?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13647542#comment-13647542 ] Michael Koehnlein commented on HIVE-335: ---------------------------------------- This would be useful for me, too. We have data on HDFS that belongs to a system user account, and our "normal" users should be able analyze it as an external table. As it is now, the users would need HDFS write permissions on the data directory if they want to create an external table for that directory themselves, although they really only need read permissions. Of course that's not a big obstacle, since we can just let the system user create the external table. It certainly would be nice to get pure read access via external tables, though. > 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 > > 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 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