lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hoss Man (JIRA)" <>
Subject [jira] Commented: (LUCENE-998) BooleanQuery.setMaxClauseCount(int) is static
Date Sat, 15 Sep 2007 00:35:32 GMT


Hoss Man commented on LUCENE-998:

One of the reasons this is static is so that any when any query rewrites itself to a BooleanQuery
the max clause count can take effect -- this is really the only situation where the max clause
count is important -- if BooleanQueries were only ever being constructed by client code, the
clinet could stop when they want.

adding this is a setting on an IndexSearcher wouldn't work -- the IndexSearcher is ot involved
in rewriting ... i suppose it could be moved to the IndexReader class (which is involved in
rewriting) but frankly if someone was going to bother changing this, it might make more sense
if the various classes that rewrite to BooleanQuery all had their own seperate setter for
this (so when a new WildCardQuery is constructed, you tell thta object how big it's allowed
to get when it rewrites itself)

> BooleanQuery.setMaxClauseCount(int) is static
> ---------------------------------------------
>                 Key: LUCENE-998
>                 URL:
>             Project: Lucene - Java
>          Issue Type: Bug
>          Components: Search
>    Affects Versions: 2.1
>            Reporter: Tim Lebedkov
> 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 is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message