Hi,
I'm just migrating our small search customization from Lucene version
2.3 to the current version (3.0.3) and wonder why, in contrast to the
old version, we no longer get the Wildcard Queries (which are default,
since surround the search string with asterisks) highlighted.
We're using the
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
--
e 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 wil
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
h
considering before assuming that
scoring is necessary on wildcard terms.
Best
Erick
On Wed, Jan 26, 2011 at 9:10 AM, Wulf Berschin 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 sc
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:
Hi,
I'm poking in the dark and hope someone has some light...
We have part numbers in technical documentation to retrieve. For now we
have a (long) regular expression to find those in a string. The part
numbers have letters, digits and (redundant) whitespace. Furthermore
authors often used a
with? It's because I also work with technical documentation and we
do exactly, waht you're asking for, but it is XML-data.
On Fri, Jan 28, 2011 at 1:05 PM, Wulf Berschin wrote:
Hi,
I'm poking in the dark and hope someone has some light...
We have part numbers in technical docum
Hi,
for indexing PDF files we have to undo word hyphenation. The basic idea
is simply to remove the hyphen when a new line and a small letter
follows. Of course this approach isnt 100%-foolproofed but checking
against a dictionary wouldnt be as well...
Since we face this problem too when hig
ucene/Solr User Conference, May
25-26, San Francisco
On Fri, Apr 1, 2011 at 11:50 AM, Wulf Berschin wrote:
Hi,
for indexing PDF files we have to undo word hyphenation. The basic idea is
simply to remove the hyphen when a new line and a small letter follows. Of
course this approach isnt 100%-foolp
Hi all,
in our Lucene 3.0.3-based web application when a user clicks on a hit
link the targeted PDF should be opened in the browser with highlighted hits.
For this purpose using the Acrobat Highlight File (Parameter xml, see
http://www.pdfbox.org/userguide/highlighting.html and
http://partne
try {
tokenStream.close();
}
catch (Exception e) {
}
}
}
}
}
Am 10.05.2011 12:32, schrieb Wulf Berschin:
Hi all,
in our Lucene 3.0.3-based web application when a user clicks on a hit
link the targeted PDF should be opened in the browser with hig
12 matches
Mail list logo
