Dear All,
when indexing an object I create a document that contains a field called
title. I set the boost of that field to 60. After the indexing was complete
I checked the document using luke. The norm field for it contained 40.
Shouldn't this column (the field norm) contain the boost that was se
Look at norm(t,d) in the javadocs for Similarity. Note use of the
word "encapsulates". Also note the stuff on loss of precision.
--
Ian.
On Mon, Apr 23, 2012 at 12:11 PM, Akos Tajti wrote:
> Dear All,
>
> when indexing an object I create a document that contains a field called
> title. I set
Thanks, Ian,
I checked the documentation and it turned out that the lengt normalization
made the norm so small. I started using SweetSpotSimilarity for that field
and now the scores are ok.
Ákos
On Mon, Apr 23, 2012 at 1:33 PM, Ian Lea wrote:
> Look at norm(t,d) in the javadocs for Similarit
On Mon, Apr 23, 2012 at 10:31 AM, Jong Kim wrote:
> Is there any good way to solve this design problem? Obviously, an
> alternative design would be to split the index into two, and maintain
> static (and large) data in one index and the other dynamic part in the
> other index. However, this approa
Hi,
Thanks for the fix.
I also wonder if you know any collection (free ones) to test pruning
approaches. Almost all the papers use TREC collections which I don't have!!
For now, I use Reuters21578 collection and Carmel's Kendall's tau extension
to measure similarity. But I need a collection with
Hi all,
(scroll to bottom for question)
I was setting up a simple web app to play around with phonetic filters.
The idea is simple, I just create a document for each word in the
English dictionary, each document containing a single search field
holding the value after it is preprocessed using
Thanks for the reply.
Our metadata is not stored in a single field, but is rather a collection of
fields. So, it requires a boolean search that spans multiple fields. My
understanding is that it is not possible to iterate over the matching
documents efficiently using termDocs() when the search inv
On Mon, Apr 23, 2012 at 1:25 PM, Jong Kim wrote:
> Thanks for the reply.
>
> Our metadata is not stored in a single field, but is rather a collection of
> fields. So, it requires a boolean search that spans multiple fields. My
> understanding is that it is not possible to iterate over the matching
