#community-help

Prioritising Email in Collections Using Typesense

TLDR Pankaj had an issue ranking user emails first in a collection. Jason explained how 'sort_by' works and suggested using the new filter-based sorting mechanism, specifically "sort_by": "_eval(has_email:true):asc,id:desc". Pankaj agreed to try this solution.

14mo

Join the chat

Oct 26, 2022 (14 months ago)

Photo of md5-6eb5a1ce5c2a902eaa7ed5dae82ed54b

Pankaj

03:47 PM

Hi guys, i have a scenarios tried some ways but not able to get it right
my example collection

email 
id 
description

i want to rank the result where users with having email are ranked first with id desc

tried doing sort_by
email(missing_values:last):desc,
_text_match:desc,
id:desc

but looks like missing_values is last one to sort so it always like email desc any other ways this can be done ? thanks in advance

Photo of md5-8813087cccc512313602b6d9f9ece19f

Jason

04:42 PM

sort_by uses a tie-breaking to sort on multiple fields. So in your case it will first sort on email (and place missing values last), and then if two records tie by having the same email address, then _text_match is used to break the tie. And then if that also ties, then id is used to break the tie.

You could use the new filter-based sorting mechanism we’ve added in 0.24.0.rcn25 to implement your use case. Something like:

"sort_by": "_eval(has_email:true):asc,id:desc"

where has_email is a new boolean field you’ll have to create at indexing time to each record

Oct 27, 2022 (14 months ago)

Pankaj

06:07 PM

will try this. thank you 🙂

Typesense

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

Indexed 3005 threads (79% resolved)

Join Our Community

Similar Threads

Document Weighting and Sorting Discussion

SamHendley asked how to weight a document based on age and offered a sorting method. Jason clarified the method and suggested an RC for use. SamHendley tested and confirmed the solution. User Kishore Nallan assisted when an error occurred with a new feature.

11mo

Troubleshooting Typesense API Sorting Error in Item Collections

Nikhil encountered a sorting error when using Typesense API due to an optional reference field in the items collection schema. Harpreet and Jason helped debug and identified a bug with sorting in general for 2 fields with the first one being the join field, promising a fix in a forthcoming build.

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.

4mo