The discussion revolves around search problems in Discourse v2.3. netpositive reported issues with search results containing unrelated posts and ignoring options like “Matching in title only.” They also mentioned that ignoring accents is not an option due to potential inaccurate results.
sam suggested rebuilding the full search index after changing the site setting search ignore accents, but this did not solve the problem. netpositive provided an example of a search query that returns incorrect results.
zogstrip tested the issue on try.discourse.org and found that the search results were correct. They asked netpositive to share their site settings, which were provided.
zogstrip then tried the search with the default locale set to “magyar” and found that it worked. However, netpositive reported that upgrading to the latest version did not solve the issue.
netpositive eventually discovered that the problem is related to the full-text search in PostgreSQL and how the text is parsed. They hope that using hunspell dictionaries in PostgreSQL will improve the situation, but the Hungarian dictionary is currently broken.
Hello,
I’ve upgraded our Discourse instance from 2.2.6 to 2.3. Unfortunately we’ve noticed some issues with search:
It shows up with terms containing accent like Hungarian word “tészta” 
Ignore accents when searching for text. in admin settings is unchecked.
If you ever amend the site setting search ignore accents you must rebuild the full search index with:
./launcher enter app
rake search:reindex
Thanks for the hint! Unfortunately it doesn’t solve the problem 
It’s quite weird that some pre-2.3 posts contain search URLs (some has multi-word search terms with different accents) which are working fine and return valid result while new search queries are not working and give back not relevant posts.
Has nobody met this problem? 
Unfortunately accents can’t be ignored because it would result in inaccurate results. Where should I look to fix this issue? Maybe downgrading back to 2.2 (it’d be just a temporary fix though )?
Any idea is welcome!
I still don’t understand the problem.
Post an exact chunk of text here with behaviour you would expect. We can then test this on local.
Search term: “kávé in:title” (it doesn’t work without in:title either)
A snippet from results:
The correct result should be:
Besides the irrelevant results, some valid ones are not listed at all.
Thanks a lot!
And you confirm 100% that search ignore accents in site setting is unchecked and that you did a reindex after unchecking that?
Any update on this issue?
I just tested on try.discourse.org and created 5 topics with the titles you provided.
Then, I searched for “kávé in:title” and got these results
Which looks correct to me 
Can you show us the list of all the site settings you’ve changed?
(
make sure you scrap all sensitive values though)
Yes but unfortunately it did not help
I’ve made a fresh local install and “kávé” worked OK but some other words did not. It seems the problem is related to the full text search in PostgreSQL and how the text is parsed. For example from search word “kávé” will be “ká” after normalization and that normalized form will be matched to the text so “kávé” and “káposzta” are both correct results for the FTS
I hope the situation will improve with using hunspell dictionaries in PostgreSQL but currently the Hungarian one is broken 
