hive-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jesus Camacho Rodriguez (JIRA)" <j...@apache.org>
Subject [jira] [Comment Edited] (HIVE-19490) Locking on Insert into for non native and managed tables.
Date Mon, 28 May 2018 16:45:00 GMT

    [ https://issues.apache.org/jira/browse/HIVE-19490?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16492821#comment-16492821
] 

Jesus Camacho Rodriguez edited comment on HIVE-19490 at 5/28/18 4:44 PM:
-------------------------------------------------------------------------

Pushed to master, branch-3.

Cc [~vgarg]


was (Author: jcamachorodriguez):
Pushed to master, branch-3.

> Locking on Insert into for non native and managed tables.
> ---------------------------------------------------------
>
>                 Key: HIVE-19490
>                 URL: https://issues.apache.org/jira/browse/HIVE-19490
>             Project: Hive
>          Issue Type: Improvement
>          Components: Druid integration
>            Reporter: slim bouguerra
>            Assignee: slim bouguerra
>            Priority: Blocker
>              Labels: druid, locking
>             Fix For: 3.1.0, 4.0.0
>
>         Attachments: HIVE-19490.2.patch, HIVE-19490.3.patch, HIVE-19490.4.patch, HIVE-19490.5.patch,
HIVE-19490.6.patch, HIVE-19490.6.patch, HIVE-19490.7.patch, HIVE-19490.patch
>
>
> Current state of the art: 
> Managed non native table like Druid Tables, will need to get a Lock on Insert into or
insert Over write. The nature of this lock is set to Exclusive by default for any non native
table.
> This implies that Inserts into Druid table will Lock any read query as well during the
execution of the insert into. IMO this lock (on insert into) is  not needed since the insert
statement is appending data and the state of loading it is managed partially by Hive Storage
handler hook and part of it by Druid. 
> What i am proposing is to relax the lock level to shared for all non native tables on
insert into operations and keep it as Exclusive Write for insert Overwrite for now.
>  
> Any feedback is welcome.
> cc [~ekoifman] / [~ashutoshc] / [~jdere] / [~hagleitn]
> Also am not sure what is the best way to unit test this currently am using debugger to
check if locks are what i except, please let me know if there is a better way to do this. 
>  



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

Mime
View raw message