Although ClickHouse is geared toward high volume analytic workloads, it is possible in some situations to modify or
delete existing data. These operations are labeled “mutations” and are executed using the ALTER TABLE command.
Updating data
Use the ALTER TABLE...UPDATE command to update rows in a table:
ALTER TABLE [<database>.]<table> UPDATE <column> = <expression> WHERE <filter_expr><expression> is the new value for the column where the <filter_expr> is satisfied. The <expression> must be the same datatype as the column or be convertible to the same datatype using the CAST operator. The <filter_expr> should return a UInt8 (zero or non-zero) value for each row of the data. Multiple UPDATE <column> statements can be combined in a single ALTER TABLE command separated by commas.
Examples:
-
A mutation like this allows updating replacing
visitor_idswith new ones using a dictionary lookup:ALTER TABLE website.clicks UPDATE visitor_id = getDict('visitors', 'new_visitor_id', visitor_id) WHERE visit_date < '2022-01-01' -
Modifying multiple values in one command can be more efficient than multiple commands:
ALTER TABLE website.clicks UPDATE url = substring(url, position(url, '://') + 3), visitor_id = new_visit_id WHERE visit_date < '2022-01-01' -
Mutations can be executed
ON CLUSTERfor sharded tables:ALTER TABLE clicks ON CLUSTER main_cluster UPDATE click_count = click_count / 2 WHERE visitor_id ILIKE '%robot%'
Deleting data
Use the ALTER TABLE command to delete rows:
ALTER TABLE [<database>.]<table> DELETE WHERE <filter_expr>The <filter_expr> should return a UInt8 value for each row of data.
Examples
-
Delete any records where a column is in an array of values:
ALTER TABLE website.clicks DELETE WHERE visitor_id in (253, 1002, 4277) -
What does this query alter?
ALTER TABLE clicks ON CLUSTER main_cluster DELETE WHERE visit_date < '2022-01-02 15:00:00' AND page_id = '573'
View the DELETE statement docs page for more details.
Lightweight deletes
Another option for deleting rows is to use the DELETE FROM command, which is referred to as a lightweight delete. The deleted rows are marked as deleted immediately and will be automatically filtered out of all subsequent queries, so you don’t have to wait for a merging of parts or use the FINAL keyword. Cleanup of data happens asynchronously in the background.
DELETE FROM [db.]table [ON CLUSTER cluster] [WHERE expr]For example, the following query deletes all rows from the hits table where the Title column contains the text hello:
DELETE FROM hits WHERE Title LIKE '%hello%';A few notes about lightweight deletes:
- This feature is only available for the
MergeTreetable engine family. - Lightweight deletes are synchronous by default, waiting for all replicas to process the delete. The behavior is controlled by the
lightweight_deletes_syncsetting.