Sorting Agents Based on Primary Market Position
TLDR Saahiththiyan wants to sort agents based on their primary_market
position, but Kishore Nallan suggests it's not possible server side and recommends a client side solution.
Mar 21, 2023 (9 months ago)
Saahiththiyan
01:20 AMI have a collection called
agents
, each agent in that index can have primary_market
.Example, for an agent called Jack
primary_market: [Sydney-NSW-2000-Australia, Pots-Point-NSW-Australia]
, For an agent called Bill primary_market: [Pots-Point-NSW-Australia, Sydney-NSW-2000-Australia]
When i filter for agents using the slug
Sydney-NSW-2000-Australia
i want to have Jack on top of the results based on the position of the slug inside the primary_market
and Bill to be at the bottom of the results.Basically i want to sort the results based on the position of the slug i am filtering by inside the
primary_market
array.Likewise if i filter for agents using the slug
Pots-Point-NSW-Australia
i want Bill to be at the top of the results and jack to be at the bottom.Is that even possible? or even an alternative way where i can achieve the same outcome? Any help would be awesome.
Kishore Nallan
03:06 AMTypesense
Indexed 3015 threads (79% resolved)
Similar Threads
Adjusting Text Match Score Calculation in TypeSense
Johannes wanted to modify the Text Match Score calculation in TypeSense to improve search results returns. With counsel from Jason and Kishore Nallan, various solutions were proposed, including creating a Github issue, attempting different parameters, and updating Docker to a new version to resolve the matter.
Issue with Embedding Error in Version 0.25.0.rc63
Bill reported a bug in version 0.25.0.rc63 regarding a problem with updating or emplacing a document and receiving an embedding error. This was resolved in version 0.25.0.rc65, but further discussion ensued regarding the function of 'index' in the update feature.
Typesense Bug Fix with `canceled_at` Field and Upgrade Concerns
Mateo reported an issue regarding the treatment of an optional field by Typesense which was confirmed a bug by Jason. After trying an upgrade, an error arose. Jason explained the bug was due to a recent change and proceeded to downgrade their version. Future upgrade protocols were discussed.