hive-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Eugene Koifman (Jira)" <j...@apache.org>
Subject [jira] [Assigned] (HIVE-15044) LockManager may be too coarse grained
Date Wed, 28 Jul 2021 14:14:03 GMT

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

Eugene Koifman reassigned HIVE-15044:
-------------------------------------

    Assignee:     (was: Eugene Koifman)

> LockManager may be too coarse grained 
> --------------------------------------
>
>                 Key: HIVE-15044
>                 URL: https://issues.apache.org/jira/browse/HIVE-15044
>             Project: Hive
>          Issue Type: Improvement
>          Components: Transactions
>    Affects Versions: 1.0.0
>            Reporter: Eugene Koifman
>            Priority: Major
>
> Consider
> {noformat}
> create table target (a int, b int)
>       partitioned by (p int, q int) clustered by (a) into 2  buckets 
>       stored as orc TBLPROPERTIES ('transactional'='true')")
> insert into target partition(p=1,q) values (1,2,3)
> {noformat}
> this insert will lock the whole table.  See 
> {noformat}
> DbTxnManager.acquireLocks()
> switch (output.getType()) {
>         case DUMMYPARTITION:   //
> {noformat}
> Insert operation runs with SHARED_READ lock but once HIVE-15032 is addressed this will
be an issue for Update/Delete/Merge which use a more restrictive SHARED_WRITE lock.
> This can probably be achieved using "like /db/table/part/*" predicate making the LM operations
more expensive TxnHandler.checkLock()



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

Mime
View raw message