5.2 KiB
| slug | sidebar_position | sidebar_label |
|---|---|---|
| /en/sql-reference/statements/alter/ | 35 | ALTER |
ALTER
Most ALTER TABLE queries modify table settings or data:
:::note
Most ALTER TABLE queries are supported only for *MergeTree tables, as well as Merge and Distributed.
:::
These ALTER statements manipulate views:
- ALTER TABLE ... MODIFY QUERY — Modifies a Materialized view structure.
- ALTER LIVE VIEW — Refreshes a Live view.
These ALTER statements modify entities related to role-based access control:
ALTER TABLE ... MODIFY COMMENT statement adds, modifies, or removes comments to the table, regardless if it was set before or not.
Mutations
ALTER queries that are intended to manipulate table data are implemented with a mechanism called “mutations”, most notably ALTER TABLE … DELETE and ALTER TABLE … UPDATE. They are asynchronous background processes similar to merges in MergeTree tables that to produce new “mutated” versions of parts.
For *MergeTree tables mutations execute by rewriting whole data parts. There is no atomicity - parts are substituted for mutated parts as soon as they are ready and a SELECT query that started executing during a mutation will see data from parts that have already been mutated along with data from parts that have not been mutated yet.
Mutations are totally ordered by their creation order and are applied to each part in that order. Mutations are also partially ordered with INSERT INTO queries: data that was inserted into the table before the mutation was submitted will be mutated and data that was inserted after that will not be mutated. Note that mutations do not block inserts in any way.
A mutation query returns immediately after the mutation entry is added (in case of replicated tables to ZooKeeper, for non-replicated tables - to the filesystem). The mutation itself executes asynchronously using the system profile settings. To track the progress of mutations you can use the system.mutations table. A mutation that was successfully submitted will continue to execute even if ClickHouse servers are restarted. There is no way to roll back the mutation once it is submitted, but if the mutation is stuck for some reason it can be cancelled with the KILL MUTATION query.
Entries for finished mutations are not deleted right away (the number of preserved entries is determined by the finished_mutations_to_keep storage engine parameter). Older mutation entries are deleted.
Synchronicity of ALTER Queries
For non-replicated tables, all ALTER queries are performed synchronously. For replicated tables, the query just adds instructions for the appropriate actions to ZooKeeper, and the actions themselves are performed as soon as possible. However, the query can wait for these actions to be completed on all the replicas.
For all ALTER queries, you can use the replication_alter_partitions_sync setting to set up waiting.
You can specify how long (in seconds) to wait for inactive replicas to execute all ALTER queries with the replication_wait_for_inactive_replica_timeout setting.
:::note
For all ALTER queries, if replication_alter_partitions_sync = 2 and some replicas are not active for more than the time, specified in the replication_wait_for_inactive_replica_timeout setting, then an exception UNFINISHED is thrown.
:::
For ALTER TABLE ... UPDATE|DELETE queries the synchronicity is defined by the mutations_sync setting.