Release Notes (10.4.1.2)

Release Notes (10.4.1.2)

Data Engineering Integration Known Issues (10.4.1.2)

Data Engineering Integration Known Issues (10.4.1.2)

The following table describes known issues:
Issue
Description
BDM-35764
You cannot fetch aggregate logs for applications that run on a Cloudera CDP Public Cloud cluster.
BDM-35582
When the Spark engine runs a mapping on an EMR 6.0 cluster using a Rank transformation that accesses flat file sources and targets, the mapping fails.
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.
Workaround: Edit the Data Integration Service advanced properties to add the following property-value pair:
ExecutionContextOptions.JVMOption1/-Duser.timezone=UTC
BDM-35519
The Spark engine writes an incorrect date to a Hive target on Amazon EMR 6.0 when the mapping source is a flat file Hive source.
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.


Updated March 26, 2021