In this article, I will describe the impact of the Hive ACID activation on a running cluster HDP 2.6.4<\/p>\n
\u00a0<\/p>\n\n\n\n\n\n\n\n
When you use Hive without ACID activation and you decide to activate it, be careful as you will have some collateral effect on 2.6.4.<\/p>\n
Te Hive Acid activation change the transactional manager from :<\/p>\n
To<\/p>\n The big impact is the way of Hive manage the locks even for no transactionnal tables as describe in Hive documentation<\/a> about LockManager .<\/p>\n This could dramatically increase processing times of all your jobs using Hive<\/strong>.<\/p>\n You could use the parameter hive.txn.strict.locking.mode<\/a> to manage the behavior of the LockManager even if the documentation said that it is only available since Hive 2.2, use set -v to show presence of this parameter in Hive 1.2.1000.<\/p>\n This parameter could be set on the server<\/strong> and client<\/strong> side, so set it to false<\/strong> in the hive server configuration and true<\/strong> in the client when you want to use a transactionnal table.<\/p>\n You could hit 2 bugs too :<\/p>\nhive.txn.manager=org.apache.hadoop.hive.ql.lockmgr.DummyTxnManager<\/code><\/p>\nhive.txn.manager=org.apache.hadoop.hive.ql.lockmgr.DbTxnManager<\/code><\/p>\n