Skip to content
HotKVDocs

Ask the HotKV docs

Answers come only from these docs and can be wrong; check the linked pages before you rely on them.

GUARD.GET

Last updated 
GUARD.GET namespace key
Group
Keyed caches
Complexity
O(1)
Arity
3 (exactly, counting the command name)
Flags
read-only, fast
Keys
first 1, last 1, step 1
HotKV Cloud
Performance and Scale
On-Premise
requires the guard-cache license feature

The guard cache stores only responses that have already passed your schema validation or guardrail checks, so a hit is known to be safe to replay without checking it again. GUARD.GET returns the value stored under key, which must match byte for byte. In an existing namespace, each call counts as a hit or a miss in GUARD.STATS. An expired entry counts as a miss.

Return value

Section titled “Return value”
Case RESP2 RESP3
Hit Bulk string: the cached value Same
Miss, expired entry, or unknown namespace Nil bulk string Null

Errors:

  • ERR wrong number of arguments for 'guard.get' command if the argument count is wrong.
  • NOLICENSE guard-cache requires a HotKV license. Contact sales@hotkv.com if your license does not include the guard-cache feature.

Examples

Section titled “Examples”
127.0.0.1:6379> GUARD.SET validated "Summarize ticket 812 as JSON" "{\"summary\":\"Login fails on Safari\"}"
OK
127.0.0.1:6379> GUARD.GET validated "Summarize ticket 812 as JSON"
"{\"summary\":\"Login fails on Safari\"}"
127.0.0.1:6379> GUARD.GET validated "unknown"
(nil)

Compatibility

Section titled “Compatibility”

HotKV-only command. Redis and Valkey have no equivalent.

See also

Section titled “See also”

GUARD.CREATE, GUARD.SET, GUARD.DEL, GUARD.STATS, GUARD.FLUSH, GUARD.DROP, GUARD.LIST, AI features guide