Trouble with Text Match Score Calculation
TLDR Alex experienced issues with text match score results. Jason identified a calculation error, promising a future fix that would ensure the correct match scores and view counts were displayed.
Mar 20, 2021 (33 months ago)
1. text_match: 130816, viewCount: 180500, name: 'Luxthos - Shaman' 2. text_match: 196450, viewCount: 169474, name: "Luxthos - Paladin Core" ... ???. text_match: 196451, viewCount: 11, name: "Luxthos Paladin"
Now I have 2 problems
1. The first result technically matches the query, but it's a pretty terrible match. It's like searching for
Apple iPadand getting
Apple iPhonebecause it's more popular.
2. The result that matches the text the best will never be seen because it's so far down. Sure, it doesn't have many views, but it would still be nice to show it near the top.
Mar 22, 2021 (32 months ago)
Luxthos - Paladinshould have the same match score for the query
luxthos paladin- this is something that should be fixed as part of another change we're working on.
Once that's addressed, then with the match score tied between records, then viewCount will be used to break the tie and you'll see
viewCount: 169474, name: "Luxthos - Paladin Core"show up as the first result.
I'll let you know when this change is done in an RC build
Indexed 2779 threads (79% resolved)
Issues With `text_match` Scoring for Search Queries in Typesense
Colin encountered issues with the `text_match` scoring on Typesense v0.23.1. Jason and Kishore Nallan identified a potential issue with numeric overflow in the text match score and applied an unverified patch. The final resolution is unclear.
Solving Conflicts in Searching and Ordering Data with Typesense
SamHendley faced an issue with search result order in Typesense. Kishore Nallan explained two behaviors that affected the ranking and pledged to change these, while also considering an additional suggestion from SamHendley. These changes were implemented in version `0.24.0.rcn39`.
Discussion on Typesense Raw and Altered Text Match Scores
Weilin requested that Typesense provide both raw and altered 'text match' scores for ranking. Jason asked for a GitHub issue and promised to address it next week. Kishore Nallan then clarified the current implementation already includes the raw score.