hive-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Alan Gates (JIRA)" <>
Subject [jira] [Commented] (HIVE-11649) Hive UPDATE,INSERT,DELETE issue
Date Mon, 21 Sep 2015 16:04:04 GMT


Alan Gates commented on HIVE-11649:

      Set to org.apache.hadoop.hive.ql.lockmgr.DbTxnManager as part of turning on Hive
      transactions, which also requires appropriate settings for hive.compactor.initiator.on,
      hive.compactor.worker.threads, (true), hive.enforce.bucketing
      (true), and hive.exec.dynamic.partition.mode (nonstrict).
      The default DummyTxnManager replicates pre-Hive-0.13 behavior and provides
      no transactions.

This should be DbTxnManager if you want to use update and delete.  It won't work with DummyTxnManager.
 The reason it's taking a long time is when you set the txn manager to Dummy and the concurrency
to true you get the zookeeper lock manager, which is taking time trying to connect to zookeeper.

> -------------------------------
>                 Key: HIVE-11649
>                 URL:
>             Project: Hive
>          Issue Type: Bug
>         Environment: Hadoop-2.2.0 , hive-1.2.0 ,operating system ubuntu14.04lts (64-bit)
& Java 1.7
>            Reporter: Veerendra Nath Jasthi
>            Assignee: Hive QA
>         Attachments: afterChange.png, beforeChange.png, hive-site.xml, hive.log
>  have been trying to implement the UPDATE,INSERT,DELETE operations in hive table as per

> but whenever I was trying to include the properties which will do our work i.e. 
> Configuration Values to Set for INSERT, UPDATE, DELETE 
>	true (default is false) 
> hive.enforce.bucketing	true (default is false) 
> hive.exec.dynamic.partition.mode	nonstrict (default is strict) 
> after that if I run show tables command on hive shell its taking 65.15 seconds which
normally runs at 0.18 seconds without the above properties. 
> Apart from show tables rest of the commands not giving any output i.e. its keep on running
until and unless kill the process.
> Could you tell me reason for this?

This message was sent by Atlassian JIRA

View raw message