Mailing-List: contact java-user-help@lucene.apache.org; run by ezmlm
Precedence: bulk
Reply-To: java-user@lucene.apache.org
Received-SPF: pass (nike.apache.org: local policy includes SPF record at
 spf.trusted-forwarder.org)
MIME-Version: 1.0
Date: Mon, 9 Dec 2013 09:41:28 -0800
Message-ID: 
 <CALY=cQBTjgEDcQsmJb4kaiXCn4K2HBVd3uoGnW7HxMLX=n4smg@mail.gmail.com>
Subject: Changing similarity at query time
From: Ivan Brusic <ivan@brusic.com>
To: java-user@lucene.apache.org
Content-Type: multipart/alternative; boundary=001a11c2b6407a5fa504ed1d8145

--001a11c2b6407a5fa504ed1d8145
Content-Type: text/plain; charset=ISO-8859-1

I am currently using document-level boosts, which really translates to
changing the norm for every field under the covers. As part of an
experiment, I want to remove the boost, but that would require either
re-indexing content or changing the scoring algorithm (similarity).

If I create my own similarity, which would be identical to the
default/TFIDF similarity but with the norm hardcoded to 1.0. The Lucene
source warns against such behavior. I am assuming this is because it
appears computeNorm is only run at index time,but shouldn't I be able to
override score() and ignore the decodeNormValue calculation?

Cheers,

Ivan

--001a11c2b6407a5fa504ed1d8145--