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-17744) Acid LockManager optimization
Date Mon, 09 Oct 2017 00:04:00 GMT

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

Eugene Koifman reassigned HIVE-17744:
-------------------------------------


> Acid LockManager optimization
> -----------------------------
>
>                 Key: HIVE-17744
>                 URL: https://issues.apache.org/jira/browse/HIVE-17744
>             Project: Hive
>          Issue Type: Bug
>          Components: Transactions
>            Reporter: Eugene Koifman
>            Assignee: Eugene Koifman
>
> does it make sense to periodically compute and store min(lock_id) of a Write/semi shared
lock to know that all earlier locks are Read locks and thus don't need to be even retrieved
from storage to check if a new Read/semi shared lock can be granted?



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

Mime
View raw message