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 60BE7DF89 for ; Fri, 5 Oct 2012 12:00:04 +0000 (UTC) Received: (qmail 49700 invoked by uid 500); 5 Oct 2012 12:00:03 -0000 Delivered-To: apmail-hive-dev-archive@hive.apache.org Received: (qmail 49606 invoked by uid 500); 5 Oct 2012 12:00:03 -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 49424 invoked by uid 500); 5 Oct 2012 12:00:03 -0000 Delivered-To: apmail-hadoop-hive-dev@hadoop.apache.org Received: (qmail 49356 invoked by uid 99); 5 Oct 2012 12:00:03 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 05 Oct 2012 12:00:03 +0000 Date: Fri, 5 Oct 2012 12:00:03 +0000 (UTC) From: "Namit Jain (JIRA)" To: hive-dev@hadoop.apache.org Message-ID: <381314027.360.1349438403259.JavaMail.jiratomcat@arcas> Subject: [jira] [Created] (HIVE-3539) add an option in hive where the location for managed tables/partitions cannot be specified MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 Namit Jain created HIVE-3539: -------------------------------- Summary: add an option in hive where the location for managed tables/partitions cannot be specified Key: HIVE-3539 URL: https://issues.apache.org/jira/browse/HIVE-3539 Project: Hive Issue Type: Bug Reporter: Namit Jain Assignee: Namit Jain We run into scenarios where multiple tables/partitions point to the same data. This is OK for external tables, but may create problems for managed tables. An option should be provided to disable this behavior. -- 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