[ http://issues.apache.org/jira/browse/LUCENE-383?page=comments#action_12373843 ]
Nadav Har'El commented on LUCENE-383: ------------------------------------- Hi, It appears that ConstantScoreRangeQuery is already in the trunk. However, QueryParser still uses RangeQuery, not ConstantScoreRangeQuery. Should this issue be closed? Or are you still intending to change QueryParser to use the new class? > ConstantScoreRangeQuery - fixes "too many clauses" exception > ------------------------------------------------------------ > > Key: LUCENE-383 > URL: http://issues.apache.org/jira/browse/LUCENE-383 > Project: Lucene - Java > Type: Bug > Components: Search > Versions: 1.4 > Environment: Operating System: other > Platform: Other > Reporter: Yonik Seeley > Assignee: Lucene Developers > Attachments: ConstantScoreQuery.java, ConstantScoreQuery.java, > ConstantScoreRangeQuery.java, ConstantScoreRangeQuery.java, > TestConstantScoreRangeQuery.java > > ConstantScoreQuery wraps a filter (representing a set of documents) and > returns > a constant score for each document in the set. > ConstantScoreRangeQuery implements a RangeQuery that works for any number of > terms in the range. It rewrites to a ConstantScoreQuery that wraps a > RangeFilter. > Still needed: > - unit tests (these classes have been tested and work fine in-house, but the > current tests rely on too much application specific code) > - code review of Weight() implementation (I'm unsure If I got all the score > normalization stuff right) > - explain() implementation > NOTE: requires Java 1.4 for BitSet.nextSetBit() -- 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]
