Operations

Each step inside up: / down: is identified by an op: key. The table summarizes effect and auto-reversibility; click through for a detailed description, runnable example, and the full list of spec fields.

`op:`	Effect	Auto-reversible?
`create_collection`	Create a collection from a full spec	✔ → `delete_collection`
`delete_collection`	Drop a collection	✘ (data loss)
`update_collection`	Patch `hnsw_config`, `quantization_config`, `optimizers_config`, or per-vector params in place	✘ (prior state unknown)
`create_vector`	Add a named dense vector (Qdrant v1.18+)	✔ → `delete_vector`
`create_sparse_vector`	Add a named sparse vector	✔ → `delete_vector`
`delete_vector`	Drop a named vector	✘ (data loss)
`create_payload_index`	Index a payload field	✔ → `delete_payload_index`
`delete_payload_index`	Remove a payload index	✔ iff `schema:` is given
`create_alias`	Point an alias at a collection	✔ → `delete_alias`
`delete_alias`	Remove an alias	✘ (target unknown)
`switch_alias`	Atomically repoint an alias (zero-downtime swap)	✘ (prior target unknown)
`exec`	Run a shell command (the re-embedding escape hatch)	✘ unless `down` provided

When an operation isn't auto-reversible, supply an explicit down: block — then revector down uses it verbatim.

The shapes referenced by these operations (CollectionSpec, VectorSpec, HnswConfigSpec, …) are documented on the Specs page.