lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Doug Cutting (JIRA)" <j...@apache.org>
Subject [jira] Commented: (LUCENE-383) ConstantScoreRangeQuery - fixes "too many clauses" exception
Date Fri, 28 Oct 2005 16:54:56 GMT
    [ http://issues.apache.org/jira/browse/LUCENE-383?page=comments#action_12356221 ] 

Doug Cutting commented on LUCENE-383:
-------------------------------------

Yonik: I'd forgotten about that suggestion, thanks for remembering it!

Hoss: I think there are some nasty details still to be worked out in that suggestion, like
how to cache bitvectors.  Long-term, I think it would be a better approach, but Yonik's ConstantScoreQuery
stuff works well today.

I think fixing common use cases, like range queries, from exploding in people's faces is a
high priority.  So I would argue for changing QueryParser sooner rather than later.  If we
ever implement my proposal then we can deprecate these classes.  The majority of folks just
use QueryParser, and they won't know the difference.


> 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
>
> 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


Mime
View raw message