HPEXPIRETIME
HPEXPIRETIME 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
- read-only, fast
- Keys
- first 1, last 1, step 1
- HotKV Cloud
- All plans
- On-Premise
- no license needed
HPEXPIRETIME works like HEXPIRETIME, but returns
each field’s expiry as a Unix timestamp in milliseconds.
Return value
Section titled “Return value”An array with one integer per field, in the order given, under both RESP2 and RESP3:
| Value | Meaning |
|---|---|
-2 |
The field or the key does not exist. |
-1 |
The field exists but has no expiry. |
| Positive integer | The expiry as a Unix time in milliseconds. |
The errors are the same as for HTTL.
Examples
Section titled “Examples”127.0.0.1:6379> HSET promo:3 code "SPRING"(integer) 1127.0.0.1:6379> HPEXPIREAT promo:3 1924992000500 FIELDS 1 code1) (integer) 1127.0.0.1:6379> HPEXPIRETIME promo:3 FIELDS 1 code1) (integer) 1924992000500Compatibility
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.