We are very pleased to announce the immediate availability of QuasarDB 3.9.8. This release is planned to be the penultimate beta before 3.10. It includes several bug fixes and improvements related to query results. Several features have also been added to fix accidental data duplications or operational-induced data corruptions without shutting down the cluster. 32-bit […]
We are very proud to announce that, following our commercial successes in the US, we have officially joined Engage’s Spring 2021 Enterprise Go-To-Market program. Engage is changing corporate innovation and venture capital by introducing a collaborative venture investment model for corporations. Their partners are AT&T, Chick-fil-A, Cox Enterprises, Delta Air Lines, Georgia-Pacific, Georgia Power Foundation, Georgia […]
We are very pleased to announce the immediate availability of QuasarDB 3.9.7. As we approach the end of the beta cycle, this release bring stability, performance, and quality of life improvements. Get it here! Fixes and improvements [daemon] Add an option to unconditionally uncache entries after write [daemon] Add several statistics related to asynchronous pipelines […]
Industrial Internet of Things (IIoT) is facing the new challenge of having to ingest very high volume of timeseries data and perform complex analysis in real time. In this blog post, we share with you the lessons we’ve learned along the way.
We are very pleased to announce the immediate availability of QuasarDB 3.8.10. This release brings stability and quality of life improvements. Fixes and improvements Protocol version 35 [api] Properly handle empty partial results [daemon] Add more context to the “invalid depot path” error message [daemon] Fixed a rare issue, when, during writes, previously cached entries […]
We are very pleased to announce the immediate availability of QuasarDB 3.9.5. This release further extends the capabilities of FIND() and comes with several quality of life improvements. Fixes and improvements [api] Fixed an internal error when the direct API was used with the wrong URI [daemon] Fixed a a couple of warning/error log messages […]