BITOP

Performs bitwise operations on multiple strings, and stores the result.

Browse all commands · Upstream source documentation

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

Syntax

BITOP <AND | OR | XOR | NOT | DIFF | DIFF1 | ANDOR | ONE> destkey key [key ...]

ffkv behavior and limits

Bitmap/bitfield values share string key storage. Bitfield overflow policy and signedness affect arithmetic; request and reply budgets still apply.

Source: README.md:275–280, 784–797; tests/bdd/features/bitmaps.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)

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

Command flags: WRITE, DENYOOM.

ACL categories: BITMAP.

Argument structure

Argument	Type	Constraints / metadata
operation	oneof	Required
↳ and	pure-token	token: AND
↳ or	pure-token	token: OR
↳ xor	pure-token	token: XOR
↳ not	pure-token	token: NOT
↳ diff	pure-token	token: DIFF
↳ diff1	pure-token	token: DIFF1
↳ andor	pure-token	token: ANDOR
↳ one	pure-token	token: ONE
destkey	key	key_spec_index: 0
key	key	multiple; key_spec_index: 1

Key specifications

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

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

Additional pinned upstream metadata

{
  "group": "bitmap",
  "since": "2.6.0"
}

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

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.

• BITOP AND applies zero padding and its full truth table — tests/bdd/features/bitmaps.feature:237; command tag and invocation observed.
• BITOP OR applies zero padding and its full truth table — tests/bdd/features/bitmaps.feature:261; command tag and invocation observed.
• BITOP XOR applies zero padding and its full truth table — tests/bdd/features/bitmaps.feature:285; command tag and invocation observed.
• BITOP DIFF applies zero padding and its full truth table — tests/bdd/features/bitmaps.feature:309; command tag and invocation observed.
• BITOP DIFF1 applies zero padding and its full truth table — tests/bdd/features/bitmaps.feature:333; command tag and invocation observed.
• BITOP ANDOR applies zero padding and its full truth table — tests/bdd/features/bitmaps.feature:357; command tag and invocation observed.
• BITOP ONE applies zero padding and its full truth table — tests/bdd/features/bitmaps.feature:381; command tag and invocation observed.
• NOT is unary and aliases use original source data — tests/bdd/features/bitmaps.feature:405; command tag and invocation observed.
• BITOP rejects non-string inputs without mutation — tests/bdd/features/bitmaps.feature:640; 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.

NOT is unary and aliases use original source data — tests/bdd/features/bitmaps.feature:411 (I execute:)

[
  "BITOP",
  "NOT",
  "x",
  "x"
]

Next source assertion: the reply equals:

2

BITOP OR applies zero padding and its full truth table — tests/bdd/features/bitmaps.feature:267 (I execute:)

[
  "BITOP",
  "OR",
  "out",
  "x",
  "y",
  "z"
]

Next source assertion: the reply equals:

2

BITOP AND applies zero padding and its full truth table — tests/bdd/features/bitmaps.feature:243 (I execute:)

[
  "BITOP",
  "AND",
  "out",
  "x",
  "y",
  "z"
]

Next source assertion: the reply equals:

2