Zoomdata 5.2 Release Notes

The following enhancements and updates were made to Zoomdata in version 5.2. See the following topics:

Email salesteam@logianalytics.com to purchase Composer.

Connector Changes

The following connector changes were made in this release:

Query Engine Changes

The following changes were made to the query engine in this release:

  • Improved support for multivalued fields used as metrics when a query cannot be fully pushed down and handled by the query engine.

  • Field metadata is now stored in the query engine first-level cache instead of being stored in the Zoomdata metadata store. All requests for metadata (minimum or maximum values for numeric and time fields or distinct values for attributes) are now initially run through the query engine's first-level cache. Finally, the Zoomdata scheduler now refreshes the query engine's first-level cache, which stores the data in the Zoomdata query engine data base (zoomdata-qe) so the data is available if the query engine microservice is restarted.

    In general, this new processing improves query response time. However, after you upgrade to this version, your query requests might be slightly delayed while the query engine directly queries the data source to obtain the result set and populate the cache. Likewise, if you clear the cache, your requests might be slightly delayed while the query engine obtains the result set from the data source and populates the cache.

    This use of the query engine cache for data queries can be controlled using the following new Zoomdata properties in the zoomdata.properties file:

    Property Description
    zoomdata.source.refresh.metadata.cache.timeout.minutes Sets the default time-to-live for cache values, in minutes. The default is one week (10,080 minutes).
    zoomdata.source.refresh.values.maxDistinctValues Sets the number of queried distinct values that can be stored in cache. The default is 100000.

    Finally, cached values are affected by row security filters or connection attributes in your Zoomdata environment that customize your data requests by user. The query engine uses the requested forced filter or connection attribute to produce the result set and stores the filter or connection attribute specification as part of the cache key, so two users with different forced filters or connections cannot see the other user's metadata cache entries.

Authorization Updates

  • Variables can now be inserted for any forced filters specified in a group definition. The variables are passed to the forced filters via custom attributes specified in user definitions or dynamically in the custom attributes specified in the SAML or LDAP configurations for your Zoomdata installation. You can insert variables for forced filter values using the following syntax:

    ${User.<custom-attribute-name>}

    In version 5.9.1, this functionality was moved and is not performed in row security filters. See Inserting Variables for Row Security Restriction Filters.

  • Group permissions for data sources now work as follows:

    • Users in groups with read access to a data source can no longer select the data source on the Data Sources page or alter the data source in any way.
    • Users in groups with edit access to a data source can no longer delete the data source on the Data Sources page.
    • Users in groups with delete-only access to a data source can no longer edit the data source on the Data Sources page. They cannot review or edit the data source configuration.

    For more information, see Restricting Data Source Configurations in a Group.

User Interface Changes

The following changes were made to the user interface in this release:

  • The color selections and default settings for KPI charts have been enhanced and the embedded color settings have been removed. The Color option is now available on KPI chart menus and allows you to access the Color sidebar to dynamically change the colors for a chart. The Color sidebar is customized for KPI charts. You can use it to dynamically specify the number of colors shown on a chart, the chart color metric, whether or not the chart legend appears, how colors are used on the chart (gradient or distinct colors), and threshold color conditions for the KPI chart.

    In addition, the default data source configuration settings for KPI charts have been enhanced. You can now specify the default color metric, the number of colors, whether or not the legend appears, the legend type (color palette or color range), and the default color palette or colors for a color range.

    See KPI Charts.

  • The color selection and management on the Color sidebar for many visuals was enhanced in this release. New color options are now available for many visuals.

    • You can now specify colors by name (for example, "cornflowerblue") or using RGB color coding (for example, rgb(255,0,0)). See Specifying Colors.
    • Histograms and line & bar trend charts now have color options. They did not before.
    • For visuals that display grouped data (for example, bar, pie, donut charts), you can manually change colors based on a group value. In addition, changes to the group colors are stored with the visual type. If you change a visual's type (for example, from bar chart to pie chart) and then later change it back to the original visual type, the group colors specified on the original visual are restored.
    • For metric-based visuals, you can use thresholds to set colors conditionally. You can manually set the thresholds or have Zoomdata automatically set them.

    For details, read the descriptions for each visual type. See Composer v5 Visual Metrics and Attributes Reference.

What's Fixed?

The following problems were fixed in this release:

  • The Elasticsearch 7 connector can now read indices from an Elasticsearch 7 instance hosted by Amazon Web Services (AWS).

  • The default documentation link shown on the Customize UI page of the supervisor UI now links to the Zoomdata LTS Active documentation on Logi DevNet.

  • Zoomdata back-end dependencies and libraries have been upgraded. An update of the Bouncy Castle version was made in third-party JAR files.