FT.SEARCH: Cannot read properties of undefined (reading 'length') about node-redis

[dmaier-redislabs]

Hi,

sorry for the late reply. We will take a look and come back to you.

Regards,
David

[sjpotter]

is it possible to have the raw result (i.e. a redis-cli output) so that we can see what's going on?

edit: also the arguments as used to ft.search() could be useful, as the only thing I can imagine happening is that we aren't getting back results in the expected order of

<total # of doc's in search>
<doc-id>
<array of key/value pairs>
<doc-id>
<array of key/value pairs>
....

if for example it's

<total # of docs in search>
<doc-id>
<doc-id>
<doc-id>
....

the error would make sense, if the code expected the first response (as its now trying to parse the "next" doc-id as an array, when it isn't, but this should only happen if one specifies a RETURN option of an empty array.

But I have no idea how it could get into that state, I've run through different permutations of commands and can't duplicate it, so more info is desired if possible.