[ggivo]

Extend the existing tsRange/tsRevRange/tsMRange/tsMRevRange family to accept multiple aggregators in a single call, matching the new server syntax AGGREGATION agg1,agg2,…,aggN bucketDur (RedisTimeSeries 8.8).

Changes:

• TSElement: carry List<Double> values internally; existing(long, double) constructor preserved (wraps in a singleton list); getValue() returns values.get(0) for backward compatibility; new getValues() exposes the full positional list.
• TSRangeParams / TSMRangeParams: new aggregation(AggregationType[],long) setter; Wire format is identical to the previous single-aggregator output when length == 1.
• TimeSeriesBuilderFactory.TIMESERIES_ELEMENT_LIST: parse positional [ts, v1, …, vN] samples; size-2 takes the existing single-value path, size > 2 builds a multi-value TSElement.

No new public methods on RedisTimeSeriesCommands / RedisTimeSeriesPipelineCommands

---

Note

Medium Risk
Changes the TSElement data model and time series range parameter encoding to support multi-aggregator responses, which may affect equality/hashCode semantics and downstream code that assumes a single value per sample.

Overview
Adds support for RedisTimeSeries multi-aggregator syntax (AGGREGATION a,b,c bucket) across TS.RANGE/TS.REVRANGE and TS.MRANGE/TS.MREVRANGE by allowing TSRangeParams/TSMRangeParams to accept AggregationType[] and encoding aggregators as a comma-joined token.

Updates TSElement to carry multiple values per timestamp (getValues()), while keeping getValue() returning the first value for backward compatibility, and extends response parsing to handle [ts, v1, ..., vN] samples.

Expands test coverage for wire-format validation and new multi-aggregator behaviors (including empty results) and adjusts cluster time series ITs to disable the new label-based multi-range tests; also updates pom.xml formatter includes for timeseries tests.

^{Reviewed by Cursor Bugbot for commit 23a26e9. Bugbot is set up for automated code reviews on this repo. Configure here.}

[jit-ci]

🛡️ Jit Security Scan Results

✅ No security findings were detected in this PR

---

^{Security scan by Jit}

[github-actions]

Test Results

  191 files  ± 0    191 suites  ±0   9m 44s ⏱️ -16s
7 690 tests +16  7 200 ✅  - 422  490 💤 +438  0 ❌ ±0 
7 698 runs  + 4  7 200 ✅  - 442  498 💤 +446  0 ❌ ±0 

Results for commit 23a26e9. ± Comparison against base commit a3d6d95.

This pull request removes 14 and adds 30 tests. Note that renamed tests count towards both.

redis.clients.jedis.commands.unified.search.FTHybridCommandsTestBase$SupportedScorersTest[1] ‑ testScorer(Scorer, double, double)[1][1]
redis.clients.jedis.commands.unified.search.FTHybridCommandsTestBase$SupportedScorersTest[1] ‑ testScorer(Scorer, double, double)[1][2]
redis.clients.jedis.commands.unified.search.FTHybridCommandsTestBase$SupportedScorersTest[1] ‑ testScorer(Scorer, double, double)[1][3]
redis.clients.jedis.commands.unified.search.FTHybridCommandsTestBase$SupportedScorersTest[1] ‑ testScorer(Scorer, double, double)[1][4]
redis.clients.jedis.commands.unified.search.FTHybridCommandsTestBase$SupportedScorersTest[1] ‑ testScorer(Scorer, double, double)[1][5]
redis.clients.jedis.commands.unified.search.FTHybridCommandsTestBase$SupportedScorersTest[1] ‑ testScorer(Scorer, double, double)[1][6]
redis.clients.jedis.commands.unified.search.FTHybridCommandsTestBase$SupportedScorersTest[1] ‑ testScorer(Scorer, double, double)[1][7]
redis.clients.jedis.commands.unified.search.FTHybridCommandsTestBase$SupportedScorersTest[2] ‑ testScorer(Scorer, double, double)[2][1]
redis.clients.jedis.commands.unified.search.FTHybridCommandsTestBase$SupportedScorersTest[2] ‑ testScorer(Scorer, double, double)[2][2]
redis.clients.jedis.commands.unified.search.FTHybridCommandsTestBase$SupportedScorersTest[2] ‑ testScorer(Scorer, double, double)[2][3]
…

redis.clients.jedis.commands.unified.client.timeseries.TimeSeriesRedisClientCommandsIT[1] ‑ mRangeMultipleAggregators()[1]
redis.clients.jedis.commands.unified.client.timeseries.TimeSeriesRedisClientCommandsIT[1] ‑ mRangeMultipleAggregatorsEmptyResult()[1]
redis.clients.jedis.commands.unified.client.timeseries.TimeSeriesRedisClientCommandsIT[1] ‑ mRevRangeMultipleAggregators()[1]
redis.clients.jedis.commands.unified.client.timeseries.TimeSeriesRedisClientCommandsIT[1] ‑ mRevRangeMultipleAggregatorsEmptyResult()[1]
redis.clients.jedis.commands.unified.client.timeseries.TimeSeriesRedisClientCommandsIT[1] ‑ rangeMultipleAggregators()[1]
redis.clients.jedis.commands.unified.client.timeseries.TimeSeriesRedisClientCommandsIT[1] ‑ rangeMultipleAggregatorsEmptyResult()[1]
redis.clients.jedis.commands.unified.client.timeseries.TimeSeriesRedisClientCommandsIT[1] ‑ rangeSingleAggregatorViaArraySetter()[1]
redis.clients.jedis.commands.unified.client.timeseries.TimeSeriesRedisClientCommandsIT[1] ‑ revRangeMultipleAggregators()[1]
redis.clients.jedis.commands.unified.client.timeseries.TimeSeriesRedisClientCommandsIT[1] ‑ revRangeMultipleAggregatorsEmptyResult()[1]
redis.clients.jedis.commands.unified.client.timeseries.TimeSeriesRedisClientCommandsIT[2] ‑ mRangeMultipleAggregators()[2]
…

This pull request skips 408 tests.

redis.clients.jedis.commands.commandobjects.CommandObjectsJsonCommandsTest[1] ‑ testJsonSetWithFphaParams(String, Keyword, FphaType)[1][10]
redis.clients.jedis.commands.commandobjects.CommandObjectsJsonCommandsTest[1] ‑ testJsonSetWithFphaParams(String, Keyword, FphaType)[1][11]
redis.clients.jedis.commands.commandobjects.CommandObjectsJsonCommandsTest[1] ‑ testJsonSetWithFphaParams(String, Keyword, FphaType)[1][12]
redis.clients.jedis.commands.commandobjects.CommandObjectsJsonCommandsTest[1] ‑ testJsonSetWithFphaParams(String, Keyword, FphaType)[1][1]
redis.clients.jedis.commands.commandobjects.CommandObjectsJsonCommandsTest[1] ‑ testJsonSetWithFphaParams(String, Keyword, FphaType)[1][2]
redis.clients.jedis.commands.commandobjects.CommandObjectsJsonCommandsTest[1] ‑ testJsonSetWithFphaParams(String, Keyword, FphaType)[1][3]
redis.clients.jedis.commands.commandobjects.CommandObjectsJsonCommandsTest[1] ‑ testJsonSetWithFphaParams(String, Keyword, FphaType)[1][4]
redis.clients.jedis.commands.commandobjects.CommandObjectsJsonCommandsTest[1] ‑ testJsonSetWithFphaParams(String, Keyword, FphaType)[1][5]
redis.clients.jedis.commands.commandobjects.CommandObjectsJsonCommandsTest[1] ‑ testJsonSetWithFphaParams(String, Keyword, FphaType)[1][6]
redis.clients.jedis.commands.commandobjects.CommandObjectsJsonCommandsTest[1] ‑ testJsonSetWithFphaParams(String, Keyword, FphaType)[1][7]
…

♻️ This comment has been updated with latest results.

[cursor]

Cursor Bugbot has reviewed your changes and found 1 potential issue.

^{❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, have a team admin enable autofix in the Cursor dashboard.}

^{Reviewed by Cursor Bugbot for commit e60d8a1. Configure here.}

[cursor]

Inconsistent error messages between TSRangeParams and TSMRangeParams

Low Severity

TSRangeParams throws "At least one aggregator is required" for an empty aggregators array, while TSMRangeParams throws "Aggregators must be non-null and non-empty" for the same condition. These two parallel methods perform identical validation but use different wording, making the API inconsistent. The PR discussion explicitly suggested the TSMRangeParams wording as the preferred message.

Additional Locations (1)

• src/main/java/redis/clients/jedis/timeseries/TSMRangeParams.java#L155-L156

 

^{Reviewed by Cursor Bugbot for commit e60d8a1. Configure here.}