Rename min_similarity to fuzziness

[clintongormley]

Now that fuzziness is really an edit_distance of 1 or 2, we should rename min_similarity in the fuzzy, flt and flt_field queries, and fuzzy_min_sim in the query_string and field queries to fuzziness, which is consistent with the match query.

[s1monw]

why don't we just call it edit_distance? that is really what it is?

[clintongormley]

Sure - just for consistency. the use of fuzziness in the match query is probably more self-explanatory than edit_distance

[s1monw]

@clintongormley I really doubt this, fuzziness is a really bad terms since it relates to different things for different people. Like AI / ML people might confuse it with fuzzy logic. We somehow understand it as not_exact but at the end of the day its a edit_distance on a string with a very specific algorithm.

[clintongormley]

OK agreed. But I'd make it max_edits rather than edit_distance (shorter and more accurate). And I'd change fuzzy_prefix_length in query_string and field queries to just prefix_length

[s1monw]

sounds good to me

[uboness]

@clintongormley ++1 on max_edits, I'd also change it on the match query as well

[ankane]

max_edits would be great since as far as I can tell, there is currently no way to specify an absolute value for the edit distance with fuzziness.

[s1monw]

@ankane since 0.90 you can specify the absolute edits ie. 1 or 2 as well as a backwards compatible float [0..1)

[ankane]

@s1monw good to know. Thanks!

[s1monw]

this has actually been fixed here #4082