Zoomdata Version

Zoomdata Version 4 Release Summary

This is a summary of the changes made in version 4 of Zoomdata. It is provided so you can quickly identify new and changed Zoomdata features before upgrading from an earlier Zoomdata version. Be sure to read Installation and Upgrade Changes before you upgrade.

In addition to resolving problems and applying security fixes, Zoomdata version 4 introduced changes in the following areas. Select the area title for more detailed information.

Area New or Changed Feature Summary
Release Model Changes Zoomdata 4.9 is now the new LTS Active Support release. Version 3.7 is now the new LTS Passive Support release. Version 2.6 is no longer supported.
Licensing Changes An upgrade to Zoomdata 4 requires a new license. Your old license will no longer work with this release.
Installation and Upgrade Changes A new script utility is provided to assist with installations and upgrades of Zoomdata.
Because the use of the Zoomdata Scheduler microservice has been deprecated in this release, migration steps must be performed to upgrade to Zoomdata version 4.
The Zoomdata upload microservice is deprecated. Upload microservice properties are now renamed and can be configured in the zoomdata.properties file. These property changes should not affect normal Zoomdata instances after they are upgraded. If you have altered any of values of the properties listed above, those values are automatically migrated to the new properties during the upgrade process.
The Zoomdata Streamwriter microservice was renamed the Data Writer microservice. Its property file and properties have also changed.
The use of RabbitMQ has been deprecated. RabbitMQ is no longer a dependency and can be uninstalled from existing installations after you upgrade.
During an upgrade, automatic authorization conversions are performed for any users who had been assigned the deprecated Groups Only, User, and Admin roles.
Administration and Architectural Enhancements Load balancing was introduced for all connectors and for the query engine. Special configuration steps must be performed if you want to use a Zoomdata version 4 connector with an earlier version of Zoomdata or use a Zoomdata version 3.1 (or earlier) connector with Zoomdata 4 (or later). Zoomdata 3.2 to 3.7 connectors are fully compatible with Zoomdata 4.
Support for high availability of your Zoomdata environment is provided in this release. In a high availability Zoomdata environment, you can deploy multiple instances of Zoomdata to ensure that at least one instance of its microservices operate continuously. Microservice load balancing and failover occur automatically across the Zoomdata nodes. In addition, you can monitor all microservices and run diagnostic traces for them using the Service Monitor in conjunction with the Tracing microservice.
A new config-server-upload.jar utility is provided that can be used to migrate the microservice properties from your standalone Zoomdata servers to the Zoomdata configuration data in the PostgreSQL data store, where the configuration microservice can maintain them.
The zEngine used since version 3.6 to support fused data sources is now used for all query requests. It replaces the legacy query engine. Data sharpening is not currently supported by zEngine. In addition, several major changes in calculating the previous period (using the PreviousPeriod function) take effect with zEngine.
The query engine now supports graceful shutdown.

Service Monitor changes include:

  • The application properties of Zoomdata's dependent microservices can now be managed using the Zoomdata Service Monitor. This provides a centralized location where Zoomdata configuration properties can be maintained.
  • When you click on the URL for an instance of many microservices listed on the Service Monitor's Applications View page, a page of metrics and other information now appears for that instance of the microservice.

Microservices were added, renamed, and deprecated in this release:

  • The Streamwriter microservice was optimized and renamed the Data Writer microservice.
  • The Scheduler and upload microservices were deprecated. Their properties and functions are merged into the Zoomdata and Data Writer microservices.
  • A configuration microservice was added.
Authorization Enhancements Roles are no longer used to authorize the use of Zoomdata data sources and other features. The concept of roles has been removed from the product and the Admin, User, and Groups Only roles have been removed.

A new Zoomdata-supplied superaccount is provided. It is a dedicated and permanent account that cannot be deleted. Its sole purpose is for the maintenance of other Zoomdata accounts and other supervisory Zoomdata functions. The supplied supervisor user can only be assigned to the superaccount. Other users can also be assigned to the superaccount.

The following new group privileges were added: Can Administer Dashboards, Can Administer Groups, Can Administer Users, Can Invoke Actions, Can Manage Action Templates, and Can Manage Connections.
More than one supervisor user can now be defined. Users assigned to the superaccount have full access to the Zoomdata supervisor UI and its supervisory functions.
The supplied supervisor user can now be enabled and disabled.

Supervisors can no longer:

  • Manage data source, dashboards, and charts for an account.
  • Maintain group definitions or assign users to group definitions. The only exception is when they create an account for the first time, when they assign or create an initial administrative user for the account.
  • Change or reset passwords (except their own).
  • Maintain user definitions in the account management section of the supervisor UI. They can only create and remove users in the Manage Users section of the supervisor UI.
The zoomdata scheduler user has been removed and is no longer used for scheduled data source refreshes. Instead, the controls for scheduled data source refreshes are now set in the connection definitions used by Zoomdata to connect to your data stores.
Connector Changes Load balancing was introduced for all connectors. (See Administration and Architectural Changes above.)
A new TIBCO Data Virtualization (TDV) connector supports TDV versions 8.0 - 8.1.
A new Couchbase connector supports (with some limitations) Couchbase version 6.0.1.

Support changes were made for many connectors in the following areas: deprecated versions, new versions, Kerberos and SSL support, user delegation, pushdown joins, and SQL views. See Connector Changes for a full list of these updates.

Using a new property, you can now limit the list of available collections in a Teradata data store to collections from a specific schema specified in the Teradata JDBC URL. Work with your Teradata database administrator before you use this property.
Fusion Enhancements Pushdown joins for Fusion data sources are now supported by Zoomdata's Apache Drill, MemSQL, and Snowflake data connectors.
Data from Fusion data sources can now be used in box plot charts, histograms, and raw data tables. Zoomdata recommends that you initially use a subset of fields from Fusion data sources on raw data tables to limit the load on Zoomdata's query engine and improve its performance.
The aggregate functions TableCOUNTD and WindowCOUNTD are now supported in fused data sources.
Support for last value data was introduced for Fusion data sources.
Even time interval support for dashboards using Fusion data sources was introduced.
Application Integration Action Support Support for Zoomdataactions is introduced. Actions allow you to integrate your Zoomdata chart data into your applications. After your system and data administrators have defined your application integration with Zoomdata and granted proper permissions to use Zoomdata actions, you can invoke an action while working with a chart on your dashboard. The invoked action creates a query definition based on the filters applied to the chart and on the data and limit specifications in the application integration definition. It then sends the query definition to your application. Your application can use the Zoomdata API to run the query and display or use the data that it collects.
User Interface (UI) Changes Changes were made to how data store connections are defined in the UI.
If you are logged into Zoomdata as a user who can maintain data source configurations but cannot maintain connection definitions, the following data source and dashboard import behavior has changed.
For consistency and an improved look and feel, the styling of the following UI screens and dialogs changed.
If an action template is enabled for a chart's data source, the radial menu for the chart now includes an option to invoke an action and the chart menu now includes a new Actions menu option.
Time bar functionality has changed. The time range zooming that occurred automatically in past releases when you adjusted the sliders on the time bar no longer occurs automatically. The default range for a derived time field is now always the current year. Finally, while you are working on a dashboard or chart, the time range and playback configuration you have used for different time fields are retained.
The behavior of the Home page button () has changed so it now remembers the filter requested for the Home page when you return to it after looking at a dashboard.
A number of changes were made to the Derived Field Editor and the Custom Metric Editor. These include syntax highlighting, hidden field visibility (Derived Field Editor only), editor left-hand panel changes, autocomplete functionality, and a gutter indicator of syntax errors.

The following charts now render using the latest version of the ECharts library: bar charts, box plots, donut charts, floating bubble charts, heat maps, line charts, packed bubble charts, pie charts, scatter plots, tree maps, and word cloud charts.

Specific chart changes were made to heat maps, map marker charts, pivot tables, and raw data tables. See User Interface (UI) Changes for details.
Data Manipulation Enhancements Second and millisecond support has been added for date and time data. You can now request that date and time data be processed using second or millisecond granularities.
Fields with a MONEY field type are now automatically converted to the NUMBER field type. The MONEY field type is no longer supported.
You can now use derived fields in WHERE clauses in custom metrics.
Hidden source and derived fields can now be used in other derived fields.
A new time_diff row-level function can now be used in row-level expressions for derived fields. This row-level function allows you to obtain the difference between the values of two time fields in the date/time unit you require.
REST API Changes All Version 1 public APIs have been removed. Version 2 of the REST API should be used going forward.
The internal APIs starting with paths such as /service/ are removed in favor of paths starting with /api/.
It is now mandatory that you specify the application/vnd.zoomdata.v2+json version of the API in requests. For requests that retrieve a payload, such as HTTP GET operations, this should be in the Accept header. For requests submitting data (for example PUT, POST, or PATCH), this is typically in the Content-Type header.
You can now use the /api/sources/{id}/key endpoint as an alternative to the api/sources/key?source=[list of source IDs] API endpoint.
A new API endpoint, api/action has been added to Zoomdata. Use this endpoint to run the Zoomdata query defined by an action.
A new, optional, ?format= parameter has been added to the /zoomdata/api/export/chartdata/content endpoint. Valid values are csv or json. Use this parameter to request that the data from the query be returned in JSON format or exported as a CSV file. The default value is csv.
The REST endpoints /zoomdata/system/info and /zoomdata/actuator/metrics-grouped have been removed. Use the /zoomdata/actuator/metrics endpoint instead.
Features Deprecated in Version 4 Zoomdata licenses prior to version 4.9. Contact Zoomdata Technical Support to obtain a new license.
The installation script used for versions earlier than version 4.
Manually upgrading Zoomdata 4.1 or later no longer provides the Java Runtime Environment (JRE) needed for Zoomdata to start.
The use of RabbitMQ. RabbitMQ is no longer a dependency and can be uninstalled from existing installations after you upgrade.
The Zoomdata upload microservice.
The Zoomdata Scheduler microservice.
The MONEY field type is no longer supported. Fields with this field type are automatically converted to NUMBER.
Connector support for different data store versions. See Features Deprecated in Version 4 for a list.
The REST endpoints /zoomdata/system/info and /zoomdata/actuator/metrics-grouped
The zoomdata scheduler user has been removed and is no longer used for scheduled data source refreshes. Instead, the controls for scheduled data source refreshes are now set in the connection definitions used by Zoomdata to connect to your data stores.

Roles are no longer used to authorize the use of Zoomdata data sources and other features. The concept of roles has been removed from the product and the Admin, User, and Groups Only roles have been removed.

Supervisors can no longer:

  • Manage data source, dashboards, and charts for an account.
  • Maintain group definitions or assign users to group definitions. The only exception is when they create an account for the first time, when they assign or create an initial administrative user for the account.
  • Change or reset passwords (except their own).
  • Maintain user definitions in the account management section of the supervisor UI. They can only create and remove users in the Manage Users section of the supervisor UI.

Click https://www.zoomdata.com/contact-us/ to purchase Zoomdata.

Was this topic helpful?