ZINCRBY

Increments the score of a member in a sorted set.

Browse all commands · Upstream source documentation

Reference field	Value
Canonical name	ZINCRBY
Catalog group	Sorted set commands
Upstream since	1.2.0 — upstream Redis/module version, not an ffkv release
Pinned catalog	Redis 8.10.0

Syntax

ZINCRBY key increment member

ffkv behavior and limits

Scores and lexicographic ranges are separate query modes. Do not rely on random-pop order; sorted-set storage remains RAM-resident in hybrid mode.

Source: README.md:275–295, 810–825; tests/bdd/features/sorted_sets.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(log(N)) where N is the number of elements in the sorted set.

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

Command flags: WRITE, DENYOOM, FAST.

ACL categories: SORTEDSET.

Argument structure

Argument	Type	Constraints / metadata
key	key	key_spec_index: 0
increment	integer	Required
member	string	Required

Key specifications

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

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

Additional pinned upstream metadata

{
  "group": "sorted_set",
  "since": "1.2.0"
}

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

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.

• Increment returns its resolved score and rejects NaN without mutation — tests/bdd/features/sorted_sets.feature:92; 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.

Increment returns its resolved score and rejects NaN without mutation — tests/bdd/features/sorted_sets.feature:111 (I execute:)

[
  "ZINCRBY",
  "ranked",
  "2.5",
  "b"
]

Next source assertion: the reply equals:

"2.5"

Increment returns its resolved score and rejects NaN without mutation — tests/bdd/features/sorted_sets.feature:98 (I execute:)

[
  "ZINCRBY",
  "ranked",
  "-inf",
  "a"
]

Next source assertion: the reply is an error with code “ERR”