QuasarDB "Seneca" 3.14.1 Released

We are thrilled to announce the immediate availability of QuasarDB 3.14.1, an update from 3.14.0.

This update brings major new features while being 100% compatible with 3.14.0. Features such as streaming aggregation (named aggregated tables) and automatic data expiration are now available to all users.

Streaming aggregations enable you to aggregate the data as it comes and store the aggregate, unlocking ultra-low latency analytics while crushing disk usage.

In addition, we’ve added numerous performance enhancements, query functionalities, and bug fixes, that make the upgrade to 3.14.1 highly recommended!

Change log

(w.r.t. 3.14.0)

  • Protocol version 48
  • [arm64] Optimized several functions to leverage ARM Neon SIMD
  • [compression] Slight improvement in (de)compression speed
  • [daemon] Upsert now properly replaces all duplicates
  • [kernel] Add support for TTL in tables
  • [kernel] General availability of AGGREGATED tables (streaming analytics)
  • [kernel] Overall improvement of insertion performance across the board
  • [linux] Fixed stack trace symbol dump
  • [orderbook] Can now generate order books on a list of timestamps and offsets
  • [orderbook] Significant performance improvement of the Currenex order book engine
  • [orderbook] The account ID column is now properly displayed
  • [query] Add round, ceil, and floor functions
  • [query] Add support for complex ASOF joins across multiple tables
  • [query] Add support for count($timestamp)
  • [query] Add support for interpolation in GROUP BY queries
  • [query] Add support for JSON operators
  • [query] Add support for LEAD() and LAG() for sliding window queries
  • [query] ASOF now has a consistent behavior when there are NULL values
  • [query] Can now drop a column that has a name made of a single character
  • [query] Columns with different symbol tables can now be compared
  • [query] Fix invalid first() and last() result for certain complex queries
  • [query] Significant improvement for GROUP BY spanning thousands of tables
  • [query] Support composition for correlation
  • [query] Support for HAVING with PIVOT

by Edouard Alligand

QuasarDB "Seneca" 3.14.0 Released

We are thrilled to announce the immediate availability of QuasarDB 3.14.0, an update from 3.13.7.

Multiple performance and fixes have been added in this release, as well as support for multiple readers from a single S3 bucket, improved S3 backup speed, and, last but not least, initial support for windowing functions with the SQL OVER syntax.

This version sets a new standard in terms of speed, compression, and analytical power for timeseries databases and has been battle tested over multiple petabytes data sets in use case as diverse as asset health monitoring, orderbook analysis, cybersecurity, and electric grid simulations.

Get QuasarDB 3.14.0 here!

Change log

(w.r.t. 3.13.7)

  • Protocol version 48
  • [api] Add a function to trim a single entry
  • [client] Compiler, build, cpu, and allocator are now in the –version output
  • [daemon] Add support for multiple instances over the same S3 bucket (one writer, many readers)
  • [daemon] Add support for short-term credentials for S3 authentication
  • [daemon] Sensitive parameters are now hidden from the log
  • [daemon] Significantly increased S3 backup speed
  • [daemon] Trimming multiple entries is now done in a dedicated background thread
  • [kernel] Fix an issue where old buckets could not be updated after a new column was added to a table
  • [kernel] Trimming a timeseries now includes the root
  • [odbc] Add support for log size limit and rotation
  • [odbc] Log verbosity is now configurable, and the default value has been lowered
  • [orderbook] Currenex ORDERBOOK function is more tolerant of errors
  • [orderbook] Fix a bug related to time ranges and Currenex data
  • [orderbook] Greatly improved the performance of the ORDERBOOK functions for Currenex data
  • [persistence] Reduces the chances for data loss in case of an operating system failure during a trimming operation
  • [persistence] S3 Backups can now be done using multiple threads
  • [query] Initial support for Windowing functions (SQL OVER())

by Edouard Alligand