very well explained. However, you dont know the number (integer/float) field
value of a matched in advance. So even suppose the Similarity field is
constructed, how to use it in the query?
--
View this message in context:
http://lucene.472066.n3.nabble.com/Similarity-of-numbers-in
: I didn't realize that subsets were used to evaluate similarity. From your
: example, I assume that the strings: 456 and 123456 are "similar". If I store
: them as integers instead of strings, will Solr/Lucene still use subsets to
: assign similarity?
Strictly speaking MLT opperates on "Terms" .
I didn't realize that subsets were used to evaluate similarity. From your
example, I assume that the strings: 456 and 123456 are "similar". If I store
them as integers instead of strings, will Solr/Lucene still use subsets to
assign similarity?
--
View this message in context:
http://www.nabbl
The problem is the concept of "similarity". Your concept of similarity
is based on the meaning of the numbers (or the words). Solr's concept of
similarity is based on subsets of characters. This way for Solr
"thunder" is similar to "thunderstorm" or to "under" because there are
sets of characte
I stored 2 copies of a single field: one as a number, the other as a string.
The MLT handler returned the same documents regardless of which of the 2
fields I used for similarity. So to answer my own question, the
MoreLikeThisHandler does not do numeric comparisons on numeric fields.
--
View this
I have a numeric field that I'm using for getting more records like the
current one. Does the MoreLikeThisHandler do numeric comparisons on numeric
fields (e.g. 4 is "similar" to 5), or is it a string comparison?
--
View this message in context:
http://www.nabble.com/%22Similarity%22-of-numbers-
