Mailing-List: contact java-dev-help@lucene.apache.org; run by ezmlm
Precedence: bulk
Reply-To: java-dev@lucene.apache.org
Message-ID: <288788815.1131762543124.JavaMail.jira@ajax.apache.org>
Date: Sat, 12 Nov 2005 03:29:03 +0100 (CET)
From: "Hoss Man (JIRA)" <jira@apache.org>
To: java-dev@lucene.apache.org
Subject: [jira] Updated: (LUCENE-383) ConstantScoreRangeQuery - fixes "too
 many clauses" exception
Mime-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

     [ http://issues.apache.org/jira/browse/LUCENE-383?page=all ]

Hoss Man updated LUCENE-383:
----------------------------

    Attachment: TestConstantScoreRangeQuery.java

a Unit test for ConstantScoreRangeQuery ... that was easy to crank out based on the existing BaseTestRangeFilter.

One catch is that the test currently fails: when i tried to prove that the scores were not only constant, but also equaled the boost I couldn't get it to work -- perhaps I have a missunderstanding of how HItCollector works, but I thought that was the safest way to get a "raw" score.

> 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: java-dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: java-dev-help@lucene.apache.org