PFMERGE

Merges one or more HyperLogLog values into a single key.

Browse all commands · Upstream source documentation

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

Syntax

PFMERGE destkey [sourcekey [sourcekey ...]]

ffkv behavior and limits

Cardinality is approximate. ffkv uses Redis-compatible HYLL registers and unions; this does not establish compatibility for every arbitrary or corrupted upstream dump.

Source: README.md:288; src/engine/hyperloglog.rs; tests/bdd/features/hyperloglog.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) to merge N HyperLogLogs, but with high constant times.

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

Command flags: WRITE, DENYOOM.

ACL categories: HYPERLOGLOG.

Argument structure

Argument	Type	Constraints / metadata
destkey	key	key_spec_index: 0
sourcekey	key	optional; multiple; key_spec_index: 1

Key specifications

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

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

Additional pinned upstream metadata

{
  "group": "hyperloglog",
  "since": "2.8.9"
}

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

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.

• Union deduplicates overlapping input and supports destination aliases — tests/bdd/features/hyperloglog.feature:89; command tag and invocation observed.
• PFMERGE rejects invalid HYLL without mutating existing values — tests/bdd/features/hyperloglog.feature:352; command tag and invocation observed.
• Sketch merges and cache refresh retain expiry and survive recovery — tests/bdd/features/hyperloglog.feature:436; 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.

Union deduplicates overlapping input and supports destination aliases — tests/bdd/features/hyperloglog.feature:119 (I execute:)

[
  "PFMERGE",
  "a"
]

Next source assertion: the reply equals:

"OK"

Sketch merges and cache refresh retain expiry and survive recovery — tests/bdd/features/hyperloglog.feature:442 (I execute:)

[
  "PFMERGE",
  "a",
  "b"
]

Next source assertion: the reply equals:

"OK"

PFMERGE rejects invalid HYLL without mutating existing values — tests/bdd/features/hyperloglog.feature:358 (I execute:)

[
  "PFMERGE",
  "dest",
  "missing",
  "bad"
]

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