Question About Text_Match and Token Reoccurrence
TLDR Paul asked about the effect of token reoccurrence on _text_match
. Kishore Nallan informed them it's not taken into account due to issues with "keyword stuffing". Jason suggested breaking long form content into multiple documents to improve search result relevance.
Oct 21, 2022 (12 months ago)
Paul
02:20 PM_text_match
should be affected by the number of times a token is found within a field? Currently I’m seeing the same score for hits, regardless how many times the token appears within the field. For example, searching for a single word, any result that contains that token at least once, is returned but with the same score even though one result has the token 10 times in the body field and another result only has 1 occurrence of the token.Kishore Nallan
03:30 PMPaul
03:43 PMThere isn’t any tie-breaking I can apply, so is typesense not really suitable for long form content?
Jason
05:44 PMTypesense
Indexed 2779 threads (79% resolved)
Similar Threads
Inconsistent Search Results in Typesense UI vs Dashboard
Abhishek reports inconsistent search results in the typesense UI vs dashboard integration when using page rank with Docusaurus plugin. Jason suggests creating a GitHub issue while Abhishek seeks clarification on prioritizing exact matches.
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.
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.