[ http://issues.apache.org/jira/browse/LUCENE-383?page=comments#action_12374301 ]
Hoss Man commented on LUCENE-383: --------------------------------- I believe (but i'm not certain) that i remember a discusion on java-dev a while back regarding this and that there was some concensus not to make the QueryParser change until 2.0 so as not to affect the scores of existing searches. i could be completely wrong > 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]
