QuasarDB 3.8.6 released
We are pleased to announce the immediate availability of QuasarDB 3.8.6. This is a bug fix and performance improvement release. All QuasarDB users are encouraged to update to the 3.8.6 version.
Changes in this version
- [daemon] Greatly improve compression for tables with many columns (> 4)
- [query] SELECT + WHERE will now properly apply the LIMIT server side
- [query] Add support for CREATE TABLE IF NOT EXISTS
- [shell] Log where the history is stored on startup
- [shell] Do not attempt to read stdin (nohup incompatibility issue)
QuasarDB 3.8.5 released
We are pleased to announce the immediate availability of QuasarDB 3.8.5. This is a bug fix and performance improvement release. All QuasarDB users are encouraged to update to the 3.8.5 version.
Changes in this version
- [daemon] If the server encounters a corrupted bucket, it will return an empty result instead of failing the complete query
- [daemon] Fix a bug introduced in 3.8.4 that could prevent the ring from stabilizing
- [daemon] Fix an insertion bug introduced in 3.7.0 that could insert non-existing null values
- [dbtool] Correctly print timestamp values
- [python] Fix an improper UTF-8 string handling
QuasarDB 3.8.4 released
We are pleased to announce the immediate availability of QuasarDB 3.8.4. This is a bug fix and performance improvement release. All QuasarDB users are encouraged to update to the 3.8.4 version.
Changes in this version
- [daemon] Clustering: allow out of order startup of nodes
- [daemon] Add an option to disable background replication and migration
- [daemon] Add chord statistics to monitor cluster stability
- [daemon] Increase logs verbosity on metadata errors
- [daemon] No longer migrate data on startup by default
- [replication] Prevent the replication to create transaction conflicts
- [dbtool] Add upgrade, dump shard, and repair commands
- [dbtool] Add a “force” option to force upgrading the indexes
- [maxcon] Allow the max connection tool to connect to a secure cluster
QuasarDB 3.8.3 released
We are pleased to announce the immediate availability of QuasarDB 3.8.3. This is a bug fix and performance improvement release. All QuasarDB users are encouraged to update to the 3.8.3 version.
Changes in this version
- [daemon] Increase timeseries bucket I/O efficiency
- [daemon] direct_prefix_get did not properly match prefixes
- [daemon] Fix disk usage results
- [api] Properly return "not implemented" instead of "internal error" for certain GROUP BY queries
- [shell] Fix invalid alignment of results containing NULL values
- [shell] Properly retrieve cluster status information on secured clusters
- [grafana] Properly transform blob and string values
QuasarDB 3.8.2 release and an update on our process
We are pleased to announce that QuasarDB 3.8.2 is available. The 3.8.2 release features important bug fixes for the 3.8.0 release and all users are advised to upgrade.
As our user base grew significantly in the last months, we have decided to update our release process to reflect the needs of our customers.
You can learn more about our updated release process in this blog post.
QuasasrDB "Crates" 3.8.0 available!
We are very pleased to announce the immediate availability of QuasarDB 3.8.0.
This release focuses on performance improvement and lower memory usage.
Important: the default binaries are now optimized for Haswell architectures (previous versions were targeting Westmere). You will need to use the Core2 builds if your architecture is older than Haswell.
New features
- [query] Support for INSERT TRUNCATE
Fixes and improvements
- [query] Significant performance improvement to GROUP BY queries for high-cardinality results
- [daemon] Properly honor cgroups memory restrictions (Docker and Kubernetes)
- [daemon] Fixed backtrace functions log in Linux
- [client] Optimized client/server communications for better performance