lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Erik Hatcher <e...@ehatchersolutions.com>
Subject Re: svn commit: r332747 - in /lucene/java/trunk: ./ src/java/org/apache/lucene/search/regex/ src/test/org/apache/lucene/search/regex/
Date Tue, 15 Nov 2005 02:04:33 GMT

On 14 Nov 2005, at 18:04, Doug Cutting wrote:

> ehatcher@apache.org 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'm all for that.  Since Yonik volunteered to take the first steps,  
I'll follow his lead in refactoring these queries when he gives the  
word.

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

The downside is scoring closer matches (in say the WildcardQuery)  
would no longer be possible, right?

     Erik


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