If a mapping on the Blaze engine reads data from a Hive table and you specify database names in both the Data Access Connection String and in the runtime properties, a SQL override uses the database in the Hive connection instead of the database in the data object.

If a mapping on the Spark engine reads data from a Hive table and you specify the database name in the data object, a SQL override uses the database in the Hive connection instead of the database in the data object.

When you use a Hive connection to create a physical data object with a schema name which is different from the one specified in the Connection String, you cannot use a custom query to read data from a Hive source as the mapping results might be inconsistent.

When you select a Hive table from the

Select a resource

dialog box, the tables from other databases are also selected.

You cannot use the

Show Default Schema Only

option in the Connection Explorer to show tables that use the default schema and to add tables from non-default schemas.

When you run a Hive mapping to read data from a custom data object and the source has two Hive tables with same name but from different databases, the mapping fails.

When you run a mapping in the native environment to write data to a Hive target, the mapping runs successfully. However, the session log displays the following error:

java.lang.ArrayIndexOutOfBoundsException