HIMPORT
A container for session-based hash import commands using fieldsets.
Browse all commands · Upstream source documentation
| Reference field | Value |
|---|---|
| Canonical name | HIMPORT |
| Catalog group | Hash commands |
| Upstream since | 8.10.0 — upstream Redis/module version, not an ffkv release |
| Pinned catalog | Redis 8.10.0 |
Syntax
Section titled “Syntax”HIMPORTffkv 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: Depends on subcommand.
Upstream arity: -2 (includes the command name; a negative number is a minimum).
ACL categories: HASH.
Additional pinned upstream metadata
{ "group": "hash", "since": "8.10.0"}Metadata source · Local snapshot: src/command_metadata.json, key himport.
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.
- Prepared layouts preserve declared field order and replace complete hashes —
tests/bdd/features/hashes.feature:877; command tag.
Scenario tags are present, but no safely parsed JSON command vector was extracted. Consult the named feature source for fixture-driven or parameterized execution; no executable example is invented here.