Version you are viewing: Zoomdata v4
Zoomdata Version 4.9
The following enhancements and updates were made to Zoomdata in version 4.9. See the following topics:
- Licensing Requirements
- Release Vehicle Changes
- Connector Changes
- High Availability Support
- Service Monitor Updates
- Chart Updates
- UI Changes
- Field Changes
- REST API Changes
- What's Fixed?
- What's Deprecated?
Click https://www.zoomdata.com/contact-us/ to purchase Zoomdata.
An upgrade to Zoomdata 4.9 requires a new license. Your old license will no longer work with this release. Please contact Zoomdata Technical Support to obtain one.
With this release, Zoomdata 4.9 becomes the new LTS Active Support release. Version 3.7 becomes the new LTS Passive Support release.
|Version 2.6 is no longer supported..|
For more information, see Zoomdata Release Vehicles.
Support for Apache Drill versions 1.11 through 1.13 are deprecated in this release. In addition, support for Apache Drill versions 1.14 through 1.16 are added. See Managing the Apache Drill Connector.
Support for MongoDB version 4.2 has been added in this release. We now support versions 3.4 - 4.2. See Managing the MongoDB Connector.
Support for PostgreSQL version 9.3 is deprecated in this release. We now support versions 9.4 - 11.1. See Managing the PostgreSQL Connector.
This release introduces support for high availability of your Zoomdata environment. In a high availability scenario you can minimize the downtime caused by:
- hardware or software failures due to excessive resource use or other events
- software upgrades or updates
In a high availability Zoomdata environment, you can deploy multiple instances of Zoomdata to ensure that at least one instance of its microservices operates continuously. A load balancer is required to distribute the network traffic across your user-facing Zoomdata nodes. Microservice load balancing and failover occur automatically within the Zoomdata nodes themselves. In addition, you can monitor all microservices and collect diagnostic trace information for them using the Service Monitor in conjunction with the Tracing microservice. For more information, see High Availability Environment Support and Configuring a High Availability Environment.
If you have the configuration microservice configured and running, you can maintain properties for microservices of a given type in a single location in the Service Monitor. For example, if you have two query engine microservices running in your high availability environment, you can change the properties for both microservices in a single location, ensuring that the query engine microservices operate in the same manner across the product nodes. 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 high availability PostgreSQL data store, where the configuration microservice can maintain them. For more information see Migrating Properties to the Configuration Server.
If you click on the URL for an instance of any of the following 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.
all data connector microservices
Data Writer microservice
query engine microservice
The following changes were made to charts in this release:
The line chart types were updated in this release and now render using the latest version of the ECharts library. This was done for all three line chart types: line & bar trend charts, line trend attribute value charts, and line trend multiple metric charts. See Line Charts.
Two new settings can be made for pivot tables produced by your data source data:
Setting Description Column Limit Specifies the maximum number of columns of data that can be returned for a pivot table. The default is 4000 columns. Cell Limit Specifies the maximum number of cells of data that can be returned for a pivot table. The default is 1,000,000 cells.
These two settings regulate the quantity of data returned in a pivot table and can reduce the risk of performance problems with your browser. When the data returned from a query exceeds one of these settings, an error message displays.
The following UI changes were made in this release:
Syntax highlighting has been added to the Derived Field Editor and the Custom Metric Editor to improve the readability of expressions and provide visual clues about the items being used and their validity.
The following parts of an expression are now highlighted in different colors or with different text treatments:
- function names, both row level and aggregate
- fields and metrics
- keywords such as CASE and IN
- example parameters
- date period constants such as
- values such as numbers and
- arithmetic operators such as
References to fields that do not exist in the data source or are otherwise not usable in an expression are interpreted as values and show up in black, alerting you to possible typos or other issues.
Hidden fields are now listed in the left-hand panel of the Derived Field Editor when it is accessed via the Fields tab of the data source configuration wizard. (When the editor is accessed in other ways, hidden fields are not listed). Hidden fields appear italicized in the list to differentiate them from visible fields.
As applicable, the Function Library, Row Level Function, and Attributes & Metrics sections now always appear in the left-hand panel, allowing you to more easily switch between these sections.
Attributes and metrics in the left-hand panel now include tooltips that provide information on the field ID in square brackets when it is different from the field label. In the Derived Field Editor, the tooltips provide the hidden status of the field, when applicable.
Function completions provide the type of function, the name of the function, the description of the function, and an example of how the function is used, including parameters.
Field completions are available by typing either the field ID or the field label. The field ID appears in square brackets next to the field label when the two are different. Field completions provide the type of the field, the field label and ID, expressions for derived fields, and information about whether the field is hidden (as applicable).
Metric completions provide the metric label and the expression that will be inserted into the editor when the metric is selected.
In addition to the alert notifying you of syntax errors in an expression, an indicator appears in the gutter area of the Derived Field Editor and the Custom Metric Editor. When you hover over the indicator, information about the syntax error, including line and column numbers, appears.
You can now invoke actions from the chart menu if an action template has been enabled for the chart's data source. A new Actions menu option has been added to the menu. See Using the Chart Menu and Invoking an Action.
This release introduces a new
time_diff row-level function that can be used in row-level expressions for derived fields. This new row-level function allows you to obtain the difference between the values of two time fields in the date/time unit you require. The syntax of the
time_diff row-level function is:
time_diff('<timepart>', <end_date_field>, <start_date_field>)
See Time Functions for more information.
The following changes were made to the REST API in this release:
A new, optional,
?format=parameter has been added to the
/zoomdata/api/export/chartdata/contentendpoint. Valid values are
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
The REST endpoints
/zoomdata/actuator/metrics-groupedhave been removed. Use the
For complete information about Zoomdata's API, refer to our developer API documentation.
The following problems have been fixed in this release.
The last data point now shows in a weekly view of an attribute value line chart.
Resolved a problem in which connectors failed to start when a broken
zipfile was in the root directory.
Resolved a problem in which horizontal scrolling in a pivot table failed when many totals were presented in the data.
Resolved a problem in which a pivot table did not scroll if its attributes extended wider than the screen (before aggregation).
Corrected the preview index of an Elasticsearch data source that was accessed using an HTTP connection.
Action API endpoints are now listed in the Zoomdata developer documentation.
createdByUserIDfield is now shown in an
Corrected a parsing exception that occurred when you used a custom metric (that was comprised of several attributes) in a chart and then grouped the chart by one of the attributes.
The following features are deprecated in this release.
Support for Apache Drill versions 1.11 through 1.13 are deprecated in this release.
Support for PostgreSQL version 9.3 is deprecated in this release.
The REST endpoints
/zoomdata/actuator/metrics-groupedare deprecated in this release.
To review a history of deprecated features, see Deprecated Zoomdata Features.