By default the sqlite3 parser used by MaxScale has a recursion depth of 1000. This means e.g. that the maximum number of comparisons in a WHERE clause is 1000. The limit has now been raised to 25000, which is far more than needed by the statement in this issue.
There has to be a limit, as otherwise a WHERE clause with a sufficient number of comparisons will cause a stack overflow and MaxScale crash.

The limit will be lowered to 4096, which is still more than enough for the case in this issue. Originally it was changed to 25000, which is fine in a regular Linux environment. However, if MaxScale is running in a constrained container environment, with an expression depth of 25000 a pathological statement may cause MaxScale to run out of memory and crash. 4096 seems like a good compromise.