LMOVEM

Moves up to (or exactly) a number of elements from one list to another and returns them. Deletes the source list if it becomes empty.

Browse all commands · Upstream source documentation

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

Syntax

LMOVEM source destination <LEFT | RIGHT> <LEFT | RIGHT>
  [<COUNT count | EXACTLY exactly> <OBO | BULK>]

ffkv behavior and limits

A successful pop removes the item immediately: Redis list queues have no acknowledgement or automatic redelivery. Blocking calls do not wait in EXEC or Lua. Only large list/native-job bodies are SSD-offloaded in hybrid mode.

Source: README.md:155–174, 810–825; tests/bdd/features/lists.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) where N is the number of elements moved.

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

Command flags: WRITE, DENYOOM.

ACL categories: LIST.

Argument structure

Argument	Type	Constraints / metadata
source	key	key_spec_index: 0
destination	key	key_spec_index: 1
wherefrom	oneof	Required
↳ left	pure-token	token: LEFT
↳ right	pure-token	token: RIGHT
whereto	oneof	Required
↳ left	pure-token	token: LEFT
↳ right	pure-token	token: RIGHT
how-many	block	optional
↳ selector	oneof	Required
↳ ↳ count	integer	token: COUNT
↳ ↳ exactly	integer	token: EXACTLY
↳ ordering	oneof	Required
↳ ↳ obo	pure-token	token: OBO
↳ ↳ bulk	pure-token	token: BULK

Key specifications

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

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

Additional pinned upstream metadata

{
  "group": "list",
  "since": "8.10.0"
}

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

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.

• Destination type errors cannot consume the source (Scenario Outline) — tests/bdd/features/lists.feature:494; command tag and invocation observed.
• Batch movement returns destination order for all endpoints and modes (Scenario Outline) — tests/bdd/features/lists.feature:520; command tag and invocation observed.
• Same-key batch selection happens before any push back (Scenario Outline) — tests/bdd/features/lists.feature:554; command tag and invocation observed.
• Exactly is all-or-nothing and count bounds the available source — tests/bdd/features/lists.feature:586; command tag and invocation observed.
• Resolved insertion and batch movement recover with ordering and binary values intact — tests/bdd/features/lists.feature:882; command tag and invocation observed.
• RESP3 keeps nested pop arrays, destination-order move arrays, and missing positions distinct — tests/bdd/features/lists.feature:1009; command tag and invocation observed.
• List commands reject incompatible source values without replacing them (Scenario Outline) — tests/bdd/features/lists.feature:1047; 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.

Exactly is all-or-nothing and count bounds the available source — tests/bdd/features/lists.feature:621 (I execute:)

[
  "LMOVEM",
  "missing",
  "destination",
  "LEFT",
  "RIGHT"
]

Next source assertion: the reply equals:

[]

Same-key batch selection happens before any push back — tests/bdd/features/lists.feature:560 (I execute:)

Expanded from an actual Examples row: from=LEFT, to=LEFT, mode=OBO, moved=["b","a"], remaining=["b","a","c","d"].

[
  "LMOVEM",
  "q",
  "q",
  "LEFT",
  "LEFT",
  "EXACTLY",
  "2",
  "OBO"
]

Next source assertion: the reply equals:

["b","a"]

Batch movement returns destination order for all endpoints and modes — tests/bdd/features/lists.feature:526 (I execute:)

Expanded from an actual Examples row: from=LEFT, to=LEFT, mode=OBO, moved=["b","a"], destination=["b","a","x"].

[
  "LMOVEM",
  "source",
  "destination",
  "LEFT",
  "LEFT",
  "COUNT",
  "2",
  "OBO"
]

Next source assertion: the reply equals:

["b","a"]