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 5783FF938 for ; Thu, 25 Apr 2013 05:18:23 +0000 (UTC) Received: (qmail 53332 invoked by uid 500); 25 Apr 2013 05:18:22 -0000 Delivered-To: apmail-hive-dev-archive@hive.apache.org Received: (qmail 53077 invoked by uid 500); 25 Apr 2013 05:18:21 -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 52986 invoked by uid 500); 25 Apr 2013 05:18:21 -0000 Delivered-To: apmail-hadoop-hive-dev@hadoop.apache.org Received: (qmail 52951 invoked by uid 99); 25 Apr 2013 05:18:20 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 25 Apr 2013 05:18:20 +0000 Date: Thu, 25 Apr 2013 05:18:20 +0000 (UTC) From: "Teddy Choi (JIRA)" To: hive-dev@hadoop.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Updated] (HIVE-3846) alter view rename NPEs with authorization on. 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-3846?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Teddy Choi updated HIVE-3846: ----------------------------- Status: Patch Available (was: In Progress) > alter view rename NPEs with authorization on. > --------------------------------------------- > > Key: HIVE-3846 > URL: https://issues.apache.org/jira/browse/HIVE-3846 > Project: Hive > Issue Type: Bug > Components: Authorization > Affects Versions: 0.10.0, 0.11.0 > Reporter: Ashutosh Chauhan > Assignee: Teddy Choi > Attachments: HIVE-3846.1.patch.txt > > -- 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