Issues with Non-Indexed Required Fields and Nested Fields Schemas
TLDR Dima questioned why non-indexed fields can't be required and disabled auto-schema for nested fields. Kishore Nallan acknowledged both as potential fixes and asked user to create issues.
1Jun 28, 2023 (3 months ago)
Dima
02:37 PM
Kishore Nallan
02:38 PMDima
02:40 PMKishore Nallan
02:41 PMKishore Nallan
02:41 PMDima
02:43 PMAlso, it is possible to disable auto-schema (?) for nested fields? I have an
object field with index: false in the schema and when I add documents in the index, typesense creates nested fields definitionsKishore Nallan
02:44 PM1Dima
02:52 PMMaybe it’s expected behaviour
Kishore Nallan
03:02 PMDima
03:58 PMBut what about non-indexed required fields? Let me create two issues, one for tracking non-optional non-indexed field and one for unexpected nested fields schema
Typesense
Indexed 2764 threads (79% resolved)
Similar Threads
Defining fields to index of a nested object without flattening
Taj asked how to index fields of a nested object without flattening. Jason clarified this is possible and the object need not be in the schema. To clarify things further, Jason updated the docs.
5Storing Object Field in Document Schema
Dima asked if `enable_nested_fields` is needed to store object fields with `index: false`. Kishore Nallan clarified no special settings were needed and the object-type field only needs to be added to the document.
Handling Index and Optional Properties in Collections
Narayan questioned about disallowed sorting on an optional field. Kishore Nallan explained that the issue arises when the field is marked index: false. They clarified that a field set to index: false must be optional: true.
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.
7Non-Indexable Fields Enforced as Optional: Reasoning and Revisions
Sai asked about the enforcement of non-indexable fields being optional. Kishore Nallan informed them of the unclear historical basis and requested they create a tracking issue on GitHub for investigation.