#community-help

Understanding the 'text_match' calculation in Typesense.

TLDR John asked about the interpretation of text_match scores while Kishore Nallan clarified that the score is a composed int64 integer and shared the computation link.

18mo

Join the chat

Jun 20, 2022 (18 months ago)

Photo of md5-21545f1facb7836c149bc4c70752bd2b

John

12:38 PM

Is there any explanation of how text_match is computed somewhere, or some way to make it more interpretable? I get scores like 565161851289602 which is quite opaque 😅

Photo of md5-4e872368b2b2668460205b409e95c2ea

Kishore Nallan

12:42 PM

The score is a single int64 integer that's composed from several byte-wise text relevancy "components". The major bit is calculated here: https://github.com/typesense/typesense/blob/main/include/match_score.h#L53

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

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.

16mo

Discussing 'Text Matches' Feature Improvement in Typesense

Stefan asked if distance in 'text matches' can be determined. Kishore Nallan said no and asked for an issue to be created on Github, which was done by Stefan.

27mo

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.

17mo