THIS IS A TEST INSTANCE. ALL YOUR CHANGES WILL BE LOST!!!!
...
INSERT...VALUES, UPDATE, and DELETE have been added to the SQL grammar, starting in Hive 0.14. See LanguageManual DML for details.
...
A number of new configuration values parameters have been added to the system to support transactions.
...
Configuration Values to Set for INSERT, UPDATE, DELETE
In addition to the new values parameters listed above, some existing values parameters need to be set to support INSERT, UPDATE, and DELETE.
| Configuration Valuekey | Must be set to |
|---|---|
| hive.enforce.bucketing | true |
| hive.exec.dynamic.partition.mode | nonstrict |
Configuration Values to Set for Compaction
If the data in your system is not owned by the Hive user (i.e., the user that the Hive metastore runs as), then Hive will need permission to run as the user who owns the data in order to perform compactions. If you have already set up HiveServer2 to impersonate users, then the only additional work to do is assure that Hive has the right to impersonate users from the host running the Hive metastore. This is done by adding the hostname to hadoop.proxyuser.hive.hosts in Hadoop's core-site.xml file. If you have not already done this, then you will need to configure Hive to act as a proxy user. This requires you to set up keytabs for the user running the Hive metastore and add hadoop.proxyuser.hive.hosts and hadoop.proxyuser.hive.groups to Hadoop's core-site.xml file. See the Hadoop documentation on secure mode for your version of Hadoop (e.g., for Hadoop 2.5.1 it is at Hadoop in Secure Mode).
Table Properties
...