If i'm reading your message correctly, you (and everyone who has replied
so far) have gotten caught in a red herring. While an "explain" on the
results from your queryB will most likely show you that the
fieldNorm is the main differantiator in score between document-153 and
document-244 that'
Karl Wrote:
>
> 2 okt 2008 kl. 14.47 skrev Jimi Hullegård:
>
> > But apparently this setOmitNorms(true) also disables boosting
> > aswell. That is ok for now, but what if we want to use boosting in
> > the future? Is there no way to disable the length normalization
> > while still keeping the boost
2 okt 2008 kl. 14.47 skrev Jimi Hullegård:
But apparently this setOmitNorms(true) also disables boosting
aswell. That is ok for now, but what if we want to use boosting in
the future? Is there no way to disable the length normalization
while still keeping the boost calculation?
You can m
Erick wrote:
>
> Another possibility (and I'm not sure it'll work, but what
> the heck) would
> be
> to create a Filter for active ideas. So rather than add a
> "category:14"
> clause,
> you create a Category14Filter that you send to the query
> along with your
> +type:idea +alltext:betyg clauses.
Another possibility (and I'm not sure it'll work, but what the heck) would
be
to create a Filter for active ideas. So rather than add a "category:14"
clause,
you create a Category14Filter that you send to the query along with your
+type:idea +alltext:betyg clauses. Now, category won't be considered
Erik wrote:
>
> On Oct 2, 2008, at 7:39 AM, Jimi Hullegård wrote:
> > Is it possible to disable the lengthNorm calculation for particular
> > fields?
>
> Yes, use Field#setOmitNorms(true) when indexing.
Ok, thanks. I will just have to look on how to do this the best way (since the
CMS is handling
On Oct 2, 2008, at 7:39 AM, Jimi Hullegård wrote:
Is it possible to disable the lengthNorm calculation for particular
fields?
Yes, use Field#setOmitNorms(true) when indexing.
Erik
-
To unsubscribe, e-mail: [EMAIL P
