Discussing Issues and Improvements for Typesense
TLDR 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.
May 26, 2021 (32 months ago)
• Nested objects and arrays of objects (even if they're not searchable/filterable).
• As an alternative to first-class nesting, maybe an option to format documents on the way out (i.e. store em flat, enhance/expand structure on the way out).
• Rate limiting? Key-specific or across the board.
• Google results for older versions? Love the version picker in the docs but it's easy to end up on an older version without noticing.
• Sorting on fixed length strings! (already found this, just noting that i'm excited about it 😁)
Kishore Nallan03:22 AM
> even if they're not searchable/filterable
You can already store non-indexed nested fields in Typesense. Typesense will just store any document you throw at it verbatim and use the schema to only index the fields mentioned in the schema.
Kishore Nallan03:39 AM
Indexed 3015 threads (79% resolved)
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.
Handling Nested Objects in Typesense
Darren queried about storing arrays of objects in Typesense. Kishore Nallan advised that Typesense doesn't support nesting but shared alternative reindexing methods. They added improved nesting support is planned for the future.
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.