-
Suggestion
-
Resolution: Unresolved
NOTE: This suggestion is for Confluence Cloud. Using Confluence Server? See the corresponding suggestion.
At the moment, searching for "hello-to-the-world" in Confluence always returns the same results as "hello to the world". This situation also applies for symbols like plus, underscore, period, dollar sign, percent sign, and so on.
There's also no way to prevent asterisks being treated as wildcard characters in Lucene, so you can't search for a word like "plea" and match content with asterisks around the word.
Words are also not split on dots, so you can't search for "somefile" and find pages that contains "somefile.txt" or "somefile.doc" in the text.
Technical notes
This is due to how Confluence's search tokenises search requests. It splits the query up into words based on letter characters, and ignores all symbols in the request. We use Lucene's StandardTokenizer in our EnglishAnalyzer, and similar implementations for other languages.
Here is the description of the behaviour of StandardTokenizer from Lucene:
- Splits words at punctuation characters, removing punctuation. However, a dot that's not followed by whitespace is considered part of a token.
- Splits words at hyphens, unless there's a number in the token, in which case the whole token is interpreted as a product number and is not split.
- Recognizes email addresses and internet hostnames as one token.
An example of the grammar for this tokenizer can be viewed here: StandardTokenizerImpl.jflex.
- is duplicated by
-
CONFCLOUD-28241 search impossible
- Closed
- is related to
-
AI-568 Support substring (partial) searches for terms used in Confluence: page title, attachment names, etc.
- Gathering Interest
-
CONFSERVER-3036 Allow search for words and phrases with non-letter symbols: plus (+), minus (-), period (.), dollar sign ($), asterisk (*), etc.
- Gathering Interest
- relates to
-
AI-891 Provide ability to override Lucene tokenisation and stemming and search for exact text
- Short Term Backlog
- mentioned in
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...