maxClauseCount exception thrown for a simple model about zentity HOT 2 CLOSED

I think you're right, actually. While I was surprised to see the exception thrown, it turned to be from inputs that were either empty strings or really common matching patterns. I will read the documentation you have linked here. Thanks for the response!

from zentity.

@erewok

Most likely what you're seeing is "snowballing." This happens when the matchers or resolvers are too liberal, causing too many false matches to "snowball" into the result. When there are many false matches, the number of searchable attribute values explodes and the queries become too complex for Elasticsearch to process.

For example, let's say you have a resolver that looks at names and phone numbers, and let's say your data has a thousand documents where the value of the name is "unknown" or "". If your search matches one of those values, then suddenly your resolution job might incorrectly pick up a thousand phone numbers associated with the name "unknown" or "". Then each newly discovered phone number is included as a clause in the next query, which could exceed what Elasticsearch can process.

My recommendations would be:

• Check for common values in your data that might cause snowballing, such as a name whose value is "unknown", and exclude those values from any searches by setting them in "scope"."exclude"."attributes".
• Check to see if your matchers are too liberal. For example, if the names and phone numbers are text fields instead of keyword fields, and if your matchers are using a "match" query instead of a "term" query, then check the analyzers for those text fields. It's possible that the queries are matching tokens instead of the full values, such as just the first names or area codes of the phone numbers, and that could lead to more false matches and snowballing. For example, the name "Jane Smith" and the phone number "555-123-4567" might match "Jane Doe" and "555-555-5555" simply because of the matching tokens "Jane" and "555," which is too generous of a match. If this is happening, consider reindexing your data using a custom text analyzer or keyword normalizer that doesn't tokenize the value.

Some of this is covered in the entity modeling tips section of the documentation.

from zentity.