[
https://issues.jboss.org/browse/ISPN-6728?page=com.atlassian.jira.plugin....
]
Adrian Nistor commented on ISPN-6728:
-------------------------------------
Another possible workaround is to execute a script or server task that invokes
BooleanQuery.setMaxClauseCount setting a higher value. There is however a slight chance
that will not work as expected because a different classloader might be used for query
module than for the executing task, so the static field being set does not affect the
value seen by query module, but it is still worth trying it. I haven't yet, so cannot
confirm it's a sure workaround.
Add ability to override maxClauseCount
---------------------------------------
Key: ISPN-6728
URL:
https://issues.jboss.org/browse/ISPN-6728
Project: Infinispan
Issue Type: Enhancement
Components: Remote Querying, Server
Reporter: Van Halbert
Priority: Minor
We are using the Hotrod client, and need the ability to specify or override the
maxClauseCount setting, otherwise, we get the following error message:
- org.apache.lucene.search.BooleanQuery$TooManyClauses: maxClauseCount is set to 1024
setting
This will occur when there are more than 1024 "IN" conditions specified on the
query builder.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)