#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.

5mo

Join the chat

Apr 24, 2023 (5 months ago)

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?

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

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

03:13 PM

In 0.25 RC builds, you can refer to a field like foo* in query_by to match foobar or foobuzz

Typesense

Lightning-fast, open source search engine for everyone | Knowledge Base powered by Struct.AI

Indexed 2779 threads (79% resolved)

Join Our Community Manage subscription

Similar Threads

Handling Unknown Fields in Search Query Schema

Adrian faced an issue when an unknown field disrupted search queries. Jason informed them that Typesense must validate all fields before filtering and suggested preemptively including these fields as optional in the schema.

Usage and Modification of Dynamic Routes in Typesense Documents

Ethan needed a way to perform exact queries through two fields in Typesense documents. Kishore Nallan demonstrated its possibility using the "filter_by". An issue was resolved via recommending that fields in 'query by' should be a string type.

9mo

Updating Collection Schema and Querying Unspecified Fields in Typesense

Stefan asked about updating a collection schema. Kishore Nallan stated it's not currently possible but suggested automatic schema detection in version 0.20. Rishabh sought a workaround and Jason suggested creating a new collection with a new schema and re-indexing the data. Rishabh also asked about defining custom field IDs which Jason confirmed is not possible with Typesense.

32mo