Skip to content

docs: cover TTL on materialized views in the TTL concept page #482

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
PedroHenrique0713 wants to merge 1 commit into
base: main
Choose a base branch
from
Open

docs: cover TTL on materialized views in the TTL concept page #482

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
19 changes: 19 additions & 0 deletions documentation/concepts/ttl.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -71,6 +71,25 @@ ALTER TABLE trades SET TTL 2w;
For full syntax, see
[ALTER TABLE SET TTL](/docs/query/sql/alter-table-set-ttl/).

### On materialized views

Materialized views support TTL as well, both at creation and afterward:

```questdb-sql
-- At view creation
CREATE MATERIALIZED VIEW trades_hourly AS (
SELECT timestamp, symbol, avg(price) AS avg_price FROM trades SAMPLE BY 1h
) PARTITION BY DAY TTL 7 DAYS;

-- On an existing view
ALTER MATERIALIZED VIEW trades_hourly SET TTL 7 DAYS;
```

A view's TTL is independent of its base table's TTL. For full syntax, see
[CREATE MATERIALIZED VIEW](/docs/query/sql/create-mat-view/#ttl-time-to-live)
and
[ALTER MATERIALIZED VIEW SET TTL](/docs/query/sql/alter-mat-view-set-ttl/).

## How TTL works

TTL drops partitions based on the **partition's time range**, not individual row
Expand Down