The following release notes provide information on features, improvements, and bug fixes up to Imply STS release 2022.01. Read these release notes carefully before upgrading to 2022.01.
Before your upgrade to 2022.01, read the Upgrade and downgrade notes.
If you are upgrading by more than one version, read the intermediate release notes too.
On October 12, 2021, all 3.x versions of Imply entered end-of-support status. See Lifecycle Policy.
See Previous versions for information on older releases.
New to Imply? Get started with an Imply Cloud Free Trial or start a self-hosted trial at Get started with Imply!
With Imply Cloud, the Imply team manages your clusters in AWS, while you control the infrastructure and own the data. With self-hosted Imply, you can run Imply on *NIX systems in your own environment or cloud provider.
Changes in 2022.01
The latest release version of Imply bundles version 2022.01.0-iap of the Imply distribution of Apache Druid. Before your upgrade to 2022.01, read the Upgrade and downgrade notes.
Support for ZooKeeper 3.4 is deprecated
Support for ZooKeeper 3.4 is deprecated and will be removed in the 2022.01-LTS release. Imply will be migrating to new ZooKeeper versions over upcoming releases. If you are currently running ZooKeeper 3.4, please consider upgrading your infrastructure.
- Imply Cloud: Starting with the 2021.10 release, Cloud Manager will run ZooKeeper 3.5. Customers who upgrade to the 2021.10 release (or later) will be upgraded to ZooKeeper 3.5 automatically.
- Enhanced Imply Private on GKE and Imply Private on Kubernetes: Customers who use their own ZooKeeper 3.4 (or earlier) must update their version of ZooKeeper to 3.5 (or later) before upgrading to Imply 2022.01-LTS.
- Imply Private on Linux and Unmanaged Imply: Customers must update their version of ZooKeeper to 3.5 (or later) before upgrading to Imply 2022.01-LTS.
Pivot 2.0 now GA
Pivot 2.0 is now GA. This release introduces numerous changes to enhance Pivot 2.0 and bring it closer to feature parity with Pivot Classic. The changes affect data cubes and dashboards, and include, among others, the following changes:
- Additional visualization types for Pivot 2.0 data cubes, including spot matrix, geo shade, and bubble visualizations.
- Support for setting a default data cube view.
- Support for new and improved filtering by measure.
- Support for dimension URLs.
- Ability to customize the color palette by cluster.
- Support for brush and link filtering for dashboards (that is, the ability to click on visualizations and have that filter applied to all other views that share the filtered dimension).
The following describes the impact for new deployments compared to upgraded deployments:
- For new installations, Pivot 2.0 and Pivot SQL are now on by default. An administrator can still disable them using a feature flag. Disabling them results in new data cubes using Pivot Classic by default.
- For existing installations that have been upgraded from a previous version, there are no changes to existing data cubes or dashboards. Administrators can enable Pivot 2.0 and Pivot SQL as feature flags. If enabled, users have the ability to choose whether to use Pivot 2.0 or Pivot Classic when creating data cubes.
Pivot SQL now GA
Pivot SQL is now generally available (GA). This release brings in additional capabilities to bring Pivot SQL to GA status:
- Support for subset filters with Pivot SQL expressions
- Support for filter tokens with Pivot SQL expressions
- Deprecation of support for customAggregations in Plywood
Pivot SQL is on by default for new deployments. For the impact on upgraded clusters, see Pivot 2.0 now GA.
Pivot Classic and Plywood data cubes deprecated
Pivot Classic and Plywood data cubes are now deprecated. Support will be terminated in a future release.
Async downloading GA in Imply Private
Asynchronous downloading is now GA for Imply Private deployments. It remains in beta status in other deployment types.
- Prevent Total from showing up on the axis for vertical bar chart (id: 15138)
- Fix padding for display text on regex filters (id: 15085)
- Make empty visualizations look consistent (id: 15081)
- Fix dropdown label to say "measure" instead of "Without" (id: 15080)
- Add support to enable check/uncheck upon clicking on text for filter menu (id: 15079)
- Apply style adjustments in filter menus (id: 14803)
- Adjust min and max heights selection pane for dimensions and measures (id: 14734)
- Fix legend on dashboard tile overlaps tile drop shadow and rounded corner (id: 14663)
- Fix typo when attempting to show a geo visualization with no geo dimensions (id: 14662)
- Fix clicking visualization legend results in a crash when viewing tile in data cube (id: 14611)
- Fix large downloads failing in async downloads (id: 14588)
- Fix error when dragging a dimension on the show bar while displaying the "Totals" visualization (id: 14480)
- Fix new measure modal issue affecting aggregation (id: 14435)
- Add code to handle errors when async downloads are disabled in Druid (id: 13378)
- Remove "slow" label from download options gated by
DownloadLargeDatapermission when using async downloads (id: 13136)
- Fix "Add total row to file" doesn't work for measures other than Count (id: 12985)
- Add support for being able to view the status of an async download anywhere in Pivot (id: 12764)
- Change verbose-gated log messages to use the "debug" method (id: 12657)
- Surface OIDC role name mismatch warning messages only in verbose mode (id: 11771)
- Productionize support for visualization auto-selection and suggestions (id: 9901)
- Add icons to the header in resource views; indicate the color theme (id: 9479)
- Fix grid view when filter limit is set high enough to return no results (id: 8915)
- Fix an issue with incorrect column types during ingestion (id: 15344)
- Fix array type strategy write size tracking (id: 15315)
EARLIEST/LATESTfunction signatures less ambiguous (id: 15259)
- Fix PostAggregator interface to make it backward compatible (id: 15199)
- Update log4j2 to
- Fix delegated smoosh writer and some new facilities for segment writeout medium (id: 15132)
- Improve configurable Clarity emitter HTTP client worker pool size (id: 14626)
- Add support for histogram filtering in sessionization (id: 13552)
- Add support for pruning segments on all dimensions in the multi-dim partitioning scheme (id: 12914)
- Fix an issue with DataSketches not recognizing the same IPv6 address in different representations (id: 12901)
- Fix an issue with overlapping segment intervals causing automatic compaction to fail (id: 12671)
- Distinguish between query metrics for async queries and sync queries (id: 10949)
- Add a guardrail that prevents creating too many time chunks by mistake during batch ingestion (id: 10485)
- Fix an issue with grouping keys unexpectedly reduced in SQL planner (id: 7780)
- Fix an issue where SQL queries with floor(
<integer>) return wrong results (id: 6698)
- Security fixes
- Fix an issue with
helm upgradecommand failing to upgrade a cluster in a Kubernetes environment. (id: 15236)
Upgrade and downgrade notes
Before you upgrade or downgrade, review the following items to avoid potential version-related issues.
LATEST_BY functions replace
EARLIEST/LATEST with custom time parameter
Applies to 2022.01 and later.
EARLIEST/LATEST functions with a custom time column has been removed from the Imply distribution of Apache Druid. This removes the cognitive complexity with the coexistence of the
maxBytesPerString parameter as well as
timeColumn. You can use the following new functions to set a custom time column:
EARLIEST_BY/LATEST_BY. For more information, see Aggregation functions.
Enable async download after Imply upgrade
Applies to versions 2022.01 and later.
If you use an Imply version that's older than 2022.01 and upgrade to version 2022.01 or later, you cannot enable async download during the upgrade. Enable the async download extension in a separate step after your cluster has finished updating.