Materialized views without SAMPLE BY: latest state, filtered feeds and enrichment
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 20/100
Research direction
Start with the implementation referenced as questdb/questdb#7263 and compare its scope with related issue #114. Review superseding issue #137 before choosing work, then verify whether projection, latest-by, join, retention, permissions, and replication requirements are covered.
Written by the indexing model from the issue text.
Description
Summary
Materialized views that keep rows rather than time buckets: projection views that hold a filtered, column-selected mirror of a base table, latest-by views that hold the current row per key, and join views that enrich base rows with other tables. They use today's refresh model, reading from the base table once its WAL transactions have been applied, and refresh incrementally like SAMPLE BY views. Row-level retention keeps them bounded.
Current Limitations
- Materialized views require
SAMPLE BYor a time-basedGROUP BY; a view cannot simply keep rows - The current state per key needs a
LATEST ONscan over the base table on every read - Enrichment without aggregation, such as an
ASOF JOINof trades with quotes, cannot be materialized - There is no way to keep a bounded, continuously pruned copy of a table
Features
| Feature | Description |
|---|---|
| Projection views | A filtered, column-selected mirror of the base table that refreshes incrementally as rows arrive |
| Latest-by views | One row per key holding the most recent state, maintained as data arrives instead of a LATEST ON scan per query |
| Join views | Base rows enriched through JOIN, including ASOF JOIN, with no SAMPLE BY required; the base table triggers refresh, and refresh from joined tables is tracked in #114 |
| Row-level retention | EXPIRE ROWS on a view: expire by predicate, keep the latest row per key, or keep the N highest or lowest per group, with background reclamation where the predicate allows |
| Same tooling | Incremental refresh, TTL, SHOW CREATE MATERIALIZED VIEW, materialized_views() and replication behave as for existing views |
How it works
- The view declares its query; no
SAMPLE BYis needed. - As WAL transactions are applied to the base table, the view refreshes incrementally over the new rows.
- Reads over a view with a retention policy are filtered so expired rows disappear immediately, and disk is reclaimed in the background.
Example
Illustrative syntax:
-- projection: a filtered mirror of trades
CREATE MATERIALIZED VIEW aapl_trades AS (
SELECT timestamp, price, amount FROM trades WHERE symbol = 'AAPL'
);
-- latest-by: current state per key, bounded by retention
CREATE MATERIALIZED VIEW positions AS (
SELECT * FROM fills
) EXPIRE ROWS KEEP LATEST ON timestamp PARTITION BY account, symbol;
-- join: trades enriched with the prevailing quote
CREATE MATERIALIZED VIEW enriched_trades WITH BASE trades AS (
SELECT t.timestamp, t.symbol, t.price, q.bid, q.ask
FROM trades t ASOF JOIN quotes q ON (symbol)
);
Benefits
- Current state in one read — positions, last quotes and device status come from a view instead of a
LATEST ONscan - Bounded working sets — retention keeps a view to the rows that matter without touching the base table
- Enrichment materialized once — joins run as data arrives, not on every dashboard query
- The shapes push needs — these views are what subscriptions (#111) attach to and what the ticking grid (#132) reads
Scope
- Projection views
- Latest-by views with
KEEP LATESTretention - Join views, including
ASOF JOIN -
EXPIRE ROWSretention policies with background reclamation - Permissions and replication support in QuestDB Enterprise
Implementation: questdb/questdb#7263. Related: #114 (refresh triggered by joined tables). Followed by #137, which moves all views onto the WAL-fed live view model.
- Dominant language
- No language data
- Stars
- 7
- Forks
- 0
- PR merge metrics
- No merged PRs in 30d
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from questdb/roadmap
-
enterprise security
-
open source SQL
Difficulty 5/5 Over a week Newbie friendliness 25/100
-
enterprise open format storage
Difficulty 5/5 Over a week Newbie friendliness 25/100
-
enterprise high availability
Difficulty 5/5 Over a week Newbie friendliness 25/100
-
enterprise open source UI
Difficulty 5/5 Over a week Newbie friendliness 25/100
Similar issues
-
bug: AI Gateway client filter lists "Unknown" twice when NULL and literal Unknown clients coexist Openbug
Difficulty 2/5 1-3 hours Newbie friendliness 90/100
-
[BUG] A column whose default is the empty string is drawn in the ER diagram as having no default Openbug database-provider good first issue hacktoberfest
Difficulty 2/5 1-3 hours Newbie friendliness 90/100
libredb/libredb-studio#1030 · 6 comments ·
-
comp-datalake
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
ClickHouse/ClickHouse#121222 ·
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
-
bug redshift
Difficulty 2/5 1-3 hours Newbie friendliness 88/100