You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm trying Redis search / Redis OM for the first time.
I found a strange behavior In this nestJS project currently on branch Redis.
During my test I got the Error: [ErrorReply: Invalid field type for field `UNF`]
With no stack and no mention to Redis.
After investigation, the error occurred when I call createIndex, if I set a normalized: false in my model.
In my case the faulty generated create index request was:
FT.CREATE
DroidUser:index
ON JSON
PREFIX 1 DroidUser:
SCHEMA
$.createdAt AS createdAt NUMERIC NOINDEX
$.updatedAt AS updatedAt NUMERIC NOINDEX
$.email AS email TAG SEPARATOR | UNF
$.hash AS hash TAG SEPARATOR | NOINDEX
$.name AS name TAG SEPARATOR | NOINDEX
$.role AS role TAG SEPARATOR |
$.devices[*] AS devices TAG SEPARATOR |
$.tokens[*] AS tokens TAG SEPARATOR |
so:
can an error occurring during the create index can be more verbose ?
can you properly handle normalized: false?
In my case I want to set normalized to true, so my RedisOM test is still on track.
The text was updated successfully, but these errors were encountered:
I'm trying Redis search / Redis OM for the first time.
I found a strange behavior In this nestJS project currently on branch Redis.
During my test I got the Error:
[ErrorReply: Invalid field type for field `UNF`]
With no stack and no mention to Redis.
After investigation, the error occurred when I call
createIndex
, if I set anormalized: false
in my model.In my case the faulty generated create index request was:
so:
In my case I want to set normalized to true, so my RedisOM test is still on track.
The text was updated successfully, but these errors were encountered: