Default Sorting Field Issue in Typesense Cloud
TLDR Jide needed help with setting "default_sorting_field" in Typesense cloud. Jason clarified that id
is restricted as it's used internally by Typesense.

Jan 16, 2023 (8 months ago)
Jide
06:17 PMJason
06:21 PMNot really… May I know where you’re seeing this?
Jide
06:28 PMdefault_sorting_field
value of id_id
works but a value of id
does not. Is the value id
just restricted?Jason
06:28 PMid
is a special field that’s used by Typesense internally. So it can’t be set in the schema or the default_sorting_field
Jason
06:29 PMid
in the documents, which is what will then be used by Typesense internally to identify and dedupe documents
Jide
06:32 PM
Typesense
Indexed 2764 threads (79% resolved)
Similar Threads
Sorting Issue with Typesense 0.23.0 and 'title' Field
Stefanie struggles to sort ascendingly with the 'title' in Typesense 0.23.0, where Kishore Nallan replies with questions and insight, though the problem isn't solved.
Issue with Typesense Schema and Ruby Client
Mateo faces issues while creating a schema and using Ruby client for Typesense. Jason suggests using a new field instead of 'id' and provides assistance for Ruby client errors.
Locale Specific Sorting Issue in TypeSense (Cloud)
Viliam inquired if TypeSense supports locale specific sorting. Kishore Nallan confirmed that Typesense only supports English-based sorting. Viliam then decided to create a separate field for sorting.
