It looks like 10.5 changed search indexes to include new fields. As a result, our Index has changed from a few hundred fields to a few thousand. The issue is that our search now throws the following:

TooManyClausesException: maxClauseCount is set to 1024

. For the search we're using:

var results = index.Searcher.CreateQuery().NativeQuery(query).Execute();

Is there a recommended way of handling this issue? Should we be using multiple indexes to refine the search? Is there a way to turn of indexing the previously excluded JSON fields from Block Lists?

I'd suggest logging a bug. It's a considerably painful breaking change for an lts. Ideally it would be opt in on v10 and standard on v12 as it's made upgrading not doable for us currently.

Thanks!

Depends how you're doing your search. If you're specifying your search fields it should be under control. I had a similar issue with a search package. Had the same error as you. I rolled my own search in the end, specified the fields and it was fine. It was a multilingual site, if that makes a difference.

We are aware of this issue and are actively working on a way to optout of the new block list indexing. Will try to keep you posted

This is great. We were able to use a workaround found in a closed ticket linked below but this feels like a much better long term solution. Thanks y'all for the help! https://github.com/umbraco/Umbraco-CMS/issues/14096#issuecomment-1508425584

We ran in to this issue the other day and we've had to specifically pick which fields we want to search, a bit of a pain though and means reworking some of our searches. Hopefully a solution other than code rewrite is available soon.

Ideally the changes to the block list /nested content would be reverted as the number of index fields this creates is number of properties that use block lists x the max number of allowed blocks in each block list x the number of properties available on all the available blocks to those lists x the number of languages..