Use VECTOR.DEL to remove the vector stored under an ID.
The reply is 1 when the ID was present and 0 when it was not, so the call is safe to repeat. Removing the last vector does not delete the index: it stays in place, ready for new writes, until VECTOR.DROP removes it.
Vector indexes are an Upstash extension. See the vector command overview for how an index is created, written to, and queried.
Syntax#
Arguments#
| Argument | Required | Repeatable | Description |
|---|---|---|---|
<index> | Yes | No | Key holding the vector index. |
<id> | Yes | No | Identifier to remove. Cannot be empty. |
Important points#
- An index that does not exist returns
ERR Index <index> is not found.
Response#
The reply reports the result of the operation. Error replies have the same shape in RESP2 and RESP3 and are surfaced as exceptions by the SDKs below.
| Protocol | Reply |
|---|---|
| RESP2 | Integer: 1 if the ID was removed, 0 if it was not in the index |
| RESP3 | Integer: 1 if the ID was removed, 0 if it was not in the index |
Client libraries often decode bulk strings, maps, sets, and numeric strings into language-native values. The table describes the Redis wire reply.
Examples#
TCP examples use the TLS REDIS_URL from the Upstash console. REST examples use UPSTASH_REDIS_REST_URL and UPSTASH_REDIS_REST_TOKEN.
Redis CLI
@upstash/redis
This command is not supported yet in @upstash/redis.
upstash_redis
This command is not supported yet in upstash_redis.