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 accented character, but I’ve done several tests and the same thing happens with unaccented characters. My second thought was that it might be due to stop words, but I’ve changed app.yml to truncate the Spanish stopwords dictionary: ls -l /usr/share/postgresql/13/tsearch_data/spanish.stop -rw-r--r-- 1 root root 0 May 12 06:37 /usr/share/postgresql/13/tsearch_data/spanish.stop ☝️ Are there any settings I could tweak to make sure exact matches are always found?

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, utilizamos subjuntivo cuando utilizamos esta misma estructura, pero en negativo: “No pienso que haya mucha gente en el mercado hoy”. Espero que esto responda a tu respuesta, pero si necesitas más detalles, por favor dime, y con gusto te ayudaré. ¡Saludos! :smiley: However, to reproduce the behavior here, you’d have to set the locale to Spanish and truncate the dictionary :sweat_smile: I’ve tested it on a development Discourse site I have running locally and I’m not able to reproduce the behavior, but I think it’s because the site is practically empty. I don’t think this issue comes up until you have a lot of posts (I currently have around 68K). I could try other things related to the postgres dictionary, but I’m not sure how to enter my docker image when running a development installation. Is there an equivalent to launcher enter app? Ideally, there would be a way to ignore stop words. For example, to look for this sentence in your message: [CleanShot 2021-06-29 at 09.12.42@2x]

@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 ..

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

How to enforce exact matches when searching?

Product Support

tgxworld (Alan Tan) June 29, 2021, 12:58am 3

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.

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

How to enforce exact matches when searching?

Related topics