VSIM.SAVE
VSIM.SAVE name blob
- Group
- Vector search
- Complexity
- O(N) where N is the size of the blob
- Arity
- 3 (exactly, counting the command name)
- Flags
- write, slow
- HotKV Cloud
- Performance and Scale
- On-Premise
- requires the vsim-persist license feature
VSIM persistence stores named blobs of vector data that you supply, such as an exported set of embeddings, as files on the server, separate from your snapshots and AOF. Each blob goes to a file named after it in the directory set by dir under [vsim_persist] (default vsim_snapshots) when enabled = true there. The files are local to each server, also in a cluster. VSIM.SAVE writes blob (any string or binary value) under
name, replacing a blob already saved under that name. It creates the
directory if needed. Names are 1 to 128 characters and cannot contain /, \, ., : or control characters.
Return value
Section titled “Return value”| Case | RESP2 | RESP3 |
|---|---|---|
| Blob saved | Integer: the number of bytes written to the file | Same |
Errors:
ERR invalid snapshot nameif the name breaks the rules above.ERR cannot create snapshot directoryorERR cannot open file for writingif the server cannot write to the directory.ERR wrong number of arguments for 'vsim.save' commandif the argument count is wrong.NOLICENSE vsim-persist requires a HotKV license. Contact sales@hotkv.comif your license does not include thevsim-persistfeature.
Examples
Section titled “Examples”127.0.0.1:6379> VSIM.SAVE products-2026-10 "0.12,0.98,0.44;0.10,0.95,0.40"(integer) 41127.0.0.1:6379> VSIM.SAVE bad/name "x"(error) ERR invalid snapshot nameCompatibility
Section titled “Compatibility”HotKV-only command. Redis and Valkey have no equivalent.
See also
Section titled “See also”Was this page helpful?
Thanks for the feedback.