Upstash Documentation

HPEXPIREAT

Set field expiry as ms timestamp.
2 min read

Use HPEXPIREAT to schedule individual hash fields for deletion at a fixed point in time, given as a Unix timestamp in milliseconds.

It combines the absolute deadline of HEXPIREAT with millisecond precision, which is what you need when fields spread over several hashes have to expire at exactly the same instant. A timestamp in the past removes the fields right away, and the key is deleted when its last field expires.

FIELDS <numfields> introduces the field list and the count must match. The optional condition applies the deadline only when the field has no expiration (NX), already has one (XX), or when the new deadline is later (GT) or earlier (LT) than the current one. The reply holds one status code per field: 1 when set, 0 when the condition prevented it, 2 when the field was deleted immediately, and -2 when it does not exist.

Syntax#

Arguments#

ArgumentRequiredRepeatableDescription
<key>YesNoRedis key targeted by the command.
<unix-time-milliseconds>YesNoExpiration time as a Unix timestamp in milliseconds.
(NX | XX | GT | LT)NoNoChoose one form: NX (only when the field has no expiration); XX (only when the field already has one); GT (only when the new expiration is later than the current one); LT (only when it is earlier).
FIELDS <numfields> <field> [<field> ...]YesNoFields to target. Give the field count first, then that many field names.

Important points#

  • NX cannot be combined with XX, GT, or LT, and GT and LT cannot be used together.
  • A field with no expiration counts as an infinite one, so GT never sets an expiration on such a field and LT always does.

Response#

The reply reports the result of the operation. Error replies have the same shape in RESP2 and RESP3 and are surfaced as exceptions by the SDKs below.

ProtocolReply
RESP2Array of integer status codes, one per field
RESP3Array of integer status codes, one per field
Note

Client libraries often decode bulk strings, maps, sets, and numeric strings into language-native values. The table describes the Redis wire reply.

Examples#

TCP examples use the TLS REDIS_URL from the Upstash console. REST examples use UPSTASH_REDIS_REST_URL and UPSTASH_REDIS_REST_TOKEN.

Redis CLI
@upstash/redis
upstash_redis
ioredis
node-redis
redis-py
go-redis
jedis
redis-rs