Typesense Non-String Field Query Workarounds
TLDR Carl seeks advice on querying non-string fields in Typesense. Kishore Nallan suggests using a string version, and Jason proposes the string* data type. Carl is considering these options.
2
Jan 21, 2022 (22 months ago)
Carl
08:48 AMCarl
08:50 AMstring
as an int
on the consumer side.One workaround we think could work, is to have some top level properties which are solely used for searching on. Then have some kind of "payload" property to store the contents in the correct data form.
Kishore Nallan
10:43 AM1
Jason
02:11 PM1
Jan 24, 2022 (21 months ago)
Carl
09:14 AMstring*
, otherwise will go with the workaround I mentionedTypesense
Indexed 2779 threads (79% resolved)
Similar Threads
Solving Typesense Cloud Interface Issue in Python
Orion had an issue querying from Python in the Typesense Cloud interface. Kishore Nallan identified the problem within the array declaration. They then discussed improving error messages and Orion offered to make a PR.
Accessing string[] Data Type in Typesense Demos
Vishal inquired about accessing string[] datatype fields in Typesense demos. Jason suggested using console.log, but the issue remains unresolved.
Querying Null and String Values in Typesense.
Andrew wondered if they could look for non-null and string values in Typesense, but Jason explained a workaround by creating a new boolean field at indexing time.