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

Phabricator commented on HIVE-2471:
-----------------------------------

kevinwilfong has commented on the revision "HIVE-2471 [jira] Add timestamp 
column with index to the partition stats table.".

INLINE COMMENTS
  
ql/src/java/org/apache/hadoop/hive/ql/stats/jdbc/JDBCStatsSetupConstants.java:26
 Will do
  ql/src/java/org/apache/hadoop/hive/ql/stats/jdbc/JDBCStatsUtils.java:128 This 
is invoked by the StatsPublisher, it is used for the case where a row was not 
deleted by a previous StatsPublisher, otherwise there is a conflict between the 
primary keys.

  The StatsAggregator only invokes SELECT and DELETE statements.  The 
aggregated stats are added to the metastore via a call to the metastore's 
alter_table method.

REVISION DETAIL
  https://reviews.facebook.net/D2367

                
> Add timestamp column to the partition stats table.
> --------------------------------------------------
>
>                 Key: HIVE-2471
>                 URL: https://issues.apache.org/jira/browse/HIVE-2471
>             Project: Hive
>          Issue Type: Improvement
>            Reporter: Kevin Wilfong
>            Assignee: Kevin Wilfong
>         Attachments: HIVE-2471.1.patch.txt, HIVE-2471.D2367.1.patch, 
> HIVE-2471.D2367.2.patch
>
>
> Occasionally, when entries are added to the partition stats table the program 
> is halted before it can delete those entries, by an exception, keyboard 
> interrupt, etc.  These build up to the point where the table gets very large, 
> and it hurts the performance of the update statement which is often called.  
> In order to fix this, I am adding a column to the table which is 
> auto-populated with the current timestamp.  This will allow us to create 
> scripts that go through periodically and clean out old entries from the table.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Reply via email to