HGETDEL

Returns the value of a field and deletes it from the hash.

Browse all commands · Upstream source documentation

Reference field	Value
Canonical name	HGETDEL
Catalog group	Hash commands
Upstream since	8.0.0 — upstream Redis/module version, not an ffkv release
Pinned catalog	Redis 8.10.0

Syntax

HGETDEL key FIELDS numfields field [field ...]

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

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: -5 (includes the command name; a negative number is a minimum).

Command flags: WRITE, FAST.

ACL categories: HASH.

Argument structure

Argument	Type	Constraints / metadata
key	key	key_spec_index: 0
fields	block	token: FIELDS
↳ numfields	integer	Required
↳ field	string	multiple

Key specifications

Upstream key discovery descriptors (indexes are relative to the full command vector):

[
  {
    "flags": [
      "RW",
      "ACCESS",
      "DELETE"
    ],
    "begin_search": {
      "index": {
        "pos": 1
      }
    },
    "find_keys": {
      "range": {
        "lastkey": 0,
        "step": 1,
        "limit": 0
      }
    }
  }
]

Additional pinned upstream metadata

{
  "group": "hash",
  "since": "8.0.0",
  "history": []
}

Metadata source · Local snapshot: src/command_metadata.json, key hgetdel.

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.

• Get-and-delete processes duplicate fields in order and deletes the last-field key — tests/bdd/features/hashes.feature:319; command tag and invocation observed.
• Malformed field blocks never consume values — tests/bdd/features/hashes.feature:404; command tag and invocation observed.
• Hash operations reject incompatible key types — tests/bdd/features/hashes.feature:816; command tag and invocation observed.
• Hash mutations and field deadlines survive crash recovery — tests/bdd/features/hashes.feature:852; command tag and invocation observed.
• Existing type errors precede malformed field and expiry options — tests/bdd/features/hashes.feature:1376; command tag and invocation observed.

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.

Get-and-delete processes duplicate fields in order and deletes the last-field key — tests/bdd/features/hashes.feature:325 (I execute:)

[
  "HGETDEL",
  "h",
  "FIELDS",
  "4",
  "a",
  "a",
  "missing",
  "b"
]

Next source assertion: the reply equals:

["one",null,null,"two"]

Hash mutations and field deadlines survive crash recovery — tests/bdd/features/hashes.feature:854 (the following commands succeed:)

[
  "HGETDEL",
  "h",
  "FIELDS",
  "1",
  "b"
]

Malformed field blocks never consume values — tests/bdd/features/hashes.feature:410 (I execute:)

[
  "HGETDEL",
  "h",
  "FIELDS",
  "2",
  "a"
]

Next source assertion: the reply is an error with code “ERR”