Bug in Phrase Search with Double Quotes
TLDR Sachyya reports a bug where text_match score and tie breaker field are ignored in phrase search. Kishore Nallan suggests using a recent 0.25 RC build, providing the download link.
Apr 20, 2023 (8 months ago)
Sachyya
09:59 AMquery_by: post_content, cad_tags, speaker, speaker_referred, countries, articles If we search for Gandalf, it works for any word case with text_match score being respected. But in case of exact word, it does not respect the text_match score nor the tie breaker for the sequence of query_by fields listed above. For exact word case, we are wrapping query with double quotes.In the test case, if you search for Gandalf, it is mentioned 3 times in Historical Constitutions | Government of India Act, 1919 but it's not showing first in the search list. Does the text_match and tie breaker field ignored when searched with query being wrapped in double quotes.
Test site: https://cadcodemanas.redstart.dev/search-with-typesense/
Kishore Nallan
10:10 AMSachyya
10:13 AMKishore Nallan
10:14 AMSachyya
10:14 AMKishore Nallan
10:50 AMSachyya
11:05 AM
Typesense
Indexed 3015 threads (79% resolved)
Similar Threads
Phrase Search Relevancy and Weights Fix
Jan reported an issue with phrase search relevancy using Typesense Instantsearch Adapter. The problem occurred when searching phrases with double quotes. The team identified the issue to be related to weights and implemented a fix, improving the search results.
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.
Phrase Match Problem in Typesense Version 0.24.0rcn25
Robert was unsure about correct phrase match usage in Typesense. After providing Kishore Nallan with necessary data, Kishore Nallan was able to replicate the issue. Robert shared a Github link for further tracking, where Kishore Nallan responded later.