Changes after upgrading to Apache Hive 3
To locate and use your Apache Hive 3 tables after an upgrade, you need to understand the changes that occur during the upgrade process. Changes to the location of tables, permissions to HDFS directories, table types, and ACID-compliance occur.
Hive changes to ACID properties
Hive 2.x and 3.x have transactional and non-transactional tables. Transactional tables have atomic, consistent, isolation, and durable (ACID) properties. In Hive 2.x, the initial version of ACID transaction processing is ACID v1. In Hive 3.x, the mature version of ACID is ACID v2, which is the default table type in HDP 3.0.
Native and non-native storage formats
Storage formats are a factor in upgrade changes to table types. Hive 2.x and 3.x supports the following Hadoop native and non-native storage formats:
- Native: Tables with built-in support in Hive, such as those in the following file
- Sequence File
- RC File
- AVRO File
- ORC File
- Parquet File
- Non-native: Tables that use a storage handler, such as the DruidStorageHandler or HBaseStorageHandler
HDP 3.x upgrade changes to table types
|HDP 2.x||HDP 3.x|
|Table Type||ACID v1||Format||Owner (user) of Hive Table File||Table Type||ACID v2|
|External||No||Native or non-native||hive or non-hive||External||No|
|Managed||Yes||ORC||hive or non-hive||Managed, updatable||Yes|
|Managed||No||Native (but non-ORC)||hive||Managed, insert only||Yes|
|Managed||No||Non-native||hive or non-hive||External||No|
Other HDP 3.x upgrade changes
Managed, ACID tables that are not owned by the
hive user remain managed tables after the upgrade, but
hive becomes the owner.
After the upgrade, the format of a Hive table is the same as before the upgrade. For example, native or non-native tables remain native or non-native, respectively.
After the upgrade, the location of managed tables or partitions do not change under any one of the following conditions:
- The old table or partition directory was not in its default location
/apps/hive/warehousebefore the upgrade.
- The old table or partition is in a different file system than the new warehouse directory.
- The old table or partition directory is in a different encryption zone than the new warehouse directory.
Otherwise, the location of managed tables or partitions does change: The upgrade process moves managed files to
/warehouse/tablespace/managed/hive. By default, Hive places any new external tables you create in HDP 3.x in
/apps/hive directory, which is the former location of the Hive 2.x warehouse, might or might not exist in HDP 3.x.
ACID table conversion
During the upgrade process, you can override the conversion of ACID v1 tables to ACID v2. For example, you can choose to first convert everything except ACID v1 tables to external tables, and then later convert them to ACID tables one by one.
ALTER TABLE T3 SET TBLPROPERTIES ('transactional'='true');