https://typesense.org logo
Join Slack
Powered by
Heya. Running 0.24.0rcn25 and I'm not sure I'm doi...
# community-help
r
Heya. Running 0.24.0rcn25 and I'm not sure I'm doing "phrase match" correctly. Download phraseMatchFiles.zip then extract it, create data dir, run server, create schema and import doc:
Copy code
mkdir 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 "<http://localhost:8108/collections>" -X POST -H "Content-Type: application/json" -H "X-TYPESENSE-API-KEY: TESTCASEKEY" -d '{"name" : "twig", "fields" : [{ "name" : "content", "type" : "string", "optional" : true }] }'
curl "<http://127.0.0.1:8108/collections/twig/documents/import>" -X POST -H "X-TYPESENSE-API-KEY: TESTCASEKEY" --data-binary @"singledoc.jsonl"
Then perform search:
Copy code
curl --silent "<http://127.0.0.1:8108/multi_search?query_by=content>" -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?
k
I get a 404 for that zip file @Robert Schultz
r
Whoops. Fixed the 404. It's downloadable now
k
Okay, let me look into what's happening.
Able to reproduce, I will investigate and update this thread.
r
Cool beans. Let me know if you'd like me to submit this in a github issue instead. I wasn't sure if it was a bug or if I was doing something incorrectly.
I decided to submit this as a github issue: https://github.com/typesense/typesense/issues/779 Just so it's easier to track going forward as slack isn't super ideal for longer term type issue tracking.
k
Thanks, I've responded on the issue with details on what is happening here.
Open in Slack
PreviousNext
Powered by