Imply 2.2 adds new Pivot features that enhance filtering flexibility, especially for time filters, new percent of total measures, and tuning for approximate quantiles.Check out the screenshots below that show these new Pivot features in action.
You can now add filters directly from the filter bar.
This is particularly useful in interactive collections, where you can now add arbitrary filters.
We have upgraded the Pivot time filter menu to allow you to select a precise time.
You can now also select several time ranges.
You can now configure measures that are defined as a percentage of their next higher split (or of the global total).
This in effect transforms the measures on the client side.
It is now possible to fine-tune approximateHistogram based quantiles, allowing you to determine your trade-off between performance and accuracy.
Enter a 3rd parameter in the quantile formula of the form 'resolution=400,numBuckets=10,lowerLimit=0,upperLimit=1000' to pass those tuning parameters to the underlying aggregator.
To understand how to tune the approximateHistogram parameters check out the Druid documentation
Have you ever wondered what queries are being issued under the hood as you fly around your data? While it was been possible to run Pivot in verbose mode since the first release you can now inspect your queries directly from the UI.
The query view is a great way to understand how Pivot interacts with Druid in particular if you are utilizingcustom transformations or custom aggregations.
In addition to all of the above we also improved the consistency of some Pivot workflows as well as greatly reducing the number of queries that Pivot will issue to Druid.
And my favourite tiny feature in this release: the titles of the browser tabs will now show the names of the data cubes and collections.
Hope you enjoy.
You can get the latest version of Imply on our download page. To learn more, please see our documentation. Any feedback, bug reports and feature requests are always welcome – you can post them in our user
group or contact us.
Splunk Smartstore vs Lumi Loglake: Two Very Different Ways to Search Logs in Object Storage
One copies data back before it can be searched. The other queries it where it lives. Lumi Loglake lets Splunk teams query logs directly in object storage, including AWS S3, Delta Lake, Apache Iceberg, using...
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
Vadim Ogievetsky