Mailing-List: contact java-user-help@lucene.apache.org; run by ezmlm
Precedence: bulk
Reply-To: java-user@lucene.apache.org
Received-SPF: pass (athena.apache.org: local policy)
Message-ID: <4D40360A.2060706@dosco.de>
Date: Wed, 26 Jan 2011 15:56:10 +0100
From: Wulf Berschin <berschin@dosco.de>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; de;
 rv:1.9.2.13) Gecko/20101207 Thunderbird/3.1.7
MIME-Version: 1.0
To: java-user@lucene.apache.org
Subject: Re: ****SPAM(5.0)**** Re: Highlight Wildcard Queries: Scores
References: <4D3F0B08.5060100@dosco.de>
	<AANLkTintKmG9adL_iNH+7ZxkaoqNRhUgEQMMY3cFjB1+@mail.gmail.com>
	<00ab01cbbcca$b46143c0$1d23cb40$@thetaphi.de>
	<00ac01cbbccb$1438a270$3ca9e750$@thetaphi.de>	<4D3FF23F.5000407@dosco.de>
	<4D402B41.3020307@dosco.de>
 <AANLkTi=_oGHbHfpnhA45wPXmx0FbNXvDRLaTCs84M-dM@mail.gmail.com>
In-Reply-To: <AANLkTi=_oGHbHfpnhA45wPXmx0FbNXvDRLaTCs84M-dM@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 8bit

Hi Erick,

good points, but:

our index is fed with german text. In german (in contrast to english) 
nouns are just appended to create new words. E.g.

Kaffee
Kaffeemaschine
Kaffeemaschinensatzbeh�lter

In our scenario standard fulltext search on "Maschine" shall present all 
of these nouns. That's why we add * before and after on each term.

Of course we provide an option "full words only" which finds none of these.

Since we do not wrap * around words shorter than 4 characters we weren't 
yet faced with the too many clauses exception.

Greetings
Wulf

Am 26.01.2011 15:18, schrieb Erick Erickson:
> It is, I think, a legitimate question to ask whether scoring is worthwhile
> on wildcards. That is,
> does it really improve the user experience? Because the MaxBooleanClause
> gets tripped
> pretty quickly if you add the terms back in, so you'd have to deal with
> that.
>
> Would your users be satisfied with sorting in the case of only searching on
> wildcard characters
> by, say, dates or titles or subjects or.....?
>
> Then just let the scoring work on fields that aren't wildcarded...
>
> This may not be reasonable in your particular case, but it's worth
> considering before assuming that
> scoring is necessary on wildcard terms.
>
> Best
> Erick
>
> On Wed, Jan 26, 2011 at 9:10 AM, Wulf Berschin<berschin@dosco.de>  wrote:
>
>> Now I have the highlighted wildcards but obviously the scoring is lost. I
>> see that a rewrite of the wildcard query produces a constant score query. I
>> added
>>
>> setMultiTermRewriteMethod(MultiTermQuery.SCORING_BOOLEAN_QUERY_REWRITE);
>>
>> to my QueryParser instance but no effect. What's to be done now?
>>
>> Wulf
>>
>>
>>
>> Am 26.01.2011 11:06, schrieb Wulf Berschin:
>>
>>> Thank you Alexander and Uwe, for your help.
>>>
>>> I read Marks explanation but it seems to me that his changes are not
>>> contained in Lucene-3.0.3.
>>>
>>> So I commented out the rewrite, changed QueryTermScorer back to
>>> QueryScorer and now I got the wildcard queries highlighted again.
>>>
>>> Wulf
>>>
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: java-user-unsubscribe@lucene.apache.org
>>> For additional commands, e-mail: java-user-help@lucene.apache.org
>>>
>>>
>>>
>>>
>>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: java-user-unsubscribe@lucene.apache.org
>> For additional commands, e-mail: java-user-help@lucene.apache.org
>>
>>
>


---------------------------------------------------------------------
To unsubscribe, e-mail: java-user-unsubscribe@lucene.apache.org
For additional commands, e-mail: java-user-help@lucene.apache.org