[ https://issues.apache.org/jira/browse/SOLR-4586?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14298731#comment-14298731 ]
Mark Miller commented on SOLR-4586: ----------------------------------- Technical vetoes don't just stand like a guardian in the road forever. Once someone has withdrawn from helping address the issue or working with a group of people still working down the issue, if they insist on holding a veto, it starts to move to capricious. We can deal with it at the PMC or board level if we have to, but it's not how veto power works. > Eliminate the maxBooleanClauses limit > ------------------------------------- > > Key: SOLR-4586 > URL: https://issues.apache.org/jira/browse/SOLR-4586 > Project: Solr > Issue Type: Improvement > Affects Versions: 4.2 > Environment: 4.3-SNAPSHOT 1456767M - ncindex - 2013-03-15 13:11:50 > Reporter: Shawn Heisey > Attachments: SOLR-4586.patch, SOLR-4586.patch, SOLR-4586.patch, > SOLR-4586.patch, SOLR-4586.patch, SOLR-4586.patch, > SOLR-4586_verify_maxClauses.patch > > > In the #solr IRC channel, I mentioned the maxBooleanClauses limitation to > someone asking a question about queries. Mark Miller told me that > maxBooleanClauses no longer applies, that the limitation was removed from > Lucene sometime in the 3.x series. The config still shows up in the example > even in the just-released 4.2. > Checking through the source code, I found that the config option is parsed > and the value stored in objects, but does not actually seem to be used by > anything. I removed every trace of it that I could find, and all tests still > pass. -- This message was sent by Atlassian JIRA (v6.3.4#6332) --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org