I'm in favor of that... I think it's fine to eliminate most of the relevancy factors (like idf(), tf(), etc) from range and wildcard type queries. The biggest drawback is that index time boosts are disabled, but I think having queries that can work 100% of the time is more important.
I'll work on updating the ConstantScoreRangeQuery tests that Chris added and then get ConstantScore & ConstantScoreRangeQuery committed. After that, a filter with a TermEnum constructor should be simple enough and handle a lot of cases. On 11/14/05, Doug Cutting <[EMAIL PROTECTED]> wrote: > [EMAIL PROTECTED] wrote: > > +23. Added regular expression queries, RegexQuery and SpanRegexQuery. > > + Note the same term enumeration caveats apply with these queries as > > + apply to WildcardQuery and other term expanding queries. > > + (Erik Hatcher) > > I don't like adding more error-prone stuff like this. Giving folks > something that sounds really useful but blows up in many cases is not a > good idea. We should fix all of these before we add more, no? > > I would be in favor of converting all of the term-expanding queries to > be constant-scoring. A filter class could easily be implemented that > takes a FilteredTermEnum. Combine this with ConstantScoreQuery (from > http://issues.apache.org/jira/browse/LUCENE-383) to re-implement each > term-expanding query class. What do others think? > > Doug -Yonik Now hiring -- http://forms.cnet.com/slink?231706 --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
