FT.CONFIG GET

Retrieves runtime configuration options

Browse all commands · Upstream source documentation

Reference field	Value
Canonical name	FT.CONFIG GET
Catalog group	Search commands
Upstream since	1.0.0 — upstream Redis/module version, not an ffkv release
Pinned catalog	Redis 8.10.0

Syntax

FT.CONFIG GET option

ffkv behavior and limits

Search worker configuration controls a real Rayon pool; GC schedules generation-fenced Rust compaction, not a POSIX fork. Search indexes and documents are bounded and RAM-resident; upstream syntax is not a promise of every option combination or Redis module ABI parity.

Source: README.md:375–377, 636–642; src/engine/search/; tests/bdd/features/search.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.

Metadata availability

This command is in the canonical catalog but has no matching entry in the pinned src/command_metadata.json. Argument flags, complexity and key specifications are not invented. Use the syntax, upstream source documentation and actual scenario evidence below.

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.

• Runtime configuration round trips and invalid changes are atomic — tests/bdd/features/search.feature:284; command tag and invocation observed.
• Search worker reconfiguration preserves queries and enforces strict timeout prerequisites — tests/bdd/features/search.feature:1246; invocation observed.
• Collector scheduling controls retain their values and reject invalid intervals — tests/bdd/features/search.feature:1287; 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.

Runtime configuration round trips and invalid changes are atomic — tests/bdd/features/search.feature:290 (I execute:)

[
  "FT.CONFIG",
  "GET",
  "TIMEOUT"
]

Next source assertion: the reply equals:

[["TIMEOUT","1000"]]

Search worker reconfiguration preserves queries and enforces strict timeout prerequisites — tests/bdd/features/search.feature:1265 (I execute:)

[
  "FT.CONFIG",
  "GET",
  "WORKERS"
]

Next source assertion: the reply equals:

[["WORKERS","2"]]

Collector scheduling controls retain their values and reject invalid intervals — tests/bdd/features/search.feature:1306 (I execute:)

[
  "FT.CONFIG",
  "GET",
  "FORK_GC_RUN_INTERVAL"
]

Next source assertion: the reply equals:

[["FORK_GC_RUN_INTERVAL","1"]]