TLDR Jeremy was struggling with an exact match search issue in Typesense. Jason suggested upgrading to version 0.24.0.rcn44 of Typesense which resolved Jeremy's problem.
Part number is the first query by field
Could you share the document that you expect to match in JSON format, and also the full search query you’re using with all the search parameters?
Also, may I know which version of Typesense this is on?
Just installed yesterday, so should be 0.23.1 right? `search?q=500&query_by=Item,Description,WebShortDescription,WebLongDescription,Name,Class,SubClass,WebCategory&sort_by=Rank%3Aasc` ```{ "Class": "Beam Clamp", "Item": "500", "Name": "Beam Clamp", "Rank": 58, "Description": "Beam Clamp Spring Steel", "SubClass": "Set Screw", "UrlSlug": "500", "WebCategory": "With Bolt", "WebLongDescription": "Set Screw Beam Clamp, Fits up to 1/2\" Flange, Pass Hole for 1/4\" and 3/8\" Threaded Rod, 1/4\"-20 Thread Impression on Bottom and Back of Clamp, #10-24 Thread Impression on Back of Clamp, Spring Steel", "WebShortDescription": "Beam Clamp Up to 1/2\" Flange, Pass Hole For 1/4\" And 3/8\" Threaded Rod, 1/4\"-20 Bottom and Back, #10-24 Back, Spring Steel", "id": "7986" }```
We improved some relevance features in 0.24… Could you try this on 0.24.0.rcn44?
Getting an expected result now :slightly_smiling_face:
Jeremy
Thu, 22 Dec 2022 18:31:53 UTCRan into a strange issue with exact match not working. I am searching products, with a part number and a handful of descriptions. I have products with part number 5, and 500. Searching "5", produces the part number 5 as the first result, and then all other results that match 5 in the description. Searching "500" doesn't find my part number 500. It only display results with 500 in the description, and other parts with 500 in it (like 50009, 50012 etc...). Why would exact match not find 500?