java-dev@lucene.apache.org
[Top] [All Lists]

Re: svn commit: r332747 - in /lucene/java/trunk: ./ src/java/org/apache/

Subject: Re: svn commit: r332747 - in /lucene/java/trunk: ./ src/java/org/apache/lucene/search/regex/ src/test/org/apache/lucene/search/regex/
From: Yonik Seeley
Date: Wed, 16 Nov 2005 10:14:56 -0500
If that's the way to go, we should do it by default so the user doesn't have to.

Unless the scores between two types of queries are compatible, It's a
bad idea to transparently switch between them since it will cause
relevancy to unpredictably change in the future (triggered by either a
query changing slightly, or the index changing slightly).

-Yonik
Now hiring -- http://forms.cnet.com/slink?231706

On 11/16/05, Paul Elschot <paul.elschot@xxxxxxxxx> wrote:
> Why not leave that decision to the program using the query?
> Something like this:
> - catch the TooManyClauses exception,
> -  adapt (the offending parts of) the query to make these use
>    a FieldNormQuery,
> - retry with a warning to the provider of the query that
>   the term frequencies have been ignored.
>
> The only disadvantage of this is that the term expansion
> during rewrite has to be redone.
> Also, when enough terms are involved, they might still cause
> a memory problem because they are all needed at the same
> time.
>
> Regards,
> Paul Elschot

---------------------------------------------------------------------
To unsubscribe, e-mail: java-dev-unsubscribe@xxxxxxxxxxxxxxxxx
For additional commands, e-mail: java-dev-help@xxxxxxxxxxxxxxxxx

<Prev in Thread] Current Thread [Next in Thread>