Skip to content

chore: update cloud-rules-api.mdx #20800

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.

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

Merged
merged 1 commit into from
May 30, 2025
Merged
Changes from all commits
Commits
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
Original file line number Diff line number Diff line change
Expand Up @@ -18,7 +18,7 @@ There are two categories of rules you can create:
```sql
DELETE dropAttr1, dropAttr2 FROM DATA_TYPE (WHERE OPTIONAL_FILTER)
```
* For this type of rule, you must pass in a non-empty list of **raw** attributes names in the `SELECT` clause.
* For this type of rule, you must pass in a non-empty list of **raw** attributes names in the `DELETE` clause.

<Callout variant="tip">
Pipeline Control cloud rules only apply to data that arrives from the moment you create the rule, they don't delete data that's [already been ingested](/docs/telemetry-data-platform/ingest-manage-data/manage-data/manage-data-retention#data-deletion).
Expand Down