TYPE

Determines the type of value stored at a key.

Browse all commands · Upstream source documentation

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

Syntax

TYPE key

ffkv behavior and limits

TTL deadlines use wall-clock time and remain absolute across restart. Key/database operations can overwrite or remove data; SCAN is incremental rather than an atomic snapshot. New typed structures remain in RAM in hybrid mode.

Source: README.md:193–195, 375–377, 584–585; tests/bdd/features/generic.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(1)

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

Command flags: READONLY, FAST.

ACL categories: KEYSPACE.

Argument structure

Argument	Type	Constraints / metadata
key	key	key_spec_index: 0

Key specifications

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

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

Additional pinned upstream metadata

{
  "group": "generic",
  "since": "1.0.0"
}

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

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.

• Object representation metadata describes a live value and is absent for nonexistent keys — tests/bdd/features/generic.feature:852; invocation observed.
• Read only sorting resolves external keys and leaves an expiring set unchanged — tests/bdd/features/generic.feature:1304; invocation observed.
• Type distinguishes built in values and missing keys without inspecting their contents — tests/bdd/features/generic.feature:1352; command tag and invocation observed.
• Recovery retains intentionally unindexed initial data and metadata namespaces — tests/bdd/features/search.feature:944; 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.

Read only sorting resolves external keys and leaves an expiring set unchanged — tests/bdd/features/generic.feature:1326 (I execute:)

[
  "TYPE",
  "ids"
]

Next source assertion: the reply equals:

"set"

Type distinguishes built in values and missing keys without inspecting their contents — tests/bdd/features/generic.feature:1382 (I execute:)

[
  "TYPE",
  "set"
]

Next source assertion: the reply equals:

"set"

Recovery retains intentionally unindexed initial data and metadata namespaces — tests/bdd/features/search.feature:975 (I execute:)

[
  "TYPE",
  "idx"
]

Next source assertion: the reply equals:

"none"