#community-help

Making Fields Queryable Not in Schema

TLDR Ailish asks how to make fields queryable that are not in the schema, while Kishore Nallan suggests using auto schema detection and wildcards in version 0.25 RC for their needs.

Powered by Struct AI
4
5mo
Solved
Join the chat
Apr 24, 2023 (5 months ago)
Ailish
Photo of md5-7fcbf02da67845f42ef837fd8a989396
Ailish
06:25 AM
Hey 🙂 Is there a way to make fields queryable that are not in the schema? Some of my records have fields which are not in the ‘common’ schema but are populated dynamically when pulling from the source API. Do I need to add them to the schema specifically to make them searchable?
Kishore Nallan
Photo of md5-4e872368b2b2668460205b409e95c2ea
Kishore Nallan
06:33 AM
👋 You can use auto schema detection for such fields. See: https://typesense.org/docs/0.24.1/api/collections.html#with-auto-schema-detection
Ailish
Photo of md5-7fcbf02da67845f42ef837fd8a989396
Ailish
03:03 PM
ah nice thank you Kishore Nallan - is there a similar mechanism on the querying side or you have to pass fields specifically into query_by ?
Kishore Nallan
Photo of md5-4e872368b2b2668460205b409e95c2ea
Kishore Nallan
03:13 PM
In 0.25 RC builds, you can refer to a field like foo* in query_by to match foobar or foobuzz