- edited description
Accumulated feedback pre-release phase
Issue #1
closed
We ant to collect all kinds of feedback in the pre-Marketplace-release here. We are more than happy to get information like:
- Did the plug-in help you?
- Was the delay of the search acceptable?
- etc.
Comments (8)
-
reporter
-
Hi @apurde, thanks for this, it is really interesting. I've had a quick look at the code, but still come asking questions ;)
Does this do anything for Lucene stop words in exact matches?
For example, when searching for the phrase
"drum and bass", Confluence's default behaviour is to see that the stop wordandis present, so instead of searching for the correct exact match --"drum and bass", it will search for"drum bass"removing the stop word.I'm guessing that your plugin doesn't override this behaviour, but just wanted to check.
-
reporter
Dear David,
thank you for your post. You are right. However, according to my experience Confluence would search for all content which contains drum or bass. The plug-in then only boosts the subset in which the term drum and bass appears - as long as you put it in quotes.
Andreas
-
reporter
I have to correct myself: the plug-in does NOT solve this part of the problem.
"drum and bass" never shows up as search result.
You are right, David.
-
reporter
What could be done of course; introduce single quotes: they are ignored by Confluence but could be used by me to boost exact phrases including stop words.
-
reporter
I uploaded a new version 0.7.0 which overcomes the stop word problem. However you have to set your exact phrase in single quotes (not double quotes):
'drum and bass' -
👍👍👍 This is a nice trick to workaround the stop word problem.
If CONFSERVER-14910, ever gets fixed, we'll be able to do real exact matches for things like "to be or not to be" which are likely all stop words.
By the way, here's an interesting article about the real problem:
-
reporter
- changed status to closed
closed as the plug-in is now released
- Log in to comment
