Dear Wiki user, You have subscribed to a wiki page or wiki category on "Solr Wiki" for change notification.
The "FieldOptionsByUseCase" page has been changed by ChrisHarris. The comment on this change is: Clarifying highlighter options. http://wiki.apache.org/solr/FieldOptionsByUseCase?action=diff&rev1=10&rev2=11 -------------------------------------------------- ||sort on field ||`true` || ||`false` ||`true` [1] || || || || ||use field boosts || || || ||`false` || || || || ||document boosts affect searches within field || || || ||`false` || || || || - ||highlighting ||`true`[4] ||`true` || || ||[2] ||`true` [3] || || + ||highlighting ||`true`[3] ||`true` || || ||[2] || [2] || [2] || ||faceting ||`true` || || || || || || || ||add multiple values, maintaining order || || ||`true` || || || || || ||field length affects doc score || || || ||`false` || || || || - ||MoreLikeThis || ||true[6]|| || ||`true`[6] || || || + ||MoreLikeThis || ||true[5]|| || ||`true`[5] || || || - ||term frequency[5] || || || || ||`true` || || || + ||term frequency[4] || || || || ||`true` || || || - ||document frequency[5] || || || || ||`true` || || || + ||document frequency[4] || || || || ||`true` || || || - ||tf*idf[5] || || || || ||`true` || || || + ||tf*idf[4] || || || || ||`true` || || || - ||term postitions[5] || || || || ||`true` ||`true` ||`true` || + ||term postitions[4] || || || || ||`true` ||`true` ||`true` || - ||term offsets[5] || || || || ||`true` ||`true` ||`true` || + ||term offsets[4] || || || || ||`true` ||`true` ||`true` || @@ -25, +25 @@ Notes: 1. ''recommended but not necessary'' + 1. stored must always be true for highlighting. If you also add both termVectors and termOffsets, this can be used to boost performance. (Without termVectors/termOffsets, Solr needs to reanalyze the whole document to perform highlighting.) If you furthermore add termPositions, additional speedup may be possible. - 1. ''will be used if present, but not necessary'' - 1. ''if `termVectors=true, then use them. If not present, highlighting will reanalyze the document`'' 1. ''a tokenizer must be defined for the field, but it doesn't need to be indexed'' 1. ''For use with the TermVectorComponent'' 1. Uses the term vector if present, otherwise the stored field. Reanalyzes the document if using the stored field.
