RERANK.GET
RERANK.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 rerank-cache license feature
The rerank cache stores cross-encoder rerank scores for a query and document pair in a retrieval pipeline, so a repeated pair does not have to be scored again. RERANK.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
RERANK.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 'rerank.get' commandif the argument count is wrong.NOLICENSE rerank-cache requires a HotKV license. Contact sales@hotkv.comif your license does not include thererank-cachefeature.
Examples
Section titled “Examples”127.0.0.1:6379> RERANK.SET rerank_scores "reset password|doc:1:0" "0.873"OK127.0.0.1:6379> RERANK.GET rerank_scores "reset password|doc:1:0""0.873"127.0.0.1:6379> RERANK.GET rerank_scores "unknown"(nil)Compatibility
Section titled “Compatibility”HotKV-only command. Redis and Valkey have no equivalent.
See also
Section titled “See also”RERANK.CREATE, RERANK.SET, RERANK.DEL, RERANK.STATS, RERANK.FLUSH, RERANK.DROP, RERANK.LIST, AI features guide
Was this page helpful?
Thanks for the feedback.