Data loss might occur for some of the targets when you run a streaming mapping with a single JMS source and multiple targets after you configure durable subscriptions. Only one of the multiple targets receives the data.

When dynamic schema strategy is enabled in a streaming mapping that has a Kafka source and Complex File data object target with no column projection, the target files are not moved to the target directory. This issue occurs when the executor goes to a dead state. The target files are moved as part of cleanup.

When you run a streaming mapping with a Microsoft Azure Data Lake Storage Gen2 or HDFS target that has Parquet payload on the Hortonworks HDP version 3.1.5 distribution, the target files are not moved to the target directory after clean up when the mapping is stopped and the log file does not record the error.

When you run a streaming mapping with an HDFS target that has Parquet payload on an unsecured Cloudera CDH cluster, the target files are not moved to the target directory after clean up when the mapping is stopped.