Mailing-List: contact hive-dev-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: hive-dev@hadoop.apache.org
Message-ID: <21467144.20751277237216065.JavaMail.jira@thor>
Date: Tue, 22 Jun 2010 16:06:56 -0400 (EDT)
From: "Ning Zhang (JIRA)" <jira@apache.org>
To: hive-dev@hadoop.apache.org
Subject: [jira] Assigned: (HIVE-1394) do not update transient_lastDdlTime if
 the partition is modified by a housekeeping operation
In-Reply-To: <10516517.30131276021877162.JavaMail.jira@thor>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Ning Zhang reassigned HIVE-1394:
--------------------------------

    Assignee: Ning Zhang  (was: Paul Yang)

> do not update transient_lastDdlTime if the partition is modified by a housekeeping operation
> --------------------------------------------------------------------------------------------
>
>                 Key: HIVE-1394
>                 URL: https://issues.apache.org/jira/browse/HIVE-1394
>             Project: Hadoop Hive
>          Issue Type: Improvement
>          Components: Query Processor
>            Reporter: Namit Jain
>            Assignee: Ning Zhang
>         Attachments: HIVE-1394.patch
>
>
> Currently. purging looks at the hdfs time to see the last time the files got modified.
> It should look at the metastore property instead - these are facebook specific utilities, which do not require any changes to hive.
> However, in some cases, the operation might be performed by some housekeeping job, which should not modify the timestamp.
> Since, hive has no way of knowing the origin of the query, it might be a good idea to add a new hint which specifies that the 
> operation is a cleanup operation, and the timestamp in the metastore need not be touched for that scenario.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.