Sorting Issue in Typesense Schema
TLDR Keith had issues sorting by the field 'year' after changing its type to a string. Jason clarified that Typesense currently only supports numeric sorting and offered a workaround.
1
Dec 17, 2021 (23 months ago)
Keith
05:01 PMError: 404 - Could not find a field named year in the schema for sorting. The field itself is optional, which it was before, does there always have to have a value though to be set inadditionalSearchParameters: {
queryBy: "title,barcode",
sortBy: "_text_match:desc,year:desc",
}
Jason
05:14 PMJason
05:14 PM1
Keith
05:15 PMKeith
05:15 PMJason
05:16 PMJason
05:16 PMKeith
05:19 PMKeith
05:26 PMKeith
05:28 PMKeith
05:32 PMJason
05:34 PMKeith
05:59 PM
Typesense
Indexed 2779 threads (79% resolved)
Similar Threads
Resolve Facets and Sorting Issues with Typesense
Ethan needed assistance with getting all facet values and sorting results by date using Typesense. Jason provided guidance on how to use Typesense properties to accomplish these tasks, and resolved issues related to specific use-cases provided by Ethan and Rushil.
Sorting Results in Typesense and Handling Errors
Ramees asks about sorting results by distance in Typesense, entering a list of strings as a field, and resolving an error with `fields` format. Kishore Nallan assists with these issues and advises on storing timestamps and proper authentication.
Solving Searchable String ID Sorting Issue
Mubashirullah needed to sort by string id, which was not supported. Kishore Nallan offered a preview Docker build with the feature. Mubashirullah expressed satisfaction with the solution.
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.
Methods for Fetching, Querying, and Modifying Collections in Typesense
Bill inquired about performing OR queries, querying empty arrays and modifying collections in Typesense. Kishore Nallan explained the current limitations and provided workarounds and recommendations for each case. The conversation also touched upon the usage of cache in Typesense and the workings of the _eval function.