We’re excited to announce the release of Imply 3.4 with Apache Druid 0.19 at its core. This release includes new capabilities in Druid and Pivot that bring the stack closer to standard BI capabilities along with dozens of bug fixes and enhancements.
If you’re an Imply Cloud customer or if you run Imply on Kubernetes with the self-hosted Manager, you can now upgrade to the latest version through the management UI. This release is also available for download on our getting started page.
In Imply 3.4, we’re introducing an early preview of a new way to define data cubes in Pivot, allowing users to define custom measures and dimensions using SQL expressions instead of Plywood. We’re excited about the possibilities this feature holds for democratizing data analysis with Pivot given the broad reach of SQL, and for making it easier for people used to working with BI tools to work with Pivot. If you’d like to take it for a test drive, it can be enabled via the “Experimental features” toggle in the Advanced Settings UI.
Along the same lines, we are continuing to work on improving SQL JOIN capabilities within Druid. Imply 3.4 enables Druid SQL users to join against multi-column indexed dimension tables. This release adds numerous reliability and usability enhancements, including the ability to load indexed tables through ingestion specs, with Druid automatically handling broadcasting them to all nodes in the cluster. The screenshot shows a SELECT statement spanning multiple columns.
Additionally, we’re introducing a sneak peak at the ability to annotate time series views in Pivot, allowing users to easily correlate real-world events such as software releases or advertising campaigns against changes in metrics. Like Pivot SQL, this can be enabled via the “Experimental features” toggle in the Advanced Settings UI.
Pivot in Imply 3.4 also comes with over 30 bug fixes and product enhancements. Among other things, we’ve further expanded support for comparisons and filter by measure, which now work more reliably on a number of visualizations.
Along with over 200 new features, performance enhancements and bug fixes, Druid now has vectorization turned on by default for a large number of queries, providing a performance boost that can reach 5x on some queries.
Splunk Smartstore vs Lumi Loglake
Lumi Loglake lets Splunk teams query logs directly in object storage — AWS S3, Delta Lake, Apache Iceberg — using standard SPL, with results returned as native Splunk events that work with existing dashboards,...
Learn MoreSupercharging Schema-On-Read: Logs in Object Storage Don’t Need a Data Catalog
Machine data architectures are rapidly changing. As telemetry volumes continue to grow and as costs rise, organizations are increasingly moving logs and other machine data into object stores such as AWS S3....
Learn MoreImply Lumi Loglake vs Splunk Federated Search for S3
Teams are increasingly moving log data into AWS S3 to reduce costs and extend retention. Both Lumi Loglake and Splunk Federated Search to S3 help you query data in AWS S3 to lower costs, however the two technologies...
Learn More
Jad Naous