QuasarDB 3.8.10 Released

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 may have not properly reacquired the lock for writing
  • [daemon] Name differently the high and low partitions threads
  • [daemon] Properly set the default for the advertized address
  • [daemon] Reset the ACL fetcher on error
  • [daemon] Skip missing buckets when aggregating instead of failing
  • [query] FROM table.column was incorrectly accepted as a valid clause
  • [replication] Properly replicate tags
  • [shell] Fixed a potential segmentation fault when using quotation marks
  • [shell] Fixed invalid format for integers
  • [shell] Log warnings related to the history file instead of displaying them on the console
  • [shell] No output was given when a script file was not properly specified

Recent Posts

Quasar “Seneca” 3.13.0 Beta Released

Where is 3.11? You may have noticed that we skipped the 3.11 (beta) and 3.12

Quasar showcased on AWS marketplace

We are very proud to announce that Quasar is front and center on the AWS

QuasarDB is now Quasar

I am thrilled to announce that QuasarDB has become Quasar. If you're already a Quasar

QuasarDB 3.10.0 Stable Released

We are very pleased to announce the immediate availability of QuasarDB 3.10.0. You can get

QuasarDB 3.9.9 Beta released

We are very pleased to announce the immediate availability of QuasarDB 3.9.9. This release brings

Try the community edition now!