HPERSIST
HPERSIST key FIELDS numfields field [field ...]
- Group
- Hash
- Complexity
- O(N) where N is the number of fields given
- Arity
- -5 (at least 5 words, counting the command name)
- Flags
- write, fast
- Keys
- first 1, last 1, step 1
- HotKV Cloud
- All plans
- On-Premise
- no license needed
HPERSIST removes the time to live from each listed field of the hash at
key, so the fields no longer expire. The values are not changed.
FIELDS must come right after the key, and numfields must equal the number
of field names that follow.
Return value
Section titled “Return value”An array with one integer per field, in the order given, under both RESP2 and RESP3:
| Code | Meaning |
|---|---|
-2 |
The field or the key does not exist. |
-1 |
The field exists but had no time to live. |
1 |
The time to live was removed. |
The errors are the same as for HTTL: WRONGTYPE for a key
that is not a hash, and the FIELDS / numfields errors.
Examples
Section titled “Examples”127.0.0.1:6379> HSET session:9 token "abc" user "42"(integer) 2127.0.0.1:6379> HEXPIRE session:9 60 FIELDS 1 token1) (integer) 1127.0.0.1:6379> HPERSIST session:9 FIELDS 3 token user nope1) (integer) 12) (integer) -13) (integer) -2127.0.0.1:6379> HTTL session:9 FIELDS 1 token1) (integer) -1Compatibility
Section titled “Compatibility”Same as Redis 7.4. Valkey 8 does not have hash field expiration.
See also
Section titled “See also”Was this page helpful?
Thanks for the feedback.