MSETEX

Atomically sets multiple string keys with a shared expiration in a single operation.

Browse all commands · Upstream source documentation

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

Syntax

MSETEX numkeys key value [key value ...] [NX | XX] [EX seconds |
  PX milliseconds | EXAT unix-time-seconds |
  PXAT unix-time-milliseconds | KEEPTTL]

ffkv behavior and limits

Keys and values are binary-safe bytes. Conditional SET and DELEX comparisons use the stored bytes; DIGEST uses XXH3, not a cryptographic digest.

Source: README.md:571–585; src/engine/strings.rs; tests/bdd/features/strings.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 keys to set.

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

Command flags: WRITE, DENYOOM.

ACL categories: STRING.

Command tips: REQUEST_POLICY:MULTI_SHARD, RESPONSE_POLICY:ALL_SUCCEEDED.

Argument structure

Argument	Type	Constraints / metadata
numkeys	integer	Required
data	block	multiple
↳ key	key	key_spec_index: 0
↳ value	string	Required
condition	oneof	optional
↳ nx	pure-token	token: NX
↳ xx	pure-token	token: XX
expiration	oneof	optional
↳ seconds	integer	token: EX
↳ milliseconds	integer	token: PX
↳ unix-time-seconds	unix-time	token: EXAT
↳ unix-time-milliseconds	unix-time	token: PXAT
↳ keepttl	pure-token	token: KEEPTTL

Key specifications

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

[
  {
    "flags": [
      "OW",
      "UPDATE"
    ],
    "begin_search": {
      "index": {
        "pos": 1
      }
    },
    "find_keys": {
      "keynum": {
        "keynumidx": 0,
        "firstkey": 1,
        "step": 2
      }
    }
  }
]

Additional pinned upstream metadata

{
  "group": "string",
  "since": "8.4.0"
}

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

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.

• Counted multi set evaluates NX atomically and shares one expiration — tests/bdd/features/strings.feature:665; command tag and invocation observed.
• Resolved multi string writes survive crash recovery with their expiration — tests/bdd/features/strings.feature:1043; command tag and invocation observed.
• Counted setters handle aliases before mutation and past absolute deadlines — tests/bdd/features/strings.feature:1178; 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.

Counted multi set evaluates NX atomically and shares one expiration — tests/bdd/features/strings.feature:735 (I execute:)

[
  "MSETEX",
  "2",
  "first",
  "x",
  "second",
  "y",
  "XX",
  "KEEPTTL"
]

Next source assertion: the reply equals:

1

Counted setters handle aliases before mutation and past absolute deadlines — tests/bdd/features/strings.feature:1225 (I execute:)

[
  "MSETEX",
  "2",
  "alias",
  "gone",
  "other",
  "gone",
  "PXAT",
  "1"
]

Next source assertion: the reply equals:

1

Resolved multi string writes survive crash recovery with their expiration — tests/bdd/features/strings.feature:1045 (the following commands succeed:)

[
  "MSETEX",
  "3",
  "counter",
  "99",
  "delete-me",
  "old",
  "float",
  "1.5",
  "PXAT",
  "4102444800000"
]