Replies: 3 comments 1 reply
-
Hitting the same issue. Are there any workarounds? |
Beta Was this translation helpful? Give feedback.
-
Yeah, really frustrating, any solutions? |
Beta Was this translation helpful? Give feedback.
-
As this was the first result when searching the issue, I though I'd post what I did for anyone else that may need it. The problem is that this FT.SEARCH with a RETURN only gave me strings.
I could identify and handle the string -> number conversions, but arrays were returned as a string containing the first element in the array.
...which is no good and I couldn't do anything with it. Long story short, I worked out the RETURN was the culprit for this, so I dropped it and handled it differently:
Now, the All the best x |
Beta Was this translation helpful? Give feedback.
-
Hi, it seems that regardless of the types I specify in my indices the
.ft.search()
command always returns my data as strings (when I useRETURN
in the query). Is that expected behavior somehow? I would assume not, so am I doing something wrong?For context, I'm storing JSON docs of the type:
and I created an index like this:
And when I do a search in Node like:
I actually get the expected result:
But when I do a search using
RETURN
like this:suddenly the result I get is:
As you can see the "quantity" field is returned as a string, not a number.
Beta Was this translation helpful? Give feedback.
All reactions