lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Michael McCandless (JIRA)" <j...@apache.org>
Subject [jira] Commented: (LUCENE-998) BooleanQuery.setMaxClauseCount(int) is static
Date Wed, 11 Mar 2009 11:43:02 GMT

    [ https://issues.apache.org/jira/browse/LUCENE-998?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12680846#action_12680846
] 

Michael McCandless commented on LUCENE-998:
-------------------------------------------

Timeout collector is an interesting approach, though it's not great because you will have
spent XXX cpu only to determine you shouldn't have attempted the query in the first place.
 Whereas the maxClauseCount spends less CPU deciding to abort, though it is spooky that multi
term queries, when rewriting, use MutiReader.terms(), which in LUCENE-1483 we found to be
disastrously slow in certain, not fully understood situations.


> BooleanQuery.setMaxClauseCount(int) is static
> ---------------------------------------------
>
>                 Key: LUCENE-998
>                 URL: https://issues.apache.org/jira/browse/LUCENE-998
>             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: java-dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: java-dev-help@lucene.apache.org


Mime
View raw message