Mailing-List: contact dev-help@hive.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@hive.apache.org
Date: Fri, 1 Feb 2013 06:31:14 +0000 (UTC)
From: "Kevin Wilfong (JIRA)" <jira@apache.org>
To: hive-dev@hadoop.apache.org
Message-ID: <JIRA.12630287.1359688079770.228049.1359700274017@arcas>
In-Reply-To: <JIRA.12630287.1359688079770@arcas>
References: <JIRA.12630287.1359688079770@arcas>
Subject: [jira] [Updated] (HIVE-3970) Clean up/fix
 PartitionNameWhitelistPreEventListener
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


     [ https://issues.apache.org/jira/browse/HIVE-3970?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Kevin Wilfong updated HIVE-3970:
--------------------------------

    Status: Patch Available  (was: Open)
    
> Clean up/fix PartitionNameWhitelistPreEventListener
> ---------------------------------------------------
>
>                 Key: HIVE-3970
>                 URL: https://issues.apache.org/jira/browse/HIVE-3970
>             Project: Hive
>          Issue Type: Improvement
>          Components: Metastore
>    Affects Versions: 0.11.0
>            Reporter: Kevin Wilfong
>            Assignee: Kevin Wilfong
>         Attachments: HIVE-3970.1.patch.txt
>
>
> There are a number of issues and things which can be cleaned up related to PartitionNameWhitelistPreEventListener.
> * It's an event listener, but it really doesn't need to be given that the regex whitelist is configurable, it could just be a utility method.
> * It's not run when a partition is renamed, so partitions with invalid characters can be created in this way.
> * There's no easy way to check if a partition contains invalid characters before creating it and seeing if it fails.
> Most importantly, when a dynamic partition contains an invalid character, the directory for this partition is created, and the data is moved into it, but the partition fails to be created leaving an orphan directory.

--
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