# Multi match returns 1 of 2 available matches

**URL:** <https://discuss.elastic.co/t/multi-match-returns-1-of-2-available-matches/232510>\
**Category:** Elasticsearch\
**Created:** [May 13, 2020, 8:30pm UTC](https://discuss.elastic.co/t/multi-match-returns-1-of-2-available-matches/232510 "2020-05-13T20:30:40Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![ghost1face](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/ghost1face/32/68835_2.png) [@ghost1face](https://discuss.elastic.co/u/ghost1face)\
**Post date:** [May 13, 2020, 8:30pm UTC](https://discuss.elastic.co/t/multi-match-returns-1-of-2-available-matches/232510/1 "2020-05-13T20:30:40Z")

</div>

Hello, I've been using elastic and have recently run into a puzzling issue. I've got two records with the same first and last name and when I use a phrase prefix query for last name, only 1 returns:

```auto
{
  "query": {
    "bool": {
      "must": [
        {
          "multi_match": {
            "fields": [
              "lastName"                            
            ],
            "query": "BALL",
            "type": "phrase_prefix"
          }
        }
      ]
    }
  }
}

```

Running the above query returns 1 of 2 records "BASE BALL". (Both records have the same first name: BASE and last name: BALL)

If I include `max_expansions: 70` instead of the default 50, both records return. This is puzzling because they have the exact same last name in my test environment so I would expect them both to return without having to toggle `max_expansions``lastName` is a `text` field.

Has anyone run into this before or have a good explanation for this?

---

<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:** [June 10, 2020, 8:30pm UTC](https://discuss.elastic.co/t/multi-match-returns-1-of-2-available-matches/232510/2 "2020-06-10T20:30:40Z")

</div>

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.