TS.RANGE

Query a range in forward direction

Browse all commands · Upstream source documentation

Reference field	Value
Canonical name	TS.RANGE
Catalog group	Time series commands
Upstream since	1.0.0 — upstream Redis/module version, not an ffkv release
Pinned catalog	Redis 8.10.0

Syntax

TS.RANGE key fromTimestamp toTimestamp [LATEST]
  [FILTER BY TS Timestamp [Timestamp ...]] [FILTER BY VALUE min max]
  [COUNT count] [[ALIGN value] AGGREGATION aggregators bucketDuration [BUCKETTIMESTAMP] [EMPTY]]

ffkv behavior and limits

Time-series chunks, retention, labels and live compaction rules are implemented in RAM. TS.READ BLOCK uses bounded actor waiters and is rejected in EXEC/Lua; other reads may be used without blocking. Hybrid does not offload time-series chunks.

Source: README.md:294, 351–353, 375–377; tests/bdd/features/timeseries.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.

• Explicit retention and duplicate policies govern updates and pruning — tests/bdd/features/timeseries.feature:5; invocation observed.
• Counter deltas and inclusive deletion retain the correct remaining samples — tests/bdd/features/timeseries.feature:116; invocation observed.
• Range order filters and multi-aggregator statistics follow sample values — tests/bdd/features/timeseries.feature:172; command tag and invocation observed.
• NaN samples remain visible while aggregation counts distinguish missing numbers — tests/bdd/features/timeseries.feature:212; invocation observed.
• Compaction exposes closed and open buckets and deleting its rule stops future output — tests/bdd/features/timeseries.feature:244; invocation observed.
• Time-weighted aggregation of a constant signal preserves its measured level — tests/bdd/features/timeseries.feature:440; invocation observed.
• Deleting the latest source bucket durably reopens the previous compaction bucket — tests/bdd/features/timeseries.feature:457; command tag and invocation observed.
• Deleting every source sample resets compaction before earlier timestamps are reinserted — tests/bdd/features/timeseries.feature:519; 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.

Deleting the latest source bucket durably reopens the previous compaction bucket — tests/bdd/features/timeseries.feature:472 (client “ts3” executes:)

[
  "TS.RANGE",
  "avg",
  "-",
  "+"
]

Next source assertion: the reply equals:

[]

NaN samples remain visible while aggregation counts distinguish missing numbers — tests/bdd/features/timeseries.feature:219 (client “ts3” executes:)

[
  "TS.RANGE",
  "sensor",
  10,
  20
]

Next source assertion: the reply equals:

[[10,{"$approx":2}],[20,{"type":"double","value":"nan"}]]

Explicit retention and duplicate policies govern updates and pruning — tests/bdd/features/timeseries.feature:69 (client “ts3” executes:)

[
  "TS.RANGE",
  "sensor",
  "-",
  "+"
]

Next source assertion: the reply equals:

[[1101,{"$approx":8}]]