# Queries without fully qualified field names failing in the latest versions of Elasticsearch

**URL:** <https://discuss.elastic.co/t/queries-without-fully-qualified-field-names-failing-in-the-latest-versions-of-elasticsearch/254958>\
**Category:** Elasticsearch\
**Created:** [November 10, 2020, 5:59pm UTC](https://discuss.elastic.co/t/queries-without-fully-qualified-field-names-failing-in-the-latest-versions-of-elasticsearch/254958 "2020-11-10T17:59:56Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![Bhargav\_Balu](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/bhargav_balu/32/77183_2.png) [@Bhargav\_Balu](https://discuss.elastic.co/u/Bhargav_Balu)\
**Post date:** [November 10, 2020, 5:59pm UTC](https://discuss.elastic.co/t/queries-without-fully-qualified-field-names-failing-in-the-latest-versions-of-elasticsearch/254958/1 "2020-11-10T17:59:56Z")

</div>

Hi,

We are currently running Elasticsearch 1.4 and are trying to upgrade to the newer versions 7.x. As part of that effort, we noticed our queries are failing on the latest versions i.e 7.x if the fileds used in queries are not fully qualified. Is it mandatory now to provide fully qualified field names in queries now? I can't find any relevant documentation on this in Breaking changes pages.

Example:

For documents as follows,

```auto
{ 
  "region": "US",
  "manager": { 
    "age": 30,
    "name": { 
      "first": "John",
      "last": "Smith"
    }
  }
}

```

with mapping as follows

```auto
{
  "mappings": {
    "properties": { 
      "region": {
        "type": "keyword"
      },
      "manager": { 
        "properties": {
          "age": { "type": "integer" },
          "name": { 
            "properties": {
              "first": { "type": "text" },
              "last": { "type": "text" }
            }
          }
        }
      }
    }
  }
}

```

the following query was working in 1.4

```auto
{
  "query": {
    "match": {
      "first": {
        "query": "John"
      }
    }
  }
}

```

whereas that's not returning any results in 7.x

7.x works with fully qualified field names as follows

```auto
{
  "query": {
    "match": {
      "manager.name.first": {
        "query": "John"
      }
    }
  }
}

```

Can someone please throw some light on this?

Just fyi, I'm talking about object field types only  
[https://www.elastic.co/guide/en/elasticsearch/reference/current/object.html](https://www.elastic.co/guide/en/elasticsearch/reference/current/object.html) not nested type.

---

<div class="post-metadata">

**Author:** ![aaron-nimocks](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/aaron-nimocks/32/73965_2.png) [@aaron-nimocks](https://discuss.elastic.co/u/aaron-nimocks)\
**Post date:** [November 10, 2020, 7:06pm UTC](https://discuss.elastic.co/t/queries-without-fully-qualified-field-names-failing-in-the-latest-versions-of-elasticsearch/254958/2 "2020-11-10T19:06:27Z")

</div>

I never worked with 1.4 or anything that close but as far back as I remember you need to use `manager.name.first` dot notation now.

---

<div class="post-metadata">

**Author:** ![dadoonet](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/dadoonet/32/137187_2.png) [@dadoonet](https://discuss.elastic.co/u/dadoonet)\
**Post date:** [November 10, 2020, 9:29pm UTC](https://discuss.elastic.co/t/queries-without-fully-qualified-field-names-failing-in-the-latest-versions-of-elasticsearch/254958/3 "2020-11-10T21:29:47Z")

</div>

Yes. It was a bug actually that it was working previously.

That said, you can define a field alias if you don't want to change your queries.

---

<div class="post-metadata">

**Author:** ![Bhargav\_Balu](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/bhargav_balu/32/77183_2.png) [@Bhargav\_Balu](https://discuss.elastic.co/u/Bhargav_Balu)\
**Post date:** [November 11, 2020, 6:53am UTC](https://discuss.elastic.co/t/queries-without-fully-qualified-field-names-failing-in-the-latest-versions-of-elasticsearch/254958/4 "2020-11-11T06:53:59Z")

</div>

Thanks for confirming

---

<div class="post-metadata">

**Author:** ![Bhargav\_Balu](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/bhargav_balu/32/77183_2.png) [@Bhargav\_Balu](https://discuss.elastic.co/u/Bhargav_Balu)\
**Post date:** [November 11, 2020, 6:55am UTC](https://discuss.elastic.co/t/queries-without-fully-qualified-field-names-failing-in-the-latest-versions-of-elasticsearch/254958/5 "2020-11-11T06:55:30Z")

</div>

Thank you for the context and the field alias suggestion. Field aliases greatly simplifies our up-gradation without waiting on the client changes. Thanks for the help.

---

<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:** [December 9, 2020, 6:55am UTC](https://discuss.elastic.co/t/queries-without-fully-qualified-field-names-failing-in-the-latest-versions-of-elasticsearch/254958/6 "2020-12-09T06:55:40Z")

</div>

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