-
Suggestion
-
Resolution: Won't Fix
-
None
NOTE: This suggestion is for Confluence Cloud. Using Confluence Server? See the corresponding suggestion.
Problem Definition:
Currently if their are wildcard searches, we could exceed the maxClauseCount and this is a limitation of lucene. Instead of finishing the search, the following error is thrown:
2010-02-16 17:56:43,996 WARN [http-8080-Processor8] [search.v2.lucene.LuceneSearcherImpl] search Error encounterd in lucene search: maxClauseCount is set to 1024
-- referer: http://example.com:8080/dosearchsite.action?queryString=item+-blah.*&where=conf_all&type=&lastModified=&contributor=&contributorUsername= | url: /dosearchsite.action | userName: USERNAME | action: dosearchsite
This is especially prevalent if Confluence has a number of auto generated pages. For example if you have a wildcard search with more than 1024 pages, it will exceed the max clause count of 1024.
Suggested Resolution
If we could pass a system property to change the maxClauseCount, we would be able to avoid these issues for some customers who have an idea of what they need to set their maxClauseCount to.
- is related to
-
CONFSERVER-18824 Make the maxClauseCount configurable
- Gathering Interest