Hi all,
While attempting to use highlighter with lucene 2.3.2 to get the result similar
to that of google response am getting the following error.
Kindly give me a solution for this problem or provide me an alternate coding
methodology if this s ultimately wrong. I couldnt find out where am
Hi,
If I search for string "A B" (i.e. A followed by a space followed by B) and I
get 20 hits, then is it correct to expect that if I search for "A" (i.e. only
A), I will get at least 20 hit or more? Similarly for if I search for B, I will
get 20 hits or more?
--Hrishi
DISCLAIMER
==
T
> I suppose you could precompute the proximity associations by indexing
> n-grams (in this case, called Lucene calls them shingles), such that there
> is a single token in your index containing cheese_sandwich (effectively)
>
>
doh, I see Grant already lead you in this direction. (sorry for the
dup
yet another thing to look into that might improve things a bit is using
ShingleFilter in contrib.
this way cheese sandwich would form a shingle of "cheese sandwich" and would
get a higher score for the "Toasted Cheese Sandwich" document.
it wouldn't solve the proximity problem in general, but may
Hi Joel,
You could index every possible word combination in your document text, with one
field for each possible distance. (You would have to write an index-time
analyzer to do this, since AFAIK nothing like this exists currently. Shingles
wouldn't work, since you want to ignore intervening t
Any hint or lead on this issue. What else to be taken care?
- Original Message -
From: "Ganesh"
To:
Sent: Friday, October 30, 2009 4:01 PM
Subject: UpdateDocument failed
Hello all,
I am using Lucene 2.4.1. I am adding and updating the documents frequently. At
constant interval, I am
On Oct 30, 2009, at 5:49 AM, Joel Halbert wrote:
Hi,
Without using a proximity search i.e. "cheese sandwich"~5
What's the best way of up-scoring results in which the search terms
are
closer to each other?
I'm not aware of any query technique to score based on proximity that
doesn't, it
My vote is for option A. It's generally implied that a major version brings
in major changes (api as well as others), while the minor is, well, minor.
Why should that be broken for lucene? It would become increasingly difficult
for the lucene user community to catch up if they skipped one or two mi
Hi all,
Am using lucene 2.3.2
I would like to have the search result similar to that of the google response.
On my study i found that highlighter could do this. I found the highlighter
class available in the contrib folder of lucene 2.3.2 .zip.
But am blind about using it to get the desired re
Hello all,
I am using Lucene 2.4.1. I am adding and updating the documents frequently. At
constant interval, I am reopening the index and warming it. I am having
multiple thread, all are sharing a single writer and reader. Commit and
reopening the reader is done in separate thread at regular in
Hi,
Without using a proximity search i.e. "cheese sandwich"~5
What's the best way of up-scoring results in which the search terms are
closer to each other?
E.g. so if I search for:
content:cheese content:sandwich
How do you ensure that a document with content:
"Toasted Cheese Sandwich"
scores
The only way to do it is to index a field (self maintained primary key) with
each document and do a deleteDocument (or updateDocument) for each document
before adding it.
Something like
*writer.deleteDocument(new Term("term-key","unique-id"));*
*writer.addDocument(d);*
This should help.
--
Anshum G
12 matches
Mail list logo
