I agree. Let the caller do this, or use a modified query parser that will always do it. If you do not need the scoring information, it should be a constant scoring query to begin with.
-----Original Message----- From: Hoss Man (JIRA) [mailto:[EMAIL PROTECTED] Sent: Saturday, May 27, 2006 2:28 PM To: java-dev@lucene.apache.org Subject: [jira] Commented: (LUCENE-582) Don't throw TooManyClauses exception [ http://issues.apache.org/jira/browse/LUCENE-582?page=comments#action_1241359 4 ] Hoss Man commented on LUCENE-582: --------------------------------- If a user costructs a Query instance that rewrites to a BooleanQuery we have to assume they wanted the scoring factors to come into play -- implicitly falling back to a ConstantScoreQuery implentation is not a good idea -- the user can choose to do that themselves if they catch a TooManyClauses. > Don't throw TooManyClauses exception > ------------------------------------ > > Key: LUCENE-582 > URL: http://issues.apache.org/jira/browse/LUCENE-582 > Project: Lucene - Java > Type: Improvement > Components: Search > Versions: 2.0.0 > Reporter: Eric Jain > Priority: Minor > > I wonder if it would make sense to fall back to a ConstantScoreQuery instead of throwing a TooManyClauses exception? -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
