Apr 15, 2020

Announcing Imply 3.3

We are excited to announce the general availability of Imply 3.3 which greatly expands the expressivity of SQL by adding the ability to do JOINs and interact with lookups in novel ways.

This release includes over 200 new features, performance enhancements, bug fixes, and major documentation improvements.

JOINs in Druid SQL

We are thrilled to release Druid’s most requested query side feature: JOINs. Druid supports INNER, LEFT, and CROSS joins for now. It is now possible to express Druid’s lookups as a JOIN.

Lookups accessible in SQL

It is now also possible to query lookups directly through SQL enabling you to easily introspect and filter them.

Alerts in Imply Clarity

Alerts will also be made available in Imply Clarity, allowing you to set up alerting for the health of your Druid cluster. These alerts could proactively notify you via email or a webhook integration (such as PagerDuty) about any issues in your cluster according to your own SLAs and limits.

Role-based-access-control (RBAC) from Pivot to Druid

Pivot roles can now be connected to Druid users allowing you to have end-to-end access control between Pivot and in Druid. In particular it allows you to create Pivot users that can create data cubes in Pivot but are limited to a selection of datasources in Druid.

Finer grained alert and scheduled report access controls

This release gives you more tools around restricting exactly what data permissions are used to pull the Alerts and Scheduled reports. Specifically every Alert and Report now belongs to a single user “owner”, the “Owner” of the alert is the user whose permissions and data access will be used to query the data. This makes it simple to verify that every alert and scheduled report is run within its possible permission.

Related Posts