Bump org.questdb:questdb from 6.5.3 to 8.3.2

[dependabot]

Bumps org.questdb:questdb from 6.5.3 to 8.3.2.

Release notes

Sourced from org.questdb:questdb's releases.

8.3.2 is a stability release, bringing a number bugfixes and improvements. There have been improvements to materialized views, checkpoints, zfs support, and instance metrics, and of course, our built-in web console!

Materialized Views can now be configured to refresh on a timed schedule, instead of immediately whenever new data is written. You can also modify the TTL and refresh limit post-creation, giving you more flexibility to optimise current and new views.

Taking checkpoints will now consume much less disk space, and we've also added some new metrics to help you to monitor your overall database's health, and be alerted to writing delays or suspended tables.

The web console now allows you to set the instance name and colour. This is especially useful for production users, who have multiple deployments and flick between them. This should make it easier keep track of things, and label the instance with a useful name for its users.

This release will shortly be followed by the first beta release of the new ARRAY type. This is a multi-dimensional array (think NumPy), which will initially support DOUBLE values. This will be accompanied by the first upgardes for the ILP clients, to move from the text protocol to a bespoke binary protocol. This means arrays can be sent to the database efficiently, without expansion into lots of text, and is the first step towards supporting all of QuestDB's rich features through the database clients.

For any questions or feedback, please join us on Slack or on Discourse.

See also our prettier release notes page.

Breaking changes 💥

• The greatest and least functions will now only return a null if all of the inputs are null, instead of any. This aligns the behaviour with MSSQL.

• The WITHIN function now defaults to a different implementation, which runs WITHIN before LATEST BY.

  • If you were using the old implementation, which ran LATEST BY first, you can re-enable it using query.within.latest.by.optimisation.enabled=true. This variant was only used for WHERE + LATEST BY + indexed symbols, and at no other time.
  • Or alternatively, use the new implementation and a subquery to force the LATEST BY to run first.

Highlights

UI

• The web console now allows you to set an instance's name and colour! This is handy when switching between different deployments and instances, to make sure you run your queries on the correct console.
• The query log UI element has been upgraded, fixing a few snags, and now supports horizontal scrolling for long rows.
• (Enterprise) SSO users will not have to log back in every time they log out; instead, an existing SSO session can be resumed, or you can switch to a different account.

Prometheus Metrics

New metrics have been added to help monitor the performance of tier-1 (WAL) and tier-2 (Table) storage:

• suspended_tables; this is a global counter for how many tables are currently suspended.
• wal_apply_seq_txn; this is a global counter for sequencerTxn, the txn number corresponding to the latest transaction written to WAL, for a particular table.
• wal_apply_writer_txn; this is a global counter for writerTxn, the txn number corresponding to the latest transaction visible for read, for a particular table.
• You can subtract the above two numbers and track this over time, to estimate if the database is backing up and falling behind on data visibility.
• You can also track replication lag by comparing metrics between the primary and the replica. More granular information can be obtained by polling wal_tables() and sys.telemetry_wal;

Materialized Views

• Materialized Views can now be refreshed on a timer schedule.
  • CREATE MATERIALIZED VIEW price_1h REFRESH START '2025-09-12T00:00:00.000000Z' EVERY 1h AS ...

... (truncated)

Commits

• c818e61 [maven-release-plugin] prepare release 8.3.2
• cb51707 feat(sql): timer refresh for materialized views (#5695)
• 5baba7a chore(ui): upgrade web console to 0.7.11 (#5694)
• aab1c96 Revert "feat(sql): timer refresh for materialized views (#5678)"
• 9374c78 chore(core): instance info into telemetry (#5689)
• 882524d feat(sql): timer refresh for materialized views (#5678)
• f7e1f59 test(sql): fix flaky test testCancelMultipleQueries (#5691)
• 392b04e test(http): fix flaky test (#5673)
• 1743b69 feat(sql): breaking change 💥 - parallel filtering geohashes using WITHIN (...
• 3c4e38a chore(core): add preferences to /settings (#5621)
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)