Releases: lsst/qserv
2025.12.1
What's Changed
- DM-53597: Fix spurious crashes of the Replication Controller after the previously ingested user databases are deleted (bugs)
Known issues
- DM-53046: Sub-optimal performance of the ANTLR4-based query parser when the query text size is large (many kilobytes). The problem is still under investigation. It may be addressed in a later release (performance)
- DM-52017: Race conditions in the implementation the Qserv query processor for some queries (bugs)
Full Changelog: 2025.11.1-rc1...2025.12.1-rc1
2025.11.1
What's Changed
- DM-53152: Improve error handling in the implementation of the HTTP-based frontend of Qserv (bugs,improvements)
- DM-53041: Thread-safe implementation of CssAccess (bugs)
- DM-48502: Extend Qserv Replication system to automatically create missing databases when new workers are added to Qserv (improvements)
- DM-53037: Upgraded Apache Arrow and Parquet libraries to version 22 (dependencies)
Known issues
- DM-53046: Sub-optimal performance of the ANTLR4-based query parser when the query text size is large (many kilobytes). The problem is still under investigation. It may be addressed in a later release (performance)
- DM-52017: Race conditions in the implementation the Qserv query processor for some queries (bugs)
Full Changelog: 2025.10.1-rc1...2025.11.1-rc1
2025.10.1
What's Changed
- DM-51790: Monitoring user table ingests on the Qserv Web Dashboard (features)
- DM-51474: Upgrade Qserv to XROOTD 5.9.0 (bugs)
- DM-52890: Add INI file value file interpolation capability (refactoring)
- DM-52845: Consolidate schema migrations (refactoring)
- DM-52756: Repair schema migration tools within containers (bugs)
- DM-52928: Fix bugs in the schema migration scripts (bugs)
- DM-52874: Reinforce the table registration API in the Replication Controller to prevent crashes when table or database names are too long. The combined limit for both names is set to 56 bytes. (bugs)
Comments
- The REST API version number changed to 51
- The schema version of the Qserv metadata changed to 17
Known issues
- Sub-optional performance of the ANTLR4-based query parser when the query text size is large (many kilobytes). The problem is still under investigation. It may be addressed in a later release.
Full Changelog: 2025.9.1-rc1...2025.10.1-rc1
2025.9.1
What's Changed
- DM-51988: Upgrade to ANTLR 4.13.2 + thread local DFA (refactoring)
- DM-48953: Update all Qserv Python code to Python 3.12, add the ruff linter, and correct a bunch of basic ruff lints (refactoring)
- DM-49098: Major reorganization of the source tree (refactoring)
Comments
- The release doesn't add or change Qserv functionality of the API. It's mostly meant to mark a major refactoring of the source files and CMake definitions.
Known issues
- Qserv workers may crash in the XROOTD/SSI stack when Qserv is put under heavy load. There are two problems reported in:
- Sub-optional performance of the ANTLR4-based query parser when the query text size is large (many kilobytes). The problem is still under investigation. It may be addressed in a later release.
Full Changelog: 2025.8.2-rc1...2025.9.1-rc1
2025.8.2
What's Changed
- DM-52159: Upgraded MariaDB container to Ubuntu 22.04 LTS
- DM-52137: Fixed a bug in the qmeta schema
- DM-52125: Creating Qserv tables with specified character set and collation
Comments
- The database schema of the Czar's
qservMetadatabase has changed to 15 - The database schema of the Replication system's database has changed to 15
- Qserv REST API version has been changed to 49
- Qserv documentation has been updated
Known issues
- Qserv workers may crash in the XROOTD/SSI stack when Qserv is put under heavy load. There are two problems reported in:
Full Changelog: 2025.8.1-rc1...2025.8.2-rc1
2025.8.1-rc1
What's Changed
- DM-51491: Reinforce database family management services in Qserv to prevent an accidental removal of database entries (bugs)
- DM-51531: Temporary workaround for a problem with the stock version of Sphinx-based documentation builder (bugs)
- DM-51518: The REST service for managing query scheduling parameters (features)
- DM-51585: Unconstrained COUNT(*) queries are not optimized when LIMIT is present (bugs)
- DM-51663: Removed unsafe comparison of the overlap parameter (bugs)
- DM-51775: Special symbols in the database and/or table names need to be properly handled by Qserv (features)
- DM-51699: Improved query progression display on the Web Dashboard (features)
- DM-51605: Improved error reporting for queries hitting the large result limit (features)
- DM-48715: Documented generated columns in the Ingest section of the Qservn (documentation)
- DM-51700: Discarded result files at workers are not deleted automatically before query processing finishes (bugs)
- DM-41534: Improved display for the query scheduling info on the Qserv Web Dashboard (bugs)
- DM-51963: Upgraded Apache Arrow and Parquet libs to version 21
- DM-50683: Completed queries may not be removed from the in-progress metadata table of Qserv (bugs)
- DM-52091: Extended schema of the qmeta database (reengineering)
- DM-51702: Retain the query progression history in Qserv's metadata. Improved query progression display in the Web Dashboard. (features)
Comments
- The database schema of the Czar's
qservMetadatabase has changed to 14. The schema upgrade of the existing Qserv deployments is required. - Qserv REST API version has been changed to 48
Known issues
-
Qserv workers may crash in the XROOTD/SSI stack when Qserv is put under heavy load. There are two problems reported in:
-
Qserv Czar is prone to memory leaks under heavy load if one of the (or many) workers gets unresponsive.
No solutions or workarounds exist for either problem. They are still under investigation.
Full Changelog: 2025.6.2-rc1...2025.8.1-rc1
2025.6.2-rc2
What's Changed
- DM-51663: Unsafe handling of the overlap radius parameter in the database creation REST service of Qserv (bugs)
Comments
- This is an emergency patch for the previous release
-rc1 - The previous releases didn't allow ingesting user-generated tables into Qserv via the HTTP frontend
- Qserv REST API version is the same as in the previous release 43
Known issues
-
Qserv workers may crash in the XROOTD/SSI stack when Qserv is put under heavy load. There are two problems reported in:
-
Qserv Czar is prone to memory leaks under heavy load if one of the (or many) workers gets unresponsive.
No solutions or workarounds exist for either problem. They are still under investigation.
Full Changelog: 2025.6.2-rc1...2025.6.2-rc2
2025.6.2-rc1
What's Changed
- DM-49768: Basic authentication in the Qserv REST services (features)
- DM-51357: Incorrect implementation of the DELETE services in the Qserv HTTP-based frontend (features, bugs)
- Qserv REST API version is now 43
Known issues
-
Qserv workers may crash in the XROOTD/SSI stack when Qserv is put under heavy load. There are two problems reported in:
-
Qserv Czar is prone to memory leaks under heavy load if one of the (or many) workers gets unresponsive.
No solutions or workarounds exist for either problem. They are still under investigation.
Full Changelog: 2025.6.1-rc2...2025.6.2-rc1
2025.6.1-rc2
What's Changed
- DM-51249: Fixed a bug in the result management service of the worker (bugs)
- DM-50504: User-driven garbage collection of the result sets for asynchronous queries in Qserv (features, bugs)
- DM-50874: Extended query status reporting (features)
- DM-51300: Fixed a bug in the result merging algorithm for large results (bugs)
- Qserv REST API version is now 41
Known issues
-
Qserv workers may crash in the XROOTD/SSI stack when Qserv is put under heavy load. There are two problems reported in:
-
Qserv Czar is prone to memory leaks under heavy load if one of the (or many) workers gets unresponsive.
No solutions or workarounds exist for either problem. They are still under investigation.
Full Changelog: 2025.5.3-rc2...2025.6.1-rc2
2025.6.1-rc1
What's Changed
- DM-51249: Fixed a bug in the result management service of the worker (bugs)
- DM-50504: User-driven garbage collection of the result sets for asynchronous queries in Qserv (features, bugs)
- DM-50874: Extended query status reporting (features)
Known issues
-
Qserv workers may crash in the XROOTD/SSI stack when Qserv is put under heavy load. There are two problems reported in:
-
Qserv Czar is prone to memory leaks under heavy load if one of the (or many) workers gets unresponsive.
No solutions or workarounds exist for either problem. They are still under investigation.
Full Changelog: 2025.6.1-rc1...2025.5.3-rc2