[jira] [Updated] (HIVE-17970) MM LOAD DATA with OVERWRITE doesn't use base_n directory concept

["Eugene Koifman (JIRA)" <ji...@apache.org>]

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

Eugene Koifman updated HIVE-17970:
----------------------------------
    Summary: MM LOAD DATA with OVERWRITE doesn't use base_n directory concept  (was: LOAD DATA with OVERWRITE doesn't use base_n directory concept)

> MM LOAD DATA with OVERWRITE doesn't use base_n directory concept
> ----------------------------------------------------------------
>
>                 Key: HIVE-17970
>                 URL: https://issues.apache.org/jira/browse/HIVE-17970
>             Project: Hive
>          Issue Type: Sub-task
>          Components: Transactions
>    Affects Versions: 3.0.0
>            Reporter: Eugene Koifman
>
> Judging by 
> {code:java}
> Hive.loadTable(Path loadPath, String tableName, LoadFileType loadFileType, boolean isSrcLocal,
>       boolean isSkewedStoreAsSubdir, boolean isAcid, boolean hasFollowingStatsTask,
>       Long txnId, int stmtId, boolean isMmTable)
> {code}
> LOAD DATA with OVERWRITE will delete all existing data then write new data into the table.  This logic makes sense for non-acid tables but for Acid/MM it should work like INSERT OVERWRITE statement and write new data to base_n/. This way the lock manager can be used to either get an X lock for IOW and thus block all readers or let it run with SemiShared and let readers continue and make the system more concurrent.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)