hive-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Eugene Koifman (JIRA)" <>
Subject [jira] [Commented] (HIVE-13646) make hive.optimize.sort.dynamic.partition compatible with ACID tables
Date Tue, 03 May 2016 23:33:12 GMT


Eugene Koifman commented on HIVE-13646:

The fix makes Acid queries respect hive.optimize.sort.dynamic.partition setting.  In case
of update/delete the query plan is not optimal (it has 2 ReduceSinks which will be addressed
in a separate ticket)  but now the user has a choice of whether to use hive.optimize.sort.dynamic.partition.

thanks Wei for the review

> make hive.optimize.sort.dynamic.partition compatible with ACID tables
> ---------------------------------------------------------------------
>                 Key: HIVE-13646
>                 URL:
>             Project: Hive
>          Issue Type: Bug
>          Components: Transactions
>    Affects Versions: 1.0.0
>            Reporter: Eugene Koifman
>            Assignee: Eugene Koifman
>            Priority: Critical
>         Attachments: HIVE-13646.2.patch, HIVE-13646.patch
>   Original Estimate: 168h
>  Remaining Estimate: 168h
> HIVE-8875 disabled hive.optimize.sort.dynamic.partition for ACID queries.
> dynamic inserts are common in ACID and this leaves users with few options if they are
seeing OutOfMemory errors due to too many writers.
> hive.optimize.sort.dynamic.partition sorts data by partition col/bucket col/sort col
to ensure each reducer only needs 1 writer.
> Acid requires data in each bucket file to be sorted by ROW__ID and thus doesn't allow
end user to determine sorting.
> So we should be able to support hive.optimize.sort.dynamic.partition with
> sort on partition col/bucket col/ROW__ID 

This message was sent by Atlassian JIRA

View raw message