# Did fuzziness change with Elasticsearch 2?

**URL:** <https://discuss.elastic.co/t/did-fuzziness-change-with-elasticsearch-2/39302>\
**Category:** Elasticsearch\
**Created:** [January 15, 2016, 5:52am UTC](https://discuss.elastic.co/t/did-fuzziness-change-with-elasticsearch-2/39302 "2016-01-15T05:52:00Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![davidbkemp](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/davidbkemp/32/594_2.png) [@davidbkemp](https://discuss.elastic.co/u/davidbkemp)\
**Post date:** [January 15, 2016, 5:52am UTC](https://discuss.elastic.co/t/did-fuzziness-change-with-elasticsearch-2/39302/1 "2016-01-15T05:52:00Z")

</div>

Was there supposed to be a change in the behaviour of fuzzy matching between Elasticsearch 1.7 and 2.1?

A match query with fuzziness of "1" in Elasticsearch 2 will match transposed adjacent characters, but didn't in Elasticsearch 1.

E.g.  
POST /foo/foo/1  
{"text": "ab"}

GET /foo/foo/\_search  
{ "query": {"match": {"text": {"query": "ba", "fuzziness": 1}}}}

In Elasticsearch 1.7, the query did not match "ab", but it does match in 2.1

---

<div class="post-metadata">

**Author:** ![mikemccand](https://avatars.discourse-cdn.com/v4/letter/m/f04885/32.png) [@mikemccand](https://discuss.elastic.co/u/mikemccand)\
**Post date:** [January 19, 2016, 4:03pm UTC](https://discuss.elastic.co/t/did-fuzziness-change-with-elasticsearch-2/39302/2 "2016-01-19T16:03:37Z")

</div>

Yes, the default for `fuzzy_transpositions` changed from `false` to `true` in [https://github.com/elastic/elasticsearch/issues/9278](https://github.com/elastic/elasticsearch/issues/9278)

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\
**Post date:** [July 5, 2017, 11:23pm UTC](https://discuss.elastic.co/t/did-fuzziness-change-with-elasticsearch-2/39302/3 "2017-07-05T23:23:24Z")

</div>