On 10/27/2011 9:14 PM, Erick Erickson wrote:
Well, this could be explained if your fields are very short. Norms
are encoded into (part of?) a byte, so your ranking may be unaffected.
Try adding debugQuery=on and looking at the explanation. If you've
really omitted norms, I think you should see c
On Fri, Oct 28, 2011 at 12:20 AM, Robert Muir wrote:
> On Thu, Oct 27, 2011 at 6:00 PM, Simon Willnauer
> wrote:
>> we are not actively removing norms. if you set omitNorms=true and
>> index documents they won't have norms for this field. Yet, other
>> segment still have norms until they get merg
Well, this could be explained if your fields are very short. Norms
are encoded into (part of?) a byte, so your ranking may be unaffected.
Try adding debugQuery=on and looking at the explanation. If you've
really omitted norms, I think you should see clauses like:
1.0 = fieldNorm(field=features, d
On Thu, Oct 27, 2011 at 6:00 PM, Simon Willnauer
wrote:
> we are not actively removing norms. if you set omitNorms=true and
> index documents they won't have norms for this field. Yet, other
> segment still have norms until they get merged with a segment that has
> no norms for that field ie. omit
we are not actively removing norms. if you set omitNorms=true and
index documents they won't have norms for this field. Yet, other
segment still have norms until they get merged with a segment that has
no norms for that field ie. omits norms. omitNorms is anti-viral so
once you set it to true it wi
As far as I know there's no issue about this. You have to reindex and that's
it.
In which kind of field are you changing the norms? (You just will see
changes in text fields)
Using debugQuery=true you can see how norms affect the score (in case you
have them not omited)
--
View this message in con
