HIMPORT SET

Creates a fieldset-based hash from values supplied in the order matching a previously prepared fieldset.

Browse all commands · Upstream source documentation

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

Syntax

HIMPORT SET key fieldset-name value [value ...]

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 fields in the fieldset.

Upstream arity: -5 (includes the command name; a negative number is a minimum).

Command flags: WRITE, DENYOOM.

ACL categories: HASH.

Argument structure

Argument	Type	Constraints / metadata
key	key	key_spec_index: 0
fieldset-name	string	Required
value	string	multiple

Key specifications

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

[
  {
    "flags": [
      "OW",
      "UPDATE"
    ],
    "begin_search": {
      "index": {
        "pos": 2
      }
    },
    "find_keys": {
      "range": {
        "lastkey": 0,
        "step": 1,
        "limit": 0
      }
    }
  }
]

Additional pinned upstream metadata

{
  "group": "hash",
  "since": "8.10.0"
}

Metadata source · Local snapshot: src/command_metadata.json, key himport|set.

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.

• Prepared layouts preserve declared field order and replace complete hashes — tests/bdd/features/hashes.feature:877; command tag and invocation observed.
• Duplicate layout preparation and mismatched imports preserve old state — tests/bdd/features/hashes.feature:934; command tag and invocation observed.
• Discarding session definitions never removes imported hashes — tests/bdd/features/hashes.feature:984; invocation observed.
• Non-hash target type takes precedence over missing definitions — tests/bdd/features/hashes.feature:1042; command tag and invocation observed.
• Replacing layout definitions affects only future imports — tests/bdd/features/hashes.feature:1076; command tag and invocation observed.
• Import layouts are isolated per connection — tests/bdd/features/hashes.feature:1117; command tag and invocation observed.
• Reset forgets definitions without changing imported hashes — tests/bdd/features/hashes.feature:1146; command tag and invocation observed.
• Imported values survive recovery without resurrecting session definitions — tests/bdd/features/hashes.feature:1175; command tag and invocation observed.
• Transactions apply session imports in execution order — tests/bdd/features/hashes.feature:1197; command tag and invocation observed.
• Discarded transactions never discard prepared definitions — tests/bdd/features/hashes.feature:1229; invocation observed.
• Scripts use invocation-local layouts rather than the network session — tests/bdd/features/hashes.feature:1253; command tag and invocation observed.
• Import names fields and values are binary safe — tests/bdd/features/hashes.feature:1287; command tag and invocation observed.
• Each outer Lua invocation owns a fresh import session rather than borrowing network layouts — tests/bdd/features/scripting.feature:623; 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.

Import layouts are isolated per connection — tests/bdd/features/hashes.feature:1128 (I execute:)

[
  "HIMPORT",
  "SET",
  "h",
  "layout",
  "value"
]

Next source assertion: the reply equals:

"OK"

Transactions apply session imports in execution order — tests/bdd/features/hashes.feature:1219 (I execute:)

[
  "HIMPORT",
  "SET",
  "next",
  "layout",
  "second"
]

Next source assertion: the reply equals:

"OK"

Replacing layout definitions affects only future imports — tests/bdd/features/hashes.feature:1091 (I execute:)

[
  "HIMPORT",
  "SET",
  "after",
  "layout",
  "updated"
]

Next source assertion: the reply equals:

"OK"