Search

Big Data Release Notes

Big Data Release Notes

10.2.2 Service Pack 1

Back Next

Mappings and Workflows Fixed Limitations and Closed Enhancements

Mappings and Workflows Fixed Limitations and Closed Enhancements

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

The following table describes fixed limitations:

Bug	Description
MWF-1680	The Data Integration Service can leak memory when you run a large number of workflow applications and the workflows include mappings that run from an operating system profile.
MWF-1668	If you bind a workflow variable to a mapping output, the Data Integration Service does not update the variable value if the mapping output is null.
MWF-1639	If you bind the taskStatus output to an integer variable, a workflow task returns a taskStatus value of 0 regardless of the success or failure of the task.
MWF-1636	The Data Integration Service can generate an excessive quantity of threads and other resources when you run a workflow that sends an email, for example in a Notification task.
MWF-1631	If a workflow runs from an infacmd command and infacmd loses contact with the Data Integration Service, infacmd reports the workflow as failing to start while the workflow starts correctly.
MWF-1621	The workflow engine does not start if it encounters a locked process in the workflow database.
MWF-1597	You can save a workflow in which a task instance does not specify a task to perform, which can cause the workflow to fail at run time.
IDQ-7594	If you run multiple mappings with Match transformations concurrently, the mappings might generate multiple cache data files with the same name. The Data Integration Service might fail to delete all of the cache data files, and therefore the mappings might fail.
IDQ-7162	The Match transformation might not add all matching records to the correct clusters if the transformation input data includes very large record groups.
BDM-20274	If you run a mapping during the last week of the year and the week ends in the next year, the system parameter MappingRunStartTime increments the year by 1. The week begins on Sunday and ends on Saturday. For example, the last week of 2018 included Sunday, December 30th and Monday, December 31st. If you ran a mapping on December 30th or December 31st, the parameter had a value of 12/30/2019 or 12/31/2019 respectively.
BDM-18771	The infacmd wfs upgradeWorkflowParameterFile command can take a long time to complete the upgrade of a set of workflow parameter files.
BDM-18115	The LTRIM and RTRIM functions do not trim spaces when the following conditions are true: An expression is nested in multiple levels of LTRIM or RTRIM functions, such as LTRIM(LTRIM(<expression>)) or RTRIM(LTRIM(<expression>)) . The nested expression references a column in a Hive table that originates from an SQL override.
BDM-17376	You might get unexpected results in a mapping with a Union transformation when the following conditions are true: The Union transformation has at last three input groups. The same two ports are unconnected in all the groups. The mapping contains a downstream transformation that filters data. The transformation might incorrectly filter data that should be retained, or it might retain data that should be filtered out.

The following table describes closed enhancement requests:

Bug	Description
MWF-1638	The Data Integration Service writes log messages to describe workflow engine activity when the workflow engine starts up. The Data Integration Service writes the number of workflow instances that the workflow engine processes to the log. The Data Integration Service also writes the workflow name, application name, and instance ID to the log.

10.2.2 Fixed Limitations and Closed Enhancements

Watch

Comments

0 COMMENTS

We’d like to hear from you! Log in to comment.