-
Suggestion
-
Resolution: Fixed
NOTE: This suggestion is for Confluence Cloud. Using Confluence Server? See the corresponding suggestion.
Currently there is no way to perform a search that will only return exact matches because the words will be tokenized by lucene.
If there is no way to make the search return only exact matches at the very least I'd expect it to prioritize exact matches in the search and show them first?
(This is in response to CSP-26824)
- is related to
-
AI-891 Provide ability to override Lucene tokenisation and stemming and search for exact text
-
- Short Term Backlog
-
-
- Closed
-
- Closed
[AI-821] Ability to make search return exact matches or at least prioritize exact matches in the search results
In what way is this fixed? Confluence simply ignores stop words in exact matches. This bug is still not fixed.
Ken Roland
added a comment - This should not be an "improvement". It's a bug! A HUGE BUG!! Try searching for "adaptation" at http://confluence.atlassian.com you get useless and incorrect results. "When I search I should find what I'm searching for." That should have been a requirement on 1.0.
Ken Roland
added a comment - This should not be an "improvement". It's a bug! A HUGE BUG!! Try searching for "adaptation" at http://confluence.atlassian.com you get useless and incorrect results. "When I search I should find what I'm searching for." That should have been a requirement on 1.0. 
Brian Hart
added a comment - I agree with previous comments, and am surprised there's no exact search facility. When searching my wiki for "communicator", I get results back including: communications, communication, communicate, communicating, and community. Makes it really hard to find that one document about Microsoft Communicator that I'm looking for.
Too smart for its own good.
Brian Hart
added a comment - I agree with previous comments, and am surprised there's no exact search facility. When searching my wiki for "communicator", I get results back including: communications, communication, communicate, communicating, and community. Makes it really hard to find that one document about Microsoft Communicator that I'm looking for.
Too smart for its own good. We are a technical company where "EXACT PHRASE" search is critical. I'm surprised Atlassian doesn't run into this itself daily?
Searching for acronyms that end in S causes problems "CDS", "HDS" both return things like "HD screen"
Prioritizing them would help. It would also help with our other problem search "GUID" which returns thousands of results for "Guide" and maybe somewhere in there are results for GUID but you'll never find them
Ken Roland
added a comment - - edited We are a technical company where "EXACT PHRASE" search is critical. I'm surprised Atlassian doesn't run into this itself daily?
Searching for acronyms that end in S causes problems "CDS", "HDS" both return things like "HD screen"
Prioritizing them would help. It would also help with our other problem search "GUID" which returns thousands of results for "Guide" and maybe somewhere in there are results for GUID but you'll never find them 
Martin Barkanowitz
added a comment - I've got the same problems in 2.10.3.
Exact search doesn't work properly, even if I set the search term in doubled quotes as the docs state.
Often the top results are stemmed variations of the search term, then followed by the exact search term a little bit later. Very confusing for users going for an exact search.
Why don't you provide a control to switch the stemmed search off?
Martin Barkanowitz
added a comment - I've got the same problems in 2.10.3.
Exact search doesn't work properly, even if I set the search term in doubled quotes as the docs state.
Often the top results are stemmed variations of the search term, then followed by the exact search term a little bit later. Very confusing for users going for an exact search.
Why don't you provide a control to switch the stemmed search off? 
It is not fixed, it is a duplicate of CONF-14910.