I'm not sure if I getting the meaning of omit_term_freq_and_positions
option for string fields correctly. In my understanding, setting this
option to true will skip terms frequencies estimation during document
indexing and also terms positions analysis during search scoring.
Please, correct me if I'm wrong.
If I got option's meaning correctly, then it's worth to use it for
fields that will be used for filtering only, like usernames,
categorical values, etc. Is that true?
That is correct. You can see this same thing in Lucene/Solr and in
Solr, which has the notion of an index schema and field types, you can
see that this option is enabled for "string" type by default, which is
what one tends to use for fields that can be used for filtering, where
the term frequency and their position doesn't play a role.
I'm not sure if I getting the meaning of omit_term_freq_and_positions
option for string fields correctly. In my understanding, setting this
option to true will skip terms frequencies estimation during document
indexing and also terms positions analysis during search scoring.
Please, correct me if I'm wrong.
If I got option's meaning correctly, then it's worth to use it for
fields that will be used for filtering only, like usernames,
categorical values, etc. Is that true?
Apache, Apache Lucene, Apache Hadoop, Hadoop, HDFS and the yellow elephant
logo are trademarks of the
Apache Software Foundation
in the United States and/or other countries.