HPEXPIRETIME(3valkey)

📦 version 9.0.6, in fedora 44

💖 HPEXPIRETIME 💖

ok so this is hpexpiretime, straight out of the Valkey Command Manual (section 3valkey, iykyk), and bestie it is SO useful. It tells you the exact Unix timestamp in milliseconds since the Unix epoch at which a given key's field(s) are gonna expire. like a lil countdown but make it absolute. 🕰️✨

✨ NAME ✨

hpexpiretime — returns the Unix timestamp in milliseconds since Unix epoch at which the given key's field(s) will expire 🌸

🎀 SYNOPSIS 🎀

HPEXPIRETIME key FIELDS numfields field [field...]

🦋 DESCRIPTION 🦋

The HPEXPIRETIME command returns the absolute Unix timestamp (since January 1, 1970) in milliseconds at which the given hash field(s) will expire. no cap, absolute — not "in 300 seconds", it's giving "this is the literal moment, put it in your calendar". 💅

Also peep the valkey-hexpiretime(7) HEXPIRETIME command, which hands you the exact same info but with seconds resolution instead of milliseconds. same vibe, chiller precision. ✨

💜 REPLY 💜

valkey-protocol(7) Array reply: a list of values associated with the result of getting the absolute expiry timestamp of the specific fields, in the same order as they are requested. order matters bestie, it always does. 👑

  • -2: Field does not exist in the provided hash key, or the hash key is empty. 💀
  • -1: Field exists in the provided hash key, but has no expiration associated with it. 🙈
  • valkey-protocol(7) Integer: The expiration time associated with the hash key field, in milliseconds. ⭐

🔥 COMPLEXITY 🔥

O(N) where N is the number of specified fields. the more fields you ask about, the more work it does, that's just math. 🧚

🌈 ACL CATEGORIES 🌈

@fast @hash @read — she's fast, she's hashy, she's read-only, she's iconic. 👑

🌸 HISTORY 🌸

  • Available since: 9.0.0 🎀

💅 EXAMPLES 💅

127.0.0.1:6379> HSET myhash f1 v1 f2 v2 f3 v3
(integer) 3
27.0.0.1:6379> HPEXPIREAT myhash 1754847944000 FIELDS 2 f2 f3
1) (integer) 1
2) (integer) 1
127.0.0.1:6379> HPEXPIRETIME myhash FIELDS 4 f1 f2 f3 non-exist
1) (integer) -1
2) (integer) 1754847944000
3) (integer) 1754847944000
4) (integer) -2

look at that. f1 said "no expiration, I'm free" (-1), f2 and f3 are locked in till 1754847944000, and non-exist is just... not there (-2). main character behavior from non-exist honestly. 💀✨

🫶 SEE ALSO 🫶

hdel(3valkey), hexists(3valkey), hexpire(3valkey), hexpireat(3valkey), hexpiretime(3valkey), hget(3valkey), hgetall(3valkey), hgetex(3valkey), hincrby(3valkey), hincrbyfloat(3valkey), hkeys(3valkey), hlen(3valkey), hmget(3valkey), hmset(3valkey), hpersist(3valkey), hpexpire(3valkey), hpexpireat(3valkey), hpttl(3valkey), hrandfield(3valkey), hscan(3valkey), hset(3valkey), hsetex(3valkey), hsetnx(3valkey), hstrlen(3valkey), httl(3valkey), hvals(3valkey) — the whole friend group, go say hi. 💖

ok that's the whole page bestie, no skips, no cuts, every flag and number kept exactly where it was. 🫶

version 9.0.0, dated 2025-10-21 — mwah, that's a wrap, slay the day and go check ur field expiries. 💅✨🎀

📦 where this page comes from