#community-help

Discussing Typesense's Handling of Sparse Indexed Fields

TLDR Adrian questioned how typesense manages sparse indexed fields. Kishore Nallan clarified that absent values aren't stored, optimizing storage and performance.

26mo

Join the chat

Sep 17, 2021 (26 months ago)

Photo of md5-0faf10c668e73a12e9a6dcd5682ea60e

Adrian

06:36 AM

Any thoughts on how typesense handles sparse indexed fields? If a collection schema has a lot of fields (like 100) but each individual document only has a couple (<10 fields) actually present, what should I expect from a storage and performance perspective?

Photo of md5-4e872368b2b2668460205b409e95c2ea

Kishore Nallan

06:38 AM

Should not be a problem. We don't store a default value or anything for optional values. So it will simply not exist in the inverted index.

Adrian

06:39 AM

cool thanks!

Typesense

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

Indexed 2786 threads (79% resolved)

Join Our Community Manage subscription

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.

30mo

Storing Non-Indexed Document Fields in Typesense

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.

21mo

Query on Performance with Many Fields in Typesense

John asked about the performance implications of having many fields but only searching on a few in Typesense. Kishore Nallan clarified that all indices are field level and independent.

13mo