# Fuzzy Aggregations
**URL:** https://discuss.elastic.co/t/fuzzy-aggregations/84067
**Category:** Elasticsearch
**Created:** [April 28, 2017, 10:40pm UTC](https://discuss.elastic.co/t/fuzzy-aggregations/84067 "2017-04-28T22:40:56Z")
**Posts on this page:** 5
**Page:** 1
### Author:  [@Michael\_Sander](https://discuss.elastic.co/u/Michael_Sander)
#### Post date: [April 28, 2017, 10:40pm UTC](https://discuss.elastic.co/t/fuzzy-aggregations/84067/1 "2017-04-28T22:40:57Z")
Elasticsearch supports [fuzzy search queries](https://www.elastic.co/guide/en/elasticsearch/guide/2.x/fuzzy-match-query.html) and [term aggregations](https://www.elastic.co/guide/en/elasticsearch/reference/current/search-aggregations-bucket-terms-aggregation.html).
I am not aware of any way to do fuzzy aggregations, but it would be a great feature. My database deals with names, misspellings are rampant. It would be great if "Brian Smith" was put into the same bucket as "Brain Smith".
If this is not possible today, is it anywhere on the roadmap? Is it even technically feasible?
---
### Author:  [@Mark\_Harwood](https://discuss.elastic.co/u/Mark_Harwood)
#### Post date: [April 29, 2017, 8:11am UTC](https://discuss.elastic.co/t/fuzzy-aggregations/84067/2 "2017-04-29T08:11:41Z")
I've built data linking systems before and a general issue with use of any fuzzy matching on large sets (such as aggregations) is that the iterative nature of linking the data means that little errors get amplified like feedback noise between a pa and mic. 'Mark' might match 'Marc' which might then join with 'Marcy' and then 'Macy'. Entities just snowball.
Each name needs additional context to prevent this. A postcode, a date of birth, a vehicle reg plate. Names on their own are not enough and entities need to hold a rich mix of identifiers for error- free linking. This requires a much more complex system
---
### Author:  [@Michael\_Sander](https://discuss.elastic.co/u/Michael_Sander)
#### Post date: [May 2, 2017, 12:26am UTC](https://discuss.elastic.co/t/fuzzy-aggregations/84067/3 "2017-05-02T00:26:18Z")
Why couldn't it be setup such that: for every entity returned in a bucket, also return all entities that are within 1 edit distance away. That way the bucket "Mark" will catch "Marc", but not "Marcy". However, the bucket "Marc" would also catch "Mark" and "Marcy".
This sounds like a difficult system to build and run at scale, but perhaps possible.
---
### Author:  [@Mark\_Harwood](https://discuss.elastic.co/u/Mark_Harwood)
#### Post date: [May 2, 2017, 7:06am UTC](https://discuss.elastic.co/t/fuzzy-aggregations/84067/4 "2017-05-02T07:06:31Z")
"Jon" would match "Joan" but not "Jonathon"
Name matching is a specialist topic and frequently backed by synonym databases (see [http://www.basistech.com/text-analytics/rosette/name-indexer/](http://www.basistech.com/text-analytics/rosette/name-indexer/) ).
My experience is that effective entity resolution relies on using added context e.g. Zip codes or phone numbers alongside names.
---
### Author:  [@system](https://discuss.elastic.co/u/system)
#### Post date: [May 30, 2017, 7:21am UTC](https://discuss.elastic.co/t/fuzzy-aggregations/84067/5 "2017-05-30T07:21:18Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.