Page History

...

Set to true to support INSERT ... VALUES, UPDATE, and DELETE  transactions (Hive 0.14.0 and later). For a complete list of parameters required for turning on transactions, see hive.txn.manager.

hive.enforce.sorting

• Default Value: false
• Added In: Hive 0.6.0

...

Set to nonstrict to support INSERT ... VALUES, UPDATE, and DELETE  transactions (Hive 0.14.0 and later). For a complete list of parameters required for turning on transactions, see hive.txn.manager.

hive.exec.max.dynamic.partitions

...

• hive.txn.manager
• hive.compactor.initiator.on
• hive.compactor.worker.threads

These parameters must also have non-default values to turn on Hive transactions:

• hive.support.concurrency
• hive.enforce.bucketing
• hive.exec.dynamic.partition.mode

hive.txn.manager

• Default Value: org.apache.hadoop.hive.ql.lockmgr.DummyTxnManager
• Hive Transactions Value: org.apache.hadoop.hive.ql.lockmgr.DbTxnManager
• Added In: Hive 0.13.0 with HIVE-5843

To turn on Hive transactions, set Set this to org.apache.hadoop.hive.ql.lockmgr.DbTxnManager as part of turning on Hive transactions. The default DummyTxnManager replicates pre-Hive-0.13 behavior and provides no transactions.

Turning on Hive transactions also requires appropriate settings for hive.compactor.initiator.on, hive.compactor.worker.threads, hive.support.concurrency, hive.enforce.bucketing, and hive.exec.dynamic.partition.mode.

hive.txn.timeout

• Default Value: 300
• Added In: Hive 0.13.0 with HIVE-5843

...

Whether to run the initiator and cleaner threads on this metastore instance. Set this to true on one instance of the Thrift metastore service to turn on Hive transactions.service as part of turning on Hive transactions. For a complete list of parameters required for turning on transactions, see hive.txn.manager.

hive.compactor.worker.threads

...

How many compactor worker threads to run on this metastore instance. Set this to a positive number on one or more instances of the Thrift metastore service to turn on Hive transactionsservice as part of turning on Hive transactions. For a complete list of parameters required for turning on transactions, see hive.txn.manager.

Worker threads spawn MapReduce jobs to do compactions. They do not do the compactions themselves. Increasing the number of worker threads will decrease the time it takes tables or partitions to be compacted once they are determined to need compaction. It will also increase the background load on the Hadoop cluster as more MapReduce jobs will be running in the background.

...

Whether Hive supports concurrency or not. A Zookeeper instance must be up and running for the default Hive lock manager to support read-write locks.

Set to true to support INSERT ... VALUES, UPDATE, and DELETE transactions (Hive 0.14.0 and later). For a complete list of parameters required for turning on Hive transactions, see hive.txn.manager.

hive.lock.mapred.only.operation

...