: > omitNorms let's you not use field norms for certain field when : > calculating document matching score. This can save you some RAM.
: Thanks. What eddect does this have on the quality of the returned : matches? Are there any guidelines as to when you would disable field : norms, and on which type of fields? it depends on how you define quality .. if you want length to be a factor in scoring, you need norms. if you want index time field or doc boosts to be a factor, you need norms -- if you have fields where you don't care baout those things, or where you explicilty *don't* want them to be a factor, you omit them, and you index (and RAM usage) get small as a bonus. : > http://lucene.apache.org/java/docs/api/org/apache/lucene/analysis/Token.html#setPositionIncrement(int) : > , it is described pretty well there. : : Right - so whereas in most cases it is set to 100, in fact a number of 5 : or so would be plenty, is that correct? In fact, isn't it more-ore-less : a boolean switch? it depends on the Analyzers you use and how sloppy you tend to make your Phrase or PanNear queries ... a value of 5 menas that if you did a sloppy query for "brown cow"~20 you could concievably match brown in one field value and cow in another ... but with a gap of 100 that would not happen. -Hoss
