[
https://issues.apache.org/jira/browse/HIVE-2777?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13420102#comment-13420102
]
Aniket Mokashi commented on HIVE-2777:
--------------------------------------
Thanks Namit. We are using S3 as our storage, which doesnt support move
operation. Hence, to replace n number of partitions with one, we need to
support that only through metadata api. In following api, for the given db and
tbl_name, addParts partition list will be added to metastore and dropParts
partitions will be deleted, atomically. Hence, users querying of one level up
of partition hierarchy would not know that the partitions were replaced with
data with a better representation (merged into bigger files, sorted etc.)
add_drop_partitions(String db, String tbl_name, List<Partition> addParts,
List<List<String>> dropParts, boolean deleteData);
Any downsides of this approach?
> ability to add and drop partitions atomically
> ---------------------------------------------
>
> Key: HIVE-2777
> URL: https://issues.apache.org/jira/browse/HIVE-2777
> Project: Hive
> Issue Type: New Feature
> Components: Metastore
> Reporter: Aniket Mokashi
> Assignee: Aniket Mokashi
> Attachments: HIVE-2777.D2271.1.patch
>
>
> Hive should have ability to atomically add and drop partitions. This way
> admins can change partitions atomically without breaking the running jobs. It
> allows admin to merge several partitions into one.
> Essentially, we would like to have an api- add_drop_partitions(String db,
> String tbl_name, List<Partition> addParts, List<List<String>> dropParts,
> boolean deleteData);
> This jira covers changes required for metastore and thrift.
--
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
