HIMPORT DISCARD
Removes a single session-local fieldset by name.
Browse all commands · Upstream source documentation
| Reference field | Value |
|---|---|
| Canonical name | HIMPORT DISCARD |
| 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”HIMPORT DISCARD fieldset-nameffkv 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 session-local fieldsets.
Upstream arity: 3 (includes the command name; a negative number is a minimum).
ACL categories: HASH.
Command tips: REQUEST_POLICY:ALL_SHARDS.
Argument structure
Section titled “Argument structure”| Argument | Type | Constraints / metadata |
|---|---|---|
fieldset-name | string | Required |
Additional pinned upstream metadata
{ "group": "hash", "since": "8.10.0"}Metadata source · Local snapshot: src/command_metadata.json, key himport|discard.
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.
- Discarding session definitions never removes imported hashes —
tests/bdd/features/hashes.feature:984; command tag and invocation observed. - Discarded transactions never discard prepared definitions —
tests/bdd/features/hashes.feature:1229; command tag and 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.
Discarding session definitions never removes imported hashes — tests/bdd/features/hashes.feature:990 (I execute:)
[ "HIMPORT", "DISCARD", "one"]Next source assertion: the reply equals:
1Discarded transactions never discard prepared definitions — tests/bdd/features/hashes.feature:1231 (the following commands succeed:)
[ "HIMPORT", "DISCARD", "layout"]