You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@impala.apache.org by "Vihang Karajgaonkar (Jira)" <ji...@apache.org> on 2020/12/23 18:51:01 UTC

[jira] [Resolved] (IMPALA-2513) Add Table Locking Capability

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

Vihang Karajgaonkar resolved IMPALA-2513.
-----------------------------------------
    Resolution: Won't Fix

I am closing this as "Won't fix" for now. Please feel free to reopen if you think otherwise and we will be happy to discuss more.

> Add Table Locking Capability
> ----------------------------
>
>                 Key: IMPALA-2513
>                 URL: https://issues.apache.org/jira/browse/IMPALA-2513
>             Project: IMPALA
>          Issue Type: New Feature
>          Components: Catalog
>    Affects Versions: Impala 2.2.4
>            Reporter: Jacob Davis
>            Priority: Major
>              Labels: catalog-server
>
> When running multiple concurrent INSERT OVERWRITE statements on a table, the result is that only the last to be executed is done successfully.  Running the same process via Hive will result in each statement running sequentially due to the locking behavior.
> The request is to add similar locking functionality within Impala.  Ideally, it would work across with Hive so that queries executed from Hive and Impala would both honor the locks.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)