What's new in Valkey 9.0? Discover new features and improvements. Read the announcement.

HPERSIST

Remove the existing expiration on a hash key's field(s).

Usage
HPERSIST key FIELDS fields
Complexity
O(N) where N is the number of specified fields.
Since
9.0.0
ACL Categories
@fast, @hash, @write
Command flags
WRITE, FAST

The HPERSIST remove the existing expiration on a hash key's field(s), turning the field(s) from volatile (a field with expiration set) to persistent (a field that will never expire as no TTL (time to live) is associated).

Examples

127.0.0.1:6379> HSET myhash f1 v1 f2 v2 f3 v3
(integer) 3
27.0.0.1:6379> HEXPIRE myhash 1000 FIELDS 2 f2 f3
1) (integer) 1
2) (integer) 1
127.0.0.1:6379> HTTL myhash FIELDS 3 f1 f2 f3
1) (integer) -1
2) (integer) 998
3) (integer) 998
127.0.0.1:6379> HPERSIST myhash FIELDS 3 f1 f2 f3
1) (integer) -1
2) (integer) 1
3) (integer) 1
127.0.0.1:6379> HTTL myhash FIELDS 3 f1 f2 f3
1) (integer) -1
2) (integer) -1
3) (integer) -1

Replies

RESP2

Array reply: a list of integer codes indicating the result of setting expiry on each specified field, in the same order as the fields are requested.

  • -2: Field does not exist in the provided hash key, or the hash key does not exist.
  • -1: Field exists in the provided hash key, but has no expiration associated with it.
  • 1: The expiration time was removed from the hash key field.

RESP3

Array reply: a list of integer codes indicating the result of setting expiry on each specified field, in the same order as the fields are requested.

  • -2: Field does not exist in the provided hash key, or the hash key does not exist.
  • -1: Field exists in the provided hash key, but has no expiration associated with it.
  • 1: The expiration time was removed from the hash key field.