I’ve noticed that for some searches, I get no results: [CleanShot 2021-06-28 at 07.00.30@2x] But if I narrow the search, for example to a specific topic, I do get the result I’m looking for: [CleanShot 2021-06-28 at 07.01.06@2x] I initially thought it might have something to do with the accent…

Hi @Nacho_Caballero Can you provide me with a sample text and search term that can reproduce the problem? I can see it in the image but only the excerpt can be seen.

Thanks, Alan. Here are the contents of that specific post: post:46: ¿No lo usamos nunca después de “pensar que” o hay una regla? En efecto, no se usa después del “pienso que” porque lo que estás afirmando que piensas, se trata de una realidad, y no de una posibilidad. Por otro lado, util…

@Nacho_Caballero ,Hey can u please let me know currently which search algo is Discourse using, it will help me in looking into the issue.

Thanks, Yashi. I assume Discourse uses the default full-text search Postgres algorithm. I think the only way to provide exact matches when using quotes (without stemming and without ignoring stop words) would be using the ‘simple’ dictionary :thinking:

Thankyou, @Nacho_Caballero . I will look over Postgres full text algo.

Is it possible to search for exact match? Example: At the moment, search for “flow” unfortunately returns “flower” as the highest relevance ..

How to enforce exact matches when searching?

Support

codinghorror (Jeff Atwood) October 21, 2021, 3:04am 11

Try searching with quotation marks, e.g. search for “flow” not flow.

Topic		Replies	Views
Are specific terms ignored from searches? Support	12	1541	October 14, 2024
Discourse should ignore if a character is accented when doing a search Feature search , completed	50	6895	October 24, 2018
Search problems in v2.3 Support	13	1455	September 11, 2019
Some flaky experience when searching Support search	9	286	September 23, 2026
Diacritics and search Feature	16	2740	August 31, 2018

How to enforce exact matches when searching?

Related topics