r [mailto:u...@thetaphi.de]
> Sent: Wednesday, January 26, 2011 5:34 PM
> To: java-user@lucene.apache.org
> Subject: RE: Highlight Wildcard Queries: Scores
>
> You can always decompose because QueryParser will also decompose and
> will do-the-right-thing (internal using a Ph
-
> From: Wulf Berschin [mailto:bersc...@dosco.de]
> Sent: Wednesday, January 26, 2011 5:07 PM
> To: java-user@lucene.apache.org
> Subject: Re: Highlight Wildcard Queries: Scores
>
> Hallo Uwe,
>
> yes, thanks for the hint, that sounds good, but it seems to me I would
the
men
http://www.thetaphi.de
eMail: u...@thetaphi.de
-Original Message-
From: Wulf Berschin [mailto:bersc...@dosco.de]
Sent: Wednesday, January 26, 2011 3:56 PM
To: java-user@lucene.apache.org
Subject: Re: SPAM(5.0) Re: Highlight Wildcard Queries: Scores
Hi Erick,
good points, but:
o: java-user@lucene.apache.org
> Subject: Re: ****SPAM(5.0)**** Re: Highlight Wildcard Queries: Scores
>
> 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 word
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
sco.de]
> Sent: Wednesday, January 26, 2011 3:24 PM
> To: java-user@lucene.apache.org
> Subject: Re: Highlight Wildcard Queries: Scores
>
> Sorry for bothering, that was my fault: I my subclass of QueryParser which
> wraps * around the terms I had not yet considered the new
> mu
Sorry for bothering, that was my fault: I my subclass of QueryParser
which wraps * around the terms I had not yet considered the new
multiTermRewriteMethod. After adding these scoring seems to work and
even the rewrite is possible again.
Wulf
Am 26.01.2011 15:10, schrieb Wulf Berschin:
Now I
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 s
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?
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
--
Removing redundant calls to rewrite was the key when I had this issue
moving from 2.3.x to 3.0.x...
Dawn
On 25/01/2011 20:04, Uwe Schindler wrote:
And: you don't need to rewrite queries before highlighting, highlighter does
this automatically internally if needed.
-
Uwe Schindler
r [mailto:u...@thetaphi.de]
> Sent: Tuesday, January 25, 2011 9:02 PM
> To: java-user@lucene.apache.org
> Subject: RE: Highlight Wildcard Queries
>
> You can set setExpandMultiTermQuery(true) on QueryScorer (or
> WeightedSpanTermExtractor), which is needed by the Highlighter CTOR -
> tha
...@thetaphi.de
> -Original Message-
> From: Alexander Kanarsky [mailto:kanarsky2...@gmail.com]
> Sent: Tuesday, January 25, 2011 8:44 PM
> To: java-user@lucene.apache.org
> Subject: Re: Highlight Wildcard Queries
>
> Hi Wulf,
>
> Check the http://www.lucidimagination.c
Hi Wulf,
Check the
http://www.lucidimagination.com/blog/2009/06/08/bringing-the-highlighter-back-to-wildcard-queries-in-solr-14/
this may help. I do not know what of Mark's changes are in Lucene 3.x,
but most likely you
will just need to set a proper RewriteMethod for the MultiTermQuery somewhere
14 matches
Mail list logo
