[
https://issues.apache.org/jira/browse/LUCENE-998?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15793976#comment-15793976
]
Trejkaz commented on LUCENE-998:
--------------------------------
Won't fix? I was about to file this one.
I don't think this setting should be static, because we have another library on
our classpath which uses Lucene, and we hit a situation where we were calling
it but they were setting it back to something else. So now we have to call it
after they call it, but are you fricking serious? That is not a solution, and
people who introduce mutable static fields should feel bad for what they have
done.
> BooleanQuery.setMaxClauseCount(int) is static
> ---------------------------------------------
>
> Key: LUCENE-998
> URL: https://issues.apache.org/jira/browse/LUCENE-998
> Project: Lucene - Core
> Issue Type: Bug
> Components: core/search
> Affects Versions: 2.1
> Reporter: Tim Lebedkov
> Attachments: lucene-998.patch
>
>
> BooleanQuery.setMaxClauseCount(int) is static. It does not allow searching in
> multiple indices from different threads using different settings. This
> setting should be probably moved in to the IndexSearcher.
--
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
