The availability of the following new features, enhancements and corrected issues is dependent on the installed edition of the product and licensed features.
Data360 Analyze 3.16.1 hotfix v2 release
Data360 Analyze 3.16.1 hotfix release
Fixed upgrade issues
Upgrade issues that were previously encountered when upgrading from versions 3.12.4 and 3.16.0 have been resolved in version 3.16.1.
Proxy support for ADLS nodes
Added the ability to specify and use a proxy on the ADLS nodes. This enhancement allows users to configure proxy settings, including Proxy URL, Proxy Username, and Proxy Password, for all ADLS nodes (List, Get, Delete, Put). This ensures seamless connectivity even in environments requiring proxy authentication.
Execution sandboxing updates
Execution sandboxing has been enhanced to prevent conflicts between scheduled executions and container cleanup. Newly created containers are no longer considered for "unmanaged" cleanup, and if a container is cleaned up during execution, the system will recreate it automatically. This ensures smoother execution workflows.
Option to disable scheduler during installation
A new checkbox has been added to the installer, allowing you to disable the scheduler on initial startup. This is particularly useful when restoring from a backup containing schedules that should not run immediately, such as in a high-availability (HA) environment.
Support for /etc/hosts configuration in sandbox containers
You can now add a boolean property
ls.brain.server.docker.containersInheritHosts (default value is
false) to the cust.prop file to configure execution sandboxing
containers to "inherit" the entries in the hosts file
(/etc/hosts) on Linux.
ls.brain.server.docker.extraContainerHosts to the
cust.prop file. It is an array of
<hostName>:<IP> entries. For example,
ls.brain.server.docker.extraContainerHosts=("bar.example.com:12.113.123.60"
"foo.bar.com:10.192.13.58").ls.brain.server.docker.extraContainerHosts will set extra
hosts on the container but will not have any effect on
Windows.Error messaging improvements
Improved error messaging for execution sandboxing on Windows. If target locations that are not under C:/ are used without proper mapping in the repositoryTargetMappings.json file, the system now provides clear error messages.
Performance improvements
Significantly improved the performance of directory move operations, particularly during ACL (Access Control List) validation.
Third party library updates
A number of third party libraries have been updated to take advantage of any security and feature updates, including:
- Java upgraded to version 17.0.13.11.
- PostgreSQL upgraded to version 16.6.
- Tomcat upgraded to version 9.0.98.
Usability changes
- The Get Metadata node inside the X-Ref Metadata node uses the latest Get Metadata node instead of Get Metadata (Deprecated).
Corrected issues
| Issue Summary | Issue Number |
|---|---|
| Fixed an issue where the Tabular XML File node failed to process files with field names containing special characters. The Tabular XML File node now runs successfully with a tabular XML file chosen from the file picker. | LAE-35480 |
| Fixed an issue where legacy connection filters could not be updated, and a console error was displayed when opening the dialog. | LAE-35473 |
| Fixed an issue where node log exports failed to include BRD files for input/output data and metadata. | LAE-35443 |
Fixed an issue in the "Do While" and
"Do While Conditional" nodes where the
accumulator BRD files were not being properly cleared upon
successful loop termination when the
"AccumulateLoopOutput" property was set to
True. This ensures proper cleanup of resources after loop
execution. |
LAE-35423 |
| Fixed an issue where the font size of an edited canvas text box did not scale with the canvas zoom level. | LAE-35371 |
| Fixed an issue where schedules could start executing before the system was fully initialized, particularly during the first startup after an upgrade. This ensures that scheduled tasks only begin after the scheduled task service has been properly booted. | LAE-35315 |
| Fixed an issue where backups could not be saved on systems with multi-user configuration due to incorrect permissions on the temp directory. | LAE-35264 |
| Ensured that execution containers run with the same timezone as the host environment when sandboxing is enabled. | LAE-35175 |
| Fixed an issue where the Execute Data Flow node did not work on Linux when execution sandboxing was enabled. | LAE-35093 |
| Fixed an issue where the Data Profiler node would sometimes report a NullPointerException when encountering certain types of data with very large numbers. | LAE-35085 |
| Fixed an issue with multi-item selection on the directory page main panel where, after deleting an item, the middle item was not selected. | LAE-35094 |
| Added checks to ensure that when moving data-collections or directories containing data-collections, the source collection is mounted, and the move will only be initiated if the file system locations for the source and targets are valid. | LAE-35038 |
Fixed an issue in the Modify Fields node
where the tool tip for the
NumericConversionErrorBehavior property
incorrectly displayed "Log" instead of
"Ignore." The tool tip now correctly
displays "Ignore" for the respective
option. |
LAE-27970 |
Fixed an issue in the Send Email node
where field names surrounded by apostrophes were not recognized when
used in the MessageBody property or other
properties with a "(from Field)" source option. You should be able
to configure the property source type as
"Field" and use the input data field. |
LAE-25390 |
| Fixed an issue where users upgrading from 3.12.4 to 3.16.0 were unable to edit the default temporary data location in Designer Settings. Additionally, users with only the Scheduler role can now view their temporary run data in My Documents. | LAE-35261 |
| Fixed an issue where the upgrade to 3.16.0 would fail if the system had users with their Home Directory pointing to a location in //Public Documents or to a location that no longer existed. The migration process now correctly accounts for changes in User Preferences, ensuring the upgrade succeeds. | LAE-35243 |
| Fixed an issue where the admin user could not manage mount points after upgrading from 3.12.4 to 3.16.0. Administrator user can now manage mount points after an upgrade. | LAE-35472 |
| Fixed an issue where warnings and info messages were incorrectly logged and displayed in the error panel when executing nodes with unmounted data collections in the system. Unmounted data collections are now correctly handled without generating unnecessary warnings, reducing confusion for users. | LAE-35478 |
| Fixed an issue where executing nodes in certain data flows containing loops would result in the execution hanging. In these cases, the execution could not be stopped. The Run command now correctly handles these scenarios, ensuring proper execution and termination. | LAE-35589 |