You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@hive.apache.org by "Paul Yang (JIRA)" <ji...@apache.org> on 2010/11/05 00:46:41 UTC
[jira] Created: (HIVE-1768) Update transident_lastDdlTime only if
not specified
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
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.
[jira] Updated: (HIVE-1768) Update transident_lastDdlTime only if
not specified
Posted by "Namit Jain (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HIVE-1768?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Namit Jain updated HIVE-1768:
-----------------------------
Status: Open (was: Patch Available)
> 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.
[jira] Updated: (HIVE-1768) Update transident_lastDdlTime only if
not specified
Posted by "Paul Yang (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HIVE-1768?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Paul Yang updated HIVE-1768:
----------------------------
Status: Patch Available (was: Open)
> 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.
[jira] Updated: (HIVE-1768) Update transident_lastDdlTime only if
not specified
Posted by "Paul Yang (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HIVE-1768?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Paul Yang updated HIVE-1768:
----------------------------
Attachment: HIVE-1768.1.patch
> 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.
[jira] Commented: (HIVE-1768) Update transident_lastDdlTime only if
not specified
Posted by "Namit Jain (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HIVE-1768?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12928715#action_12928715 ]
Namit Jain commented on HIVE-1768:
----------------------------------
OK
+1
> 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.
[jira] Commented: (HIVE-1768) Update transident_lastDdlTime only if
not specified
Posted by "Paul Yang (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HIVE-1768?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12928714#action_12928714 ]
Paul Yang commented on HIVE-1768:
---------------------------------
Well, the existing behavior is that adding/dropping a partition does not change the transient_lastDdlTimes for the table, so this patch keeps the status quo.
> 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.
[jira] Resolved: (HIVE-1768) Update transident_lastDdlTime only if
not specified
Posted by "Namit Jain (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HIVE-1768?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Namit Jain resolved HIVE-1768.
------------------------------
Resolution: Fixed
Fix Version/s: 0.7.0
Hadoop Flags: [Reviewed]
Committed. Thanks Paul
> 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
> Fix For: 0.7.0
>
> 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.
[jira] Commented: (HIVE-1768) Update transident_lastDdlTime only if
not specified
Posted by "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.