When you import a Hive mapping enabled with the truncate table target option for a Hive non-ACID table and run it from the native environment, the truncate query does not work and the mapping fails.

When a Blaze engine runs a mapping on the Cloudera CDH version 6.3.4 cluster to write data that contains single-byte ASCII delimiters to a Hive target, the mapping incorrectly writes the delimiters to the target.

Workaround: Create a Hive target table with the delimiter or octal code character and then run the mapping.

When you change the table metadata in the Developer Tool by modifying the existing data type in a Hive mapping that reads data from a Hive source and do not synchronize the Physical Data Object (PDO), the mapping fails with the following error:

FAILED: SemanticException [Error 10044]: Line 1:23 Cannot insert into target table because column number/types are different

Workaround: Synchronize the Physical Data Object and run the mapping again.

When you synchronize a Hive object that contains complex datatypes in the Developer tool, the links between the hive objects in the mapping are not retained.