[jira] Commented: (HIVE-1768) Update transident_lastDdlTime only if not specified

["Namit Jain (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/HIVE-1768?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12928703#action_12928703 ] 

Namit Jain commented on HIVE-1768:
----------------------------------

1 Question: Does add partition/drop partition change the transient_lastDdlTime of the table ?
Looks like it does not (from the code) - 

Is that the expected/correct semantics ?

> Update transident_lastDdlTime only if not specified
> ---------------------------------------------------
>
>                 Key: HIVE-1768
>                 URL: https://issues.apache.org/jira/browse/HIVE-1768
>             Project: Hive
>          Issue Type: Improvement
>          Components: Metastore
>    Affects Versions: 0.7.0
>            Reporter: Paul Yang
>            Assignee: Paul Yang
>         Attachments: HIVE-1768.1.patch
>
>
> Currently, whenever a table/partition is created/altered, the field 'transient_lastDdl' time is updated with the current timestamp. For normal operations, this is the desired behavior. However for some housekeeping tasks, it may be helpful if the user could keep the existing value (or set it to something different).
> One example where this is useful is if a partition is copied between clusters. If the last modified time were kept same after the initial copy, it would be easy to know if one partition were overwritten/updated by comparing timestamps.
> This patch alters the behavior of create/alter methods in the metastore API to update the timestamp only if it is not specified in the object.

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