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

Prasanth Jayachandran updated HIVE-20707:
-----------------------------------------
    Description: In current scenario, to add partitions for external tables to 
metastore, MSCK REPAIR command has to be executed manually. To avoid this 
manual step, external tables can be specified a table property based on which a 
background metastore thread can sync partitions periodically. Tables can also 
be specified with partition retention period. Any partition whose age exceeds 
the retention period will be dropped automatically.  (was: In current scenario, 
to add partitions for external tables to metastore, MSCK REPAIR command has to 
be executed manually. To avoid this manual step, external tables can be 
specified a table property (for retention policy) based on which a background 
metastore thread can add/drop/sync partitions periodically. The retention 
policy can be generically extended to managed tables as well (provided 
appropriate locks are obtained for adding and dropping partitions))

> Automatic partition management
> ------------------------------
>
>                 Key: HIVE-20707
>                 URL: https://issues.apache.org/jira/browse/HIVE-20707
>             Project: Hive
>          Issue Type: New Feature
>    Affects Versions: 4.0.0
>            Reporter: Prasanth Jayachandran
>            Assignee: Prasanth Jayachandran
>            Priority: Major
>         Attachments: HIVE-20707.1.patch
>
>
> In current scenario, to add partitions for external tables to metastore, MSCK 
> REPAIR command has to be executed manually. To avoid this manual step, 
> external tables can be specified a table property based on which a background 
> metastore thread can sync partitions periodically. Tables can also be 
> specified with partition retention period. Any partition whose age exceeds 
> the retention period will be dropped automatically.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Reply via email to