cancel
Showing results for 
Search instead for 
Did you mean: 

Error 'maxClauseCount is set to 10000' when i do s

ribz33
Champ on-the-rise
Champ on-the-rise
Hi,

i have an alfresco with average 200 documents inside.
My search max results in my web-client-config-custom is 500.

When i do search "***" on all repository i have this error :
Search failed due to system error: maxClauseCount is set to 10000

Someone already see this error ?
Have you an idea what happen ?
5 REPLIES 5

gavinc
Champ in-the-making
Champ in-the-making
This error occurs if the query has returned too many results for lucene to handle.

Searhcing for "***" will undoubtedly return pretty much the whole repository!

To change this value, it's referenced in core-services-context.xml via the 'lucene.query.maxClauses' property, which in turn can be found in repository.properties. You could therefore override this value in your custom repository.properties file.

ribz33
Champ on-the-rise
Champ on-the-rise
Thanks for help.

Its strange because i have less than 300 documents and i reach 10000 results on Lucene.
I dont understand how i can reach 10000 results with only 300 docs ?

mikef
Champ in-the-making
Champ in-the-making
The search is going to return everything in your repository, not just documents. That may be why you are getting a larger number of matches than you expect.

andy
Champ on-the-rise
Champ on-the-rise
Hi

The 10000 limit is the number of tokens that match the wildcard query not the number of docs found.

Andy

ragnaroek-hh
Champ in-the-making
Champ in-the-making
We migrated with about 2000 docs in the repository to alfresco 4.2.c.

we use lucene indexing.

Within the alfresco explorer, adding ressources in all workflow start tasks now is failing due to maxClauseCount limit - as above.

Surprisingly we had to increase this value from 10.000 to 1000.0000 in order to continue…

I wonder what happened.

Might this relate to the fact, that our customer workflows have more than 100 workflow definitions since each server restart in the past unfortunately caused re-deployment of all workflows? May be this generated high number of tokens for the wildcard query which is generated on ressource update searches…