Informatica Data Quality
- Informatica Data Quality 10.4.0
- All Products
Bug
| Description
|
---|---|
OCON-16421
| 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:
|
BDM-31354
| When the Spark engine runs a mapping, Hive LDAP authentication fails if the following conditions are all true:
SEVERE: Error in connecting to HiveServer2; Exception Class: [java.sql.SQLException] Exception Message: [Could not open client transport with JDBC Uri: jdbc:hive2://emblazeseb01.informatica.com:10000/default;saslQop=auth: Peer indicated failure: Error validating the login]
|
BDM-30923
| The Developer tool does not validate the default value for an output port in an Input transformation.
|
BDM-30914
| Unable to refresh the cluster configuration after upgrading to 10.4.0. The following error occurs:
[DISTRES_10002] version [6.1] is not supported for hadoop distribution [CLOUDERA] in this release. Select from the following available distribution versions :[6.1 (Default), 5.15 ]
Note : this issue occurs only when the cluster configuration distribution version in the previous release was
not marked as default (for example,
6.1 ). Then, in 10.4.0, the same distribution was marked as default (for example,
6.1 (Default) ).
|
BDM-30632
| On the Spark engine, mappings with a reusable mapplet and unused ports take a long time to complete. For example, a mapping with a mapplet, where all input ports are not connected, can take much longer to run than a mapping where all ports are connected.
|
BDM-30203
| The Developer tool fails to validate email addresses if the domain name contains "-".
|
BDM-30008
| If you select the target schema strategy FAIL - Fail mapping if target schema is different and truncate the target Hive table but the target schema from the mapping flow is the same as the schema of the target table, the Spark engine appends data to the target instead of truncating the target table.
|
BDM-29441
| Mappings configured to run using Blaze LLAP fail with "Table not found" error because the Blaze engine does not support LLAP.
|
BDM-29197
| You cannot use node labels when configuring the connection to Hortonworks HDP 3.1 to use Blaze. Mappings fail with an error like:
SEVERE: [CAL_API_1] The Integration Service encountered an unexpected error condition: [java.lang.IllegalArgumentException: Node Label [n2] is not configured in the cluster
|
BDM-29037
| Creating an SQL data service for a flat file data source in the Developer tool intermittently fails with null pointer exception.
|
BDM-27779
| The data preview log file name does not include the mapping name with the transformation name.
|
BDM-25491
BDM-25490
| When a mapping that runs on a Hortonworks HDP 3.1 cluster uses an Update Strategy transformation, and you enabled the Hive Warehouse Connector, the mapping writes incorrect data to rows marked with DD_INSERT.
|
BDM-23751
| When the Spark engine runs a mapping on Hortonworks HDP clusters, the mapping succeeds but truncating external Hive target tables on an HDFS encrypted zone fails with the following error:
WARN Hive: Directory hdfs://XXXXX71.sg.net.intra:8020/data/wm/asia/lab/base/ice_enc/cr_agenda cannot be removed:
java.io.IOException: Failed to move to trash: hdfs://XXXXX71.sg.net.intra:8020/data/wm/asia/lab/base/ice_enc/cr_agenda/part-00000-7d47cef0-e092-4f12-9922-e46d88efe588-c000
|