Storing Non-Indexed Document Fields in Typesense
TLDR Thomas asked about unindexed, stored fields. Jason explained that unindexed fields can be stored and returned if the document is a match. Andrew added a limitation about nested fields.
3
2
1
1
Feb 23, 2022 (20 months ago)
Thomas
05:19 PM
Jason
05:20 PMJason
05:21 PM1
Jason
05:22 PMJason
05:22 PMThomas
05:22 PM
Andrew
05:56 PM"data" : { "small": "foo", "big": "bar bar"} you can include or exclude "data" but not "data.small" or "data.big". This causes us a few problems, so I wanted to mention iz
2
1
Andrew
05:59 PM1
Thomas
06:19 PM1
Thomas
06:19 PM1
Typesense
Indexed 2786 threads (79% resolved)
Similar Threads
Discussing Issues and Improvements for Typesense
Greg shared feedback and raised questions about Typesense, specifically about nested objects, rate limiting, and documentation. Kishore Nallan provided explanations, confirming that non-searchable fields can be stored and noting to improve documentation clarity.
Restricting Data Storage in Typesense to Defined Schema Fields
Ashwin asks if Typesense can save only fields in their schema. Kishore Nallan advises removing unwanted fields pre-indexing, and using include_fields param to return desired fields.
Querying Non-indexed Fields
Blend asked about performing queries on non-indexed fields. John and Jason confirmed this is not possible, but unindexed fields can still be included in the document for display data.
Typesense Server Data Structure Issue
Anton had difficulties handling nested fields in Typesense and was seeking advice. Kishore Nallan clarified that Typesense only deals with flat documents, thus no nesting is possible.
Configuring Typesense Extension for Nested Fields in Firebase Collection
David had issues indexing nested fields using the Typesense extension. Jason offered advice on specifying schemas and prioritizing specific fields, but there remained unresolved challenges with the schema.