Node client search response corrupted when there are exactly 2 JSON items stored and using a limit size of 1

[SamBeroz]

Description

I want to update to the 5.X client but the attached code isn't working (it does work on 4.7.0). When I have 2 JSON items stored and search for the first item based on an aliased property in the JSON object it returns a mangled response. It works as expected if I have only 1 item or more than 2 items stored but when I have exactly 2 items stored it's a problem. Also it only seems to happen with a limit with a size of 1.

The response I would expect is:
{"total":2,"documents":[{"id":"test:itemA","value":{"itemOrder":1}}]}
However the response I get is:
{"total":2,"documents":[{"id":"test:itemA","value":{}},{"id":["itemOrder","1","$","{\"itemOrder\":1}"],"value":{}}]}

The problem query is:

  const result = await client.ft.search(indexName, "@itemOrder:[0 10]", {
    SORTBY: {
      BY: "itemOrder",
      DIRECTION: "ASC",
    },
    LIMIT: {
      from: 0,
      size: 1, //Using a limit of 1 here seems to be a problem when there are two items stored
    },
  });

where my index is:

    await client.ft.create(
      indexName,
      {
        "$.itemOrder": {
          type: "NUMERIC",
          AS: "itemOrder",
        },
      },
      {
        ON: "JSON",
        PREFIX: getKey(""),
      }
    );

The full code that demonstrates the issue is attached.

Node.js Version

v22.12.0

Redis Server Version

redis_version:7.4.3

Node Redis Version

redis@5.8.1

Platform

Windows and Linux

Logs

Connected to Redis
First item with 1 entry:
result: {"total":1,"documents":[{"id":"test:itemA","value":{"itemOrder":1}}]}
found item: [Object: null prototype] { itemOrder: 1 }
Second item with 2 entries:
result: {"total":2,"documents":[{"id":"test:itemA","value":{}},{"id":["itemOrder","1","$","{\"itemOrder\":1}"],"value":{}}]}
found item: [Object: null prototype] {}
found item: [Object: null prototype] {}
Third item with 3 entries:
result: {"total":3,"documents":[{"id":"test:itemA","value":{"itemOrder":1}}]}
found item: [Object: null prototype] { itemOrder: 1 }

[PavelPashov]

Hey @SamBeroz, thanks for reporting this, I managed to reproduce it, we'll work on a fix.

[cabaisma]

Thanks for reporting this @SamBeroz, I also having the same issue. After a couple of hours debugging it, I found out that the bug occurs when the total docs is divisible by the limit value.

Example:

In our production we have 20 total docs and I set the limit to 1, 2, 4, 5 or 10. // The issue occurs.
If I set the limit other than the values mentioned above then it works fine.

Similarly, in local environment I created 2 docs and set the limit to 1. // The issue occurs.