[jira] [Assigned] (HIVE-17744) Acid LockManager optimization

[Eugene Koifman (Jira)]

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

Eugene Koifman reassigned HIVE-17744:
-

Assignee: (was: Eugene Koifman)

> 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
>Priority: Major
>
> 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
(v8.3.4#803005)

[jira] [Assigned] (HIVE-17744) Acid LockManager optimization

[Eugene Koifman (JIRA)]

 [ 
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)