Re: How does Elasticsearch calculate the field-length norm?

Thanks Masaru, so it is the precision loss issue by encoding/decoding. That makes sense. On Friday, March 27, 2015 at 11:04:12 AM UTC+8, Masaru Hasegawa wrote: > > Hi, > > I believe it's because field norm is encoded in single byte. > See >

Re: How does Elasticsearch calculate the field-length norm?

Hi, I believe it's because field norm is encoded in single byte. See  http://lucene.apache.org/core/4_10_2/core/org/apache/lucene/search/similarities/DefaultSimilarity.html Masaru On March 26, 2015 at 14:36:45, Xudong You (xudong@gmail.com) wrote: Per this post "theory behind relevance sc

How does Elasticsearch calculate the field-length norm?

Per this post "theory behind relevance scoring" http://www.elastic.co/guide/en/elasticsearch/guide/current/scoring-theory.html Elasticsearch calculate the field-length norm as follows: norm(d) = 1 / √numTerms But per my testing, seems the actual result value calculated does not meet above f