It seems that you don't the length norm to be used. It's a factor which
normalize the score of a doc depending on the size of the searched field
of the doc. It's the field which make that 'ground ice' has a higher
score than 'ice hockey: British Sekonda Superleague Play-Off
Championship:
It can safely be removed.I am pretty sure it happens during merging on fields that
don't have term vector information included. Of course, the real fix is to not
attempt to not even call this method when there is not term vector info.
It is normal, for now. Should probably be removed,
Hi Frank,
Thanks for the suggestion. I would try that and let you know.
Regards,
Niraj
- Original Message -
From: Brisbart Franck [EMAIL PROTECTED]
To: Lucene Users List [EMAIL PROTECTED]
Sent: Monday, June 07, 2004 12:50 PM
Subject: Re: score and frequency
It seems that you don't
Jayant Kumar wrote:
Thanks for the patch. It helped in increasing the
search speed to a good extent.
Good. I'll commit it. Thanks for testing it.
But when we tried to
give about 100 queries in 10 seconds, then again we
found that after about 15 seconds, the response time
per query increased.
Does it ever make sense to set the Similartity obj in either (only one
of..) IndexWriter or IndexSearcher? i.e. If I set it in IndexWriter can
I avoid setting it in IndexSearcher? Also, can I avoid setting it in
IndexWriter and only set it in IndexSearcher? I noticed Nutch sets it in
both
All,
I've just released a new candidate (*1.0-rc3*) that now supports
plugins. You can create your own extractors
for various file formats. I've provided Extractors for Text, PDF, Word,
and HTML.
It's also possible to specify your own handlers for archives. Say you
have a RAR archive, and you
I had been using 1.3 final for 1 month, everything was ok. A week ago, i changed 1.3
final to 1.4 rc2, added sort when searching ,then errors below occurs. Why is that?
What changed in release 1.4 ? Thanks a lot!
java.lang.NullPointerException
at
