Release Notes

10.5
- 10.5.4.1
- 10.5.4
- 10.4.1
- 10.4.0

Back Next

Data Engineering Integration Fixed Issues (10.5)

Review the Release Notes of previous releases for information about previous fixed issues.

The following table describes fixed issues:

Issue	Description
PLAT-27952	Failed to set the AuthnContextClassRef to unspecified in the SAML request.
OCON-27284	If you specify more than one table in the custom query, the Sqoop mapping fails.
CORE-8958	When you run a mapping that reads from a Hive source on a Cloudera CDP cluster, the mapping fails with the following error: java.lang.NoClassDefFoundError: org/apache/jute/Record
BDM-37291	You receive the following error message when you run mappings with Java transformation on the Blaze engine: Not enough remaining space to put block of size
BDM-37177	The ADD_TO_DATE function returns different results on the Native engine and Spark engine when you subtract or add data from months that have different numbers of days. For example, when you subtract 1 month from March 31, 2021, the result should be February 28, 2021; however it was returning March 3, 2021.
BDM-36786	Memory leak occurs in the Data Integration Service when the applicationInfoImpl objects failed to get deleted and increases heap size.
BDM-36445 BDM-36513	Reject file on Data Lake is not supported for Spark Engine and Blaze Engine.
BDM-36415	If a mapping uses a parameter value to specify the execution environment, and you specify "native" or "Hadoop" as arguments when running one of the following commands, the Data Integration Service ignores the command and the mapping is not updated.
BDM-36047	Information about the DTM ID to the mapping name information are missing in the Data Integration Service logs.
BDM-35868	Mapping performance is degraded after an upgrade from 10.2x.
BDM-35667	When the Spark engine runs a mapping the mapping fails with an error like: SEVERE: Data integration service failed to create DTM instance because of the following error: java.lang.UnsupportedOperationException: PARAM_READ ...
BDM-35624	When Spark runs a mapping with a connected Lookup transformation, the mapping fails with an error like org.apache.spark.sql.AnalysisException.
BDM-35539	When the Blaze engine runs a mapping with a Parquet target containing the Date data type on a Hortonworks cluster version earlier than 3.1.5, the mapping writes incorrect TIMESTAMP data to the target.
BDM-35505	Ephemeral cluster creation fails on concurrent workflow runs with "java.lang.IllegalArgumentException: Parameter 'directory' is not a directory".
BDM-35493	DTM processes hang and block profile job execution when you cancel a large number of small mappings.
BDM-35466	When the Blaze engine runs a mapping on Cloudera CDP Public Cloud clusters on AWS, the mapping might fail with the following error: [GRIDDTM_1016] The Integration Service failed to execute grid mapping with following error [An internal exception occurred with message: java.lang.IllegalStateException: Authentication with IDBroker failed. Please ensure you have a Kerberos token by using kinit. The mapping fails if either of the following conditions is true: The mapping reads from a Hive table and writes to a flat file. The mapping uses an Amazon S3 connection.
BDM-35459	The Email Service sends repeated notifications after every 20 seconds even when there is no email communication.
BDM-34663	When the Spark engine runs a mapping with a Hive source with Select distinct enabled on a Hortonworks HDP 3.1 cluster, the mapping fails because the SQL statement to create the Hive staging table is incorrect.
BDM-34540	When the Spark engine runs a mapping with a Hive source created with a SORT clause on a Hortonworks HDP 3.1 cluster, the mapping fails because the SQL statement for the Hive staging table is incorrect.
BDM-34036	When the Spark engine runs a mapping or previews data on a Cloudera CDP cluster, the job incorrectly writes date/time data to the target when the date is earlier than 1583 and the mapping uses one of the following sources: Azure Blob Google BigQuery JDBC V2 Sqoop Complex file objects
BDM-33915	When the Blaze engines performs a lookup on a compressed Hive table of text format, the mapping fails with the following error: "[CORE_3] An internal exception occurred with message: java.io.IOException: incorrect header check java.io.IOException: incorrect header check"
BDM-33914	When the Blaze engine reads a modified Hive partition table of text format, the source read fails with the following error: "[CORE_3] An internal exception occurred with message: java.lang.RuntimeException: No data found for parttion state java.lang.RuntimeException: No data found for parttion state"
BDM-33784	Mappings on the SPARK engine fail with an "out of memory" error message.
BDM-33713	Mappings fail when you create a Hive table and Oracle table as a source to join using the Joiner transformation under the following circumstances: You use the Update Strategy transformation in the mapping pipeline to connect the required ports to all targets. You propagate only a few ports from the Hive source.
BDM-30668	The LogPacker fails to collect the infacco-site.xml or CCO export inside.
BDM-30664	When a mapping reads from a Hive table to a sequence generator, an expression, and two different targets, you get different values in the two targets.
BDM-28678	Joiner and Lookup mappings time out and fail when all of the following conditions are true: The mapping has a flat file source. The mapping includes a Joiner or Lookup transformation. The mapping is configured to use Azure HDInsight version 4.0.
BDM-27878	Email Service is unavailable for high availability and failover.
BDM-23317	When you monitor statistics for the Data Integration Service configured with file-based queuing, the jobs incorrectly appear to run even when the job state is queued.
BDM-23221	Informatica product version number is not available in session log files when a session is started after LDTM creation.
BDM-22677	When you create a Cloudera CDP cluster configuration and connection during installation, the installer uses the default engine type, MRv2, rather than Tez in the Hadoop connection.
BDM-21820	The Data Integration Service process gets stopped when any of the command task running in the Data Integration Service workflows gets SIGTTOU.

Rename Saved Search

Table of Contents

Release Notes

Release Notes

Data Engineering Integration Fixed Issues (10.5)

Data Engineering Integration Fixed Issues (10.5)