You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hive.apache.org by "Eugene Koifman (JIRA)" <ji...@apache.org> on 2016/05/19 19:58:13 UTC

[jira] [Issue Comment Deleted] (HIVE-13741) TxnHandler.enqueueLockWithRetry() - optimize sql

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

Eugene Koifman updated HIVE-13741:
----------------------------------
    Comment: was deleted

(was: also 
TxnHandler.enqueueLockWithRetry() - this currently adds components that are only being read to TXN_COMPONENTS. This is useless at best since read op don't generate anything to compact. For example, delete from T where t1 in (select c1 from C) - no reason to add C to txn_components but we do.
)

> TxnHandler.enqueueLockWithRetry() - optimize  sql
> -------------------------------------------------
>
>                 Key: HIVE-13741
>                 URL: https://issues.apache.org/jira/browse/HIVE-13741
>             Project: Hive
>          Issue Type: Improvement
>          Components: Metastore, Transactions
>    Affects Versions: 1.0.0
>            Reporter: Eugene Koifman
>   Original Estimate: 3h
>  Remaining Estimate: 3h
>
> TxnHandler.enqueueLockWithRetry()  does SQL insert into 2 tables using (possibly) multiple statements for each.  Could easily generate 1 statement for each table.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)