Phrase Match Problem in Typesense Version 0.24.0rcn25
TLDR 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.
Oct 26, 2022 (14 months ago)
Robert
06:15 PMRobert
06:16 PMmkdir data
typesense-server --data-dir=./data --api-address=127.0.0.1 --api-port=8108 --peering-address=127.0.0.1 --api-key=TESTCASEKEY
curl "" -X POST -H "Content-Type: application/json" -H "X-TYPESENSE-API-KEY: TESTCASEKEY" -d '{"name" : "twig", "fields" : [{ "name" : "content", "type" : "string", "optional" : true }] }'
curl "" -X POST -H "X-TYPESENSE-API-KEY: TESTCASEKEY" --data-binary @"singledoc.jsonl"
Then perform search:
curl --silent "" -X POST -H "Content-Type: application/json" -H "X-TYPESENSE-API-KEY: TESTCASEKEY" --data-binary @"searchTest.json"
It returns 1 hit, but I was expecting ZERO hits, because in the content the words "frontier mail" do not appear together. I see that according to highlight.meta.content.matched_tokens it only matched on "mail".
Am I not correctly doing phrase match properly? Is there an additional setting or flag I need to set?
Oct 27, 2022 (14 months ago)
Kishore Nallan
04:39 AMRobert
11:50 AMKishore Nallan
02:13 PMKishore Nallan
03:07 PMOct 28, 2022 (14 months ago)
Robert
01:44 AMNov 08, 2022 (13 months ago)
Robert
01:55 PMJust so it's easier to track going forward as slack isn't super ideal for longer term type issue tracking.
Kishore Nallan
02:13 PMTypesense
Indexed 3011 threads (79% resolved)
Similar Threads
Issue with `included_fields` Command in Typesense
SamHendley encountered an issue with the `included_fields` command in Typesense versions 0.23.0 and 0.24.0.rc17. Jason helped identify it as a bug in the 0.24.X version, which was later addressed in release 0.24.0.rcn19.
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.
Resolving Multilingual Search Function in Typesense Software
Bill is having difficulty with multilingual search functionality in Typesense software. Developer Kishore Nallan suggested setting a language locale and provided a demo build. The build solution had some issues, and after multiple rounds of software updates and troubleshooting, the problem still persists.
Array Field Autocomplete Issue in Typesense Migration
Kanwei encountered issues with autocomplete when migrating from Elasticsearch to Typesense. Jason and Kishore Nallan identified it as a bug and instructed Kanwei to create a GitHub issue.
Troubleshooting Issues with DocSearch Hits and Scraper Configuration
Rubai encountered issues with search result priorities and ellipsis. Jason helped debug the issue and suggested using different versions of typesense-docsearch.js, updating initialization parameters, and running the scraper on a Linux-based environment. The issues related to hits structure and scraper configuration were resolved.