Conversation
|
🚀 Build success! Latest successful preview: https://preview-414--questdb-documentation.netlify.app/docs/ Commit SHA: 1df4a59
|
Use human-readable time suffixes for config defaults instead of raw microsecond values. Add note that time-suffixed values are accepted. Add worker.affinity and worker.sleep.timeout to the config table. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
javier
left a comment
javier
left a comment
There was a problem hiding this comment.
Nice docs, but I think we need to change a few things
| Only the specified settings are changed. Omitted settings retain their current | ||
| values. | ||
|
|
||
| The same syntax applies to materialized views: |
There was a problem hiding this comment.
I don't think we need to provide so many details about materialized views. Maybe a link at the bottom for a see also, but not so many examples about materialized views in the alter table page
|
|
||
| ```questdb-sql | ||
| GRANT SET STORAGE POLICY ON trades TO analyst; | ||
| GRANT REMOVE STORAGE POLICY ON trades TO admin; |
There was a problem hiding this comment.
is this correct? I thought with remove you had to use FROM?
| The view's TTL is independent of the base table's TTL. See | ||
| [TTL documentation](/docs/concepts/ttl/) for details. | ||
|
|
||
| ## Storage Policy |
There was a problem hiding this comment.
The syntax at the top should show TTL or STORAGE POLICY. Now this is display only in the section, but not at the top syntax
| @@ -277,6 +277,45 @@ Time units: `HOURS`, `DAYS`, `WEEKS`, `MONTHS`, `YEARS` | |||
| The view's TTL is independent of the base table's TTL. See | |||
| [TTL documentation](/docs/concepts/ttl/) for details. | |||
There was a problem hiding this comment.
We probably need to make a note that TTL is not supported anymore for enterprise and to use Storage Policy instead
There was a problem hiding this comment.
And that if you have a view with TTL and want to move to storage policy, you need to disable TTL before
There was a problem hiding this comment.
Should we add this also to the errors section at the bottom of the page?
| @@ -241,6 +241,49 @@ information on the behavior of this feature. | |||
|
|
|||
| ::: | |||
There was a problem hiding this comment.
We need to add STORAGE POLICY as an alternative to TTL in the syntax blocks at the top of the page. Now it is only in its own section.
There was a problem hiding this comment.
We also need to explain (as in create mat view) that TTL is not supported anymore in enterprise when creating a table.
| [ALTER TABLE SET STORAGE POLICY](/docs/query/sql/alter-table-set-storage-policy/). | ||
|
|
||
| :::note | ||
|
|
There was a problem hiding this comment.
This block should be at the TTL section, not in this one
| To modify a storage policy after creation, see | ||
| [ALTER MATERIALIZED VIEW SET STORAGE POLICY](/docs/query/sql/alter-mat-view-set-storage-policy/). | ||
|
|
||
| :::note |
There was a problem hiding this comment.
This block should be at the TTL section
3 participants
Summary
concepts/storage-policy.md) documenting the Enterprise feature for automated partition lifecycle management (convert to Parquet, drop native, drop local, drop remote)query/sql/alter-table-set-storage-policy.md) with full syntax, constraints, permissions, and examplesSTORAGE POLICYclause documentation to the CREATE TABLE reference pageDROP PARTITIONsidebars.jsTest plan
yarn buildsucceeds with no broken links🤖 Generated with Claude Code