Data360 Analyze what's new - Data360_Analyze - Latest

Data360 Analyze Release Notes

Product type
Software
Portfolio
Verify
Product family
Data360
Product
Data360 Analyze
Version
Latest
Language
English
Product name
Data360 Analyze
Title
Data360 Analyze Release Notes
Copyright
2024
First publish date
2016
Last updated
2024-12-12
Published on
2024-12-12T14:19:08.338000

This topic provides release information for the latest release of Data360 Analyze.

The availability of the following new features, enhancements and corrected issues is dependent on the installed edition of the product and licensed features.

Latest release - 3.16.0
Note: Data flows built in 3.16.0 will not be backwards compatible with earlier versions.

Run multiple sets of nodes simultaneously

You can now run multiple sets of nodes simultaneously. This means that you can start running a set of nodes while other nodes are already running. Each time you do this, the nodes selected to run will be in a separate "execution". The number of concurrent executions that can be ongoing per user per data flow is controlled by this property: ls.lae.execution.concurrentExecutionsPerSession

This is a server side property that will affect all runs by all users. The default is 4.

Share run data

You can share run data with other users to work collaboratively by saving run states and temporary execution data in a shared folder in the Directory. This is possible even when execution sandboxing is enabled. If the temporary execution data is saved in a location that is accessible to all users in your team, then all users will be able to view the run data associated with the data flow, without needing to re-run the data flow themselves.

On the Designer page Run tab, you can specify where to store temporary run data and you can edit the temporary run data location for an existing run.

Note: For any existing schedules that were created and have run prior to this release, access to the historic run data will only be available to the user for which the schedule is run as. If you want other users to be able to access future run data, change the location of the temporary run data to a location accessible by all users concerned.

All users (except reviewer only users) can set their default temporary execution data location from the Directory on the Settings > Designer Settings page.

Data viewer enhancements

A number of usability enhancements have been made to the data viewer, including:

  • Sort multiple columns: A new Sort Multiple Columns option has been added to the tab menu, allowing you to edit the column sort order. You can hold down the Ctrl button and left click a column header. Each time you click, the column is added to the sort. The sort order is given by the number you see on the sort indicator.
  • Freeze rows and columns: You can freeze rows by right-clicking a data viewer cell and selecting Freeze Rows Top. This will freeze the currently selected row and all rows above it. Frozen rows remain in place as you scroll vertically. You can freeze individual columns by selecting the Freeze option from the column header menu. Frozen columns will remain in place when you scroll horizontally.
  • Search columns: A new Search Columns option has been added to the tab menu. Selecting this option opens a dialog that lists all columns in the data viewer. You can use the search bar to filter for a specific column. Choosing a column from the list will scroll the corresponding column into view in the data viewer.
  • Hide columns: A new Hide option has been added to the data viewer column menu, allowing you to hide the current column, or hide several selected columns at once. Hidden columns can be shown again using the column menu or the tab menu.
  • Search tabs: A new Search Tabs option has been added to the tab menu allowing you to filter tabs using the search field. Selecting a tab will select it in the data viewer.
  • Select node: A new Select Node option has been added to the tab menu. Selecting this option will select and center the node that the tab was opened from. If the node is at a different composite level, the current composite level will change to that of the node.
  • Open from canvas: You can now open the data viewer pop-out window directly from the canvas by holding down the Shift key when clicking on a pin.
  • Go to column: When the horizontal scroll bar is active, the tab menu lists the names of the data viewer columns. Choosing an option from the dropdown will scroll the corresponding column into view.
  • Filters and sorts: When filters and sorts are applied to an open data viewer, if the node is re-run and there are no changes to the output metadata then the data viewer stays open, the data is refreshed and the filters and sorts are re-applied.

Stop a running schedule

You can now stop a currently running schedule. This allows you to edit the schedule before re-planning. You can do this from the Schedules page, the Runs page or the details panel in the Directory when the schedule is selected.

SAML SSO group membership

When SAML SSO users login to Data360 Analyze, group membership can be configured to automatically update based on the information passed in via the SAML assertion.

On the Groups page in the Directory, you can filter the group list to show only:

  • Local groups
  • SSO managed groups
  • LDAP imported groups

On the Users page in the Directory, you can filter the user list to show only:

  • Local users
  • LDAP imported users

Default roles for imported users and groups can be set independently. Previously the default role was shared.

Performance improvements

The performance of the application has been improved, particularly when running data flows:

  • Reduced the time taken from a run being initialized to when the nodes start executing when the entire data flow is being run and there is no existing state (for example, for scheduled runs).
  • Reduced the amount of parameter evaluation that needs to occur on all Java nodes.
  • Improved the performance of the initial time for an ad hoc run to start node execution when running a subset of nodes in complex data flows where upstream nodes may need rerunning as a result of the call to run.

Breaking changes

  • Data flows built in 3.16.0 will not be backwards compatible with earlier versions.
  • RedHat Enterprise 7.X 64-bit is no longer supported.
  • Due to Java 17 incompatibilities in the Snowflake database driver, for the database nodes (JDBC Store, JDBC Query, JDBC Execute, Database Profiler and Database Metadata) if a DbType of Snowflake is specified and no DbUrl property is provided, the nodes will be automatically configured to communicate with the Snowflake database using the "JDBC_RESULT_QUERY_FORMAT" set to JSON. When forming connections to a Snowflake database using the shipped driver, if you do not specify a DbType or if the DbUrl is set explicitly, you will need to manually configure the node to use the JDBC_RESULT_QUERY_FORMAT option in the DbUrl or DbOptions property. Note that this is a breaking change if you have configured this node in Data360 Analyze prior to the 3.16.0 release. If you have existing nodes configured to connect to Snowflake using our shipped driver, where the DbUrl property has been set explicitly or if you have not set the DbType property, you must add the JDBC_RESULT_QUERY_FORMAT option to prevent the node from failing.

JDBC driver updates

  • Snowflake JDBC driver updated to version 3.20.0
  • Postgres JDBC driver updated to 42.7.4
  • Oracle JDBC driver updated to 23.5.0.24.07
  • Maria DB driver updated to 3.5.0
  • Resdshift JDBC driver updated to 2.1.0.30
  • Postgres updated to 16.4

Third party library updates

A number of third party libraries have been updated to take advantage of any security and feature updates, including:
  • Tomcat upgraded to 9.0.96
  • Jython upgraded to 2.7.4
  • Data360 Analyze components including the installer, Tomcat, the execution server, and nodes have been updated to run on Java 17 JVM.

Other changes

  • Execution sandboxing: When using a Docker l2bridge network with execution sandboxing, the trusted host configuration is setup by default for the l2bridge scenario where communication from the web application will appear to the containers to come over the host's IP instead of the gateway IP. Added configuration in the executionContainers enable script to be able to override this behavior.
  • Notification dialog: The notification dialog can now be dismissed by clicking outside of it.
  • Tabular XML File node: A new SubstituteInvalidCharacters property has been added to the Tabular XML File node. If this property is set to True, the node will substitute both characters that are reserved characters in the metadata (for example, newline, ':') and characters which are not in the Data360 Analyze server's character set into a valid alternative such that the field names in the metadata are valid.

Corrected issues

Issue summary

Issue number
Fixed an issue that prevented the Enable Scheduler button from working if schedules were deactivated with the ls.lae.schedules.schedulerInitiallyPaused=true property when starting the application. LAE-34898
Changed various type arguments used by the Cobol and Data Reader nodes to be "_Record" instead of "Record" so as to not conflict with the Java keyword. LAE-34810
Fixed an issue where the Database Metadata node was failing for Hive. LAE-34467
Fixed an issue where certain sequences of saving and running data flows would cause null pointer errors and incorrect display of data flows. LAE-34440
Fixed an issue where duplicate entries were created in the Split and Filter nodes when adding a new filter item. LAE-34379
Fixed an issue that caused the JSON Data node to fail when the JSON file key names were not parsed successfully. LAE-34341
Fixed an issue that prevented the CSV/Delimited Input, JSON Data, XML Data, Tabular XML File nodes from importing files with unsupported characters in the headers. LAE-34319
Fixed an issue where the Output CSV node reported an incoherent error message when a file already exists. LAE-34317
Fixed an issue that prevented the CSV/Delimited Input node from importing files with unsupported characters in the headers. LAE-34316
Fixed an issue to ensure that users who have access to data collections but have no access to some data directories within a data collection are still able to run data flows and have these permissions respected. LAE-34267
Fixed an issue that prevented the application from starting if a scheduled task had invalid data, for example if it specified a cron expression in the past. LAE-34205
Fixed an issue where the Output Raw node was trimming leading and trailing white space. LAE-34192
Fixed an issue that caused errors when running the ADLS List node when Data360 Analyze is configured for a multi-user install in a Linux environment. LAE-34191
Improved the error messaging when importing old unsupported LNA files. LAE-34175
Fixed an issue where deleting a property with a value did not immediately display as an unresolved property on the Configure tab. LAE-34154
Fixed an issue that caused a hidden run property "URL_Link_To_Run" to be visible on the Runs page. LAE-34134
Fixed an issue that could cause an upgrade to fail silently because the uninstall of the previous version did not notify that it had errors. LAE-34083
Fixed an issue where the canvas marquee select tool was unavailable when a data flow was opened in read-only mode. LAE-34071
Fixed an issue where immediate feedback was not provided when a file upload was started. LAE-33999
Fixed an issue where a data flow could get into a bad edit state if another version of the data flow was imported and edited at the same time. LAE-33895
Fixed an issue that could cause an upgrade to fail if a user had an invalid home directory. LAE-33866
Fixed an issue that could cause an upgrade of Data360 Analyze to fail if HTTPS had been enabled for Tomcat in the previous version. LAE-33789
Fixed an issue where the CSP header was missing on responses to UI asset requests. LAE-33695
Fixed an issue where vertical scroll bars appeared unnecessarily on text boxes. LAE-33138
Updated the default configuration on Docker containers created for execution sandboxing to ensure that no new privileges can be obtained by the container user. LAE-32111
Fixed an issue where any installation that had a historical version 3.8.5 and contained scheduled runs would fail when upgraded to 3.14.0. LAE-34980