Zoomdata 5.1 Release Notes

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

Email salesteam@logianalytics.com to purchase Composer.

License Changes

When a Zoomdata trial license expires, only supervisors can log in (so they can update the license). Regular users will see a message stating that the license has expired.

Connector Changes

The following connector changes were made in this release:

  • Pushdown join support is now provided for data sources created using the Amazon Redshift, MS SQL Server, MySQL, Oracle, PostgreSQL, SparkSQL, Teradata, and Vertica data connectors. For more information, see Optimizing Joins.

  • Derived fields are now supported by the Vertica data connector. See Managing the Vertica Connector.

  • Composite aggregations are now implemented by Elasticsearch 7 connectors. This support optimizes aggregations of Elasticsearch 7 data, except for queries with:

    • histograms
    • time groups with WEEK granularity
    • multiple groups when group fields belong to different nested contexts.

    This support introduces a new Elasticsearch 7 configuration property elasticsearch.query.composite-agg.max-fetch-size in the Elasticsearch 7 configuration file (edc-elasticsearch-7.0.properties). Use this property to specify the maximum number of buckets to return for each query within a composite aggregation. Valid values must be greater than zero; the default value is 10000. This property corresponds to the Elasticsearch setting search.max_buckets, that also has a default value of 10000. If you elect to increase the value of the elasticsearch.query.composite-agg.max-fetch-size property, be sure to correspondingly increase the value of the Elasticsearch search.max_buckets setting.

    Note that there are no changes in Elasticsearch 6 connector behavior. Elasticsearch 6 connectors do not support composite aggregations.

    See Managing the Elasticsearch Connector.

Connection Changes

Variables can now be inserted for any connection parameter in a connection definition. The variables are passed to the connection string via custom attributes specified in the user definition or dynamically in the custom attributes specified in the SAML or LDAP configurations for your Zoomdata installation. You can insert variables for connection parameters using the following syntax:

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

See Inserting Variables for Connection Parameters.

Query Engine Changes

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

  • Data Sharpening has been reintroduced in this release. However, it is not enabled by default. You must change the sharpening.enabled property setting in the query-engine.properties file to true to enable Data Sharpening. See Managing the Composer Query Engine and Use Data Sharpening in Composer v5.

  • Support for several edge cases have been implemented for the query engine. In previous versions, these edge cases were not supported.

    • Complex queries containing aggregate filters are now supported in pivot tables with grouped multivalued fields.
    • Grouped multivalued time fields are now supported.

Materialized Views Support

This release provides support for materialized views using the REST API endpoint /composer/api/materialized-views, as shown in the table below.

Materialized views cache the results of a query and can speed up query processing, especially when replicating a query with heavily aggregated data. Once the query results are cached, materialized views must be manually updated and the manual query updates make take as long to perform as the original query.

Materialized view data is stored internally in either query engine memory or in dedicated external data connector storage. When it is initially loaded, it is stored in query engine memory and no target source ID (targetSourceId) or field mappings (targetFieldMappings) are provided. However, when the materialized view is recalled, its data is stored in external data connector storage and both the targetSourceId and targetFieldMappings are provided. You can use the targetSourceId in some of the following cURL commands for the /composer/api/materialized-views endpoint.

cURL Command Description
GET /api/materialized-views Returns a list of all materialized view mappings.
POST /api/materialized-views Creates a new materialized view mapping.
PUT /api/materialized-views/{ID} Updates a specific materialized view mapping.
PATCH /api/materialized-views/{ID} Patches (partially updates) a specific materialized view mapping.
DELETE /api/materialized-views/{ID} Deletes a specific materialized view mapping.

For complete information about Zoomdata's API, see Composer v5 REST API Overview.

User Interface Changes

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

  • The About dialog location and look changed in this release. It is no longer used to switch accounts (if your Zoomdata user name has access to more than one account). See About Dialog.

  • The Home page icons in the navigation bar of the user interface have changed in this release. Only a hamburger icon () is now available which provides a menu from which you can select various options. The options available in previous versions using the other home page icons have been moved to the menu. This change occurred for the regular user interface as well as the supervisor user interface. See The Composer UI Menu and The Composer Supervisor Menu.

  • For consistency and an improved look and feel, the styling of the Customize UI screen changed in this release. See Customizing the Composer User Interface.

What's Fixed?

The following problems were fixed in this release:

  • Zoomdata back-end dependencies and libraries have been upgraded.

  • Authorization problems (401 errors) when sharing a visual using an IFrame have been resolved.