HEXPIREAT
Set expiry for hash field using an absolute Unix timestamp (seconds)
Browse all commands · Upstream source documentation
| Reference field | Value |
|---|---|
| Canonical name | HEXPIREAT |
| Catalog group | Hash commands |
| Upstream since | 7.4.0 — upstream Redis/module version, not an ffkv release |
| Pinned catalog | Redis 8.10.0 |
Syntax
Section titled “Syntax”HEXPIREAT key unix-time-seconds [NX | XX | GT | LT] FIELDS numfields field [field ...]ffkv behavior and limits
Section titled “ffkv behavior and limits”Hash fields have independent expiration. Counted field forms use FIELDS n; HSETEX counts field/value pairs. Key TTL and field TTL are distinct.
Source: README.md:587–599; tests/bdd/features/hashes.feature.
All requests share the 8 MiB framing/1,024-argument ingress limit; normal RESP replies have 64 MiB wire/logical budgets with bounded nesting/value counts. Management and Lua origins impose smaller budgets. These are not a process RSS cap. Catalog inclusion is not exhaustive option or wire-format parity. See limits and compatibility.
Upstream metadata
Section titled “Upstream metadata”The following fields come from the pinned Redis metadata, not measured ffkv performance or an assertion that ffkv enforces every upstream flag. Running COMMAND INFO/COMMAND DOCS describe the current engine.
Upstream Redis complexity: O(N) where N is the number of specified fields
Upstream arity: -6 (includes the command name; a negative number is a minimum).
Command flags: WRITE, FAST.
ACL categories: HASH.
Argument structure
Section titled “Argument structure”| Argument | Type | Constraints / metadata |
|---|---|---|
key | key | key_spec_index: 0 |
unix-time-seconds | unix-time | Required |
condition | oneof | optional |
↳ nx | pure-token | token: NX |
↳ xx | pure-token | token: XX |
↳ gt | pure-token | token: GT |
↳ lt | pure-token | token: LT |
fields | block | token: FIELDS |
↳ numfields | integer | Required |
↳ field | string | multiple |
Key specifications
Section titled “Key specifications”Upstream key discovery descriptors (indexes are relative to the full command vector):
[ { "flags": [ "RW", "UPDATE" ], "begin_search": { "index": { "pos": 1 } }, "find_keys": { "range": { "lastkey": 0, "step": 1, "limit": 0 } } }]Additional pinned upstream metadata
{ "group": "hash", "since": "7.4.0", "history": []}Metadata source · Local snapshot: src/command_metadata.json, key hexpireat.
BDD coverage and source examples
Section titled “BDD coverage and source examples”These are source observations, not a test run performed by this documentation build. A tag identifies scenario intent; an extracted vector identifies a command invocation, which may intentionally produce an error. Scenarios may require setup, multiple connections, persistence, cluster nodes or native-module fixtures.
- HEXPIREAT exposes absolute deadlines and independent conditional outcomes —
tests/bdd/features/hashes.feature:566; command tag and invocation observed. - Expiry conditions may follow counted fields and mixed conditions fail atomically —
tests/bdd/features/hashes.feature:1492; command tag and invocation observed. - Rename expiration deletion and type replacement do not leave stale postings —
tests/bdd/features/search.feature:904; invocation observed.
Extracted command vectors
Section titled “Extracted command vectors”The following JSON arrays are the test harness’s argument vectors, not shell commands. Numeric arguments are converted by the harness; objects of the form {"base64":"…"} represent decoded binary bytes, not a literal JSON command argument. Preserve scenario setup and connection ordering. See the CLI guide for shell quoting and binary stdin. No reply is invented or inferred.
HEXPIREAT exposes absolute deadlines and independent conditional outcomes — tests/bdd/features/hashes.feature:596 (I execute:)
[ "HEXPIREAT", "h", "1", "LT", "FIELDS", "1", "a"]Next source assertion: the reply equals:
[2]Expiry conditions may follow counted fields and mixed conditions fail atomically — tests/bdd/features/hashes.feature:1514 (I execute:)
[ "HEXPIREAT", "h", "4102444800", "FIELDS", "1", "b", "GT"]Next source assertion: the reply equals:
[1]Rename expiration deletion and type replacement do not leave stale postings — tests/bdd/features/search.feature:906 (the following commands succeed:)
[ "HEXPIREAT", "doc:2", 1, "FIELDS", 1, "tag"]