lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Mark Miller (JIRA)" <>
Subject [jira] Commented: (LUCENE-998) BooleanQuery.setMaxClauseCount(int) is static
Date Wed, 11 Mar 2009 11:07:50 GMT


Mark Miller commented on LUCENE-998:

Ive seen and seen reported, that the constant score version scales *much* better. Which makes
me think the enumeration is not the main problem - on a pretty large index, I've seen the
difference as fairly dramatic - say the boolean version was in the 10-20 seconds range, the
constant score version a couple seconds type of thing.

I do think constant score should be the default eventually.

Longer term, I would hope you never have to limit the number of terms it can hit - perhaps
just use the timeout collector? I have no real argument against this patch, just a string
I am not interested in tugging myself.

> BooleanQuery.setMaxClauseCount(int) is static
> ---------------------------------------------
>                 Key: LUCENE-998
>                 URL:
>             Project: Lucene - Java
>          Issue Type: Bug
>          Components: 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 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