Metadata Manager 10.4.0
- Metadata Manager 10.4.0
- All Products
When you configure a PowerCenter session to read from or write to a SQL Server stored procedure and if an error occurs in the stored procedure, the output appears in a random order.
When you use a PreSQL or PostSQL statement to write data to a Hive table in a mapping, the SQL statement fails if the following conditions are all true:
This is a Hive 1.2 issue that exists for HDP 2.6. The issue is fixed for Hive version 1.3.0, which is used by HDP 3.1.
Hive ticket reference number: HIVE-12646
Mappings that run on Hortonworks HDP 3.1 cluster might fail when the following conditions are true:
You might see an error like:
Read the Data Integration Service logs for more information about the failure.
Cloudera ticket reference number: 00228458
When you delete contents for Erasure Coding (EC) within the cluster staging directory and run the mapping, the mapping might fail when the auto installer copy sometimes fails to create the XOR codec for raw EC.
When you create a cluster configuration using an Active Directory user on an Azure HDInsight cluster with Enterprise Security Package, the creation of the cluster configuration fails with the following error:
Microsoft ticket reference number: 119042624000873
The Spark engine fails to run a built-in Hive SerDe of type CSV on a Hortonworks HDP 3.1 cluster.
Hortonworks HDP ticket reference number: 00220586
In an Azure HDInsight environment, if you enable Hive merge in an Update Strategy transformation and if Hive is enabled to execute vectorized queries, inserting data into specific columns fails.
Apache Hive ticket reference number: HIVE-14076
Mappings fail on the Spark engine when you configure an SQL override to access a Hive view.
Apache Spark ticket reference number: SPARK-21154.