# Field type conflict where indices with conflicting type do not exist

**URL:** <https://discuss.elastic.co/t/field-type-conflict-where-indices-with-conflicting-type-do-not-exist/288788>\
**Category:** Kibana\
**Created:** [November 9, 2021, 4:15pm UTC](https://discuss.elastic.co/t/field-type-conflict-where-indices-with-conflicting-type-do-not-exist/288788 "2021-11-09T16:15:05Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![adamsm](https://avatars.discourse-cdn.com/v4/letter/a/a9adbd/32.png) [@adamsm](https://discuss.elastic.co/u/adamsm)\
**Post date:** [November 9, 2021, 4:15pm UTC](https://discuss.elastic.co/t/field-type-conflict-where-indices-with-conflicting-type-do-not-exist/288788/1 "2021-11-09T16:15:05Z")

</div>

Hi

We run Kibana on AWS. We are seeing Field type conflict on a few fields, see an example image below:

 ![image](https://us1.discourse-cdn.com/elastic/original/3X/4/1/416bf49f1c43b98807b79134a1cc77392fa9f2b9.png)

However we have a stack management policy which has already deleted the conflicting indices in question (those of type `string`).

I have confirmed the indices in question do not exist by running the following:

`GET /log-collector-2021-09-27`

Response:

```auto
{
  "error" : {
    "root_cause" : [
      {
        "type" : "index_not_found_exception",
        "reason" : "no such index [log-collector-2021-09-27]",
        "index_uuid" : "_na_",
        "resource.type" : "index_or_alias",
        "resource.id" : "log-collector-2021-09-27",
        "index" : "log-collector-2021-09-27"
      }
    ],
    "type" : "index_not_found_exception",
    "reason" : "no such index [log-collector-2021-09-27]",
    "index_uuid" : "_na_",
    "resource.type" : "index_or_alias",
    "resource.id" : "log-collector-2021-09-27",
    "index" : "log-collector-2021-09-27"
  },
  "status" : 404
}

```

and

`GET _cat/indices?v`

and then searching for the problematic indices (I have not been able to find them).

I have also tried recreating the indices with the correct field types `long`. However this did not help either.

I am at a loss, does anyone have any ideas?

---

<div class="post-metadata">

**Author:** ![bhavyarm](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/bhavyarm/32/22392_2.png) [@bhavyarm](https://discuss.elastic.co/u/bhavyarm)\
**Post date:** [November 9, 2021, 6:50pm UTC](https://discuss.elastic.co/t/field-type-conflict-where-indices-with-conflicting-type-do-not-exist/288788/2 "2021-11-09T18:50:29Z")

</div>

@mattkime can we please get some help here?  
Thanks,  
Bhavya

---

<div class="post-metadata">

**Author:** ![mattkime](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/mattkime/32/43522_2.png) [@mattkime](https://discuss.elastic.co/u/mattkime)\
**Post date:** [November 9, 2021, 9:02pm UTC](https://discuss.elastic.co/t/field-type-conflict-where-indices-with-conflicting-type-do-not-exist/288788/3 "2021-11-09T21:02:15Z")

</div>

@adamsm Which version of the stack are you running? If you're running a version where you can manually refresh the field list, does refreshing the field list fix the problem?

---

<div class="post-metadata">

**Author:** ![adamsm](https://avatars.discourse-cdn.com/v4/letter/a/a9adbd/32.png) [@adamsm](https://discuss.elastic.co/u/adamsm)\
**Post date:** [November 10, 2021, 7:04am UTC](https://discuss.elastic.co/t/field-type-conflict-where-indices-with-conflicting-type-do-not-exist/288788/4 "2021-11-10T07:04:18Z")

</div>

Hi @mattkime

Thanks so much, we are running v7.10.2 which does have the ability to refresh the field list. This did solve the issue. Much appreciated.

---

<div class="post-metadata">

**Author:** ![mattkime](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/mattkime/32/43522_2.png) [@mattkime](https://discuss.elastic.co/u/mattkime)\
**Post date:** [November 10, 2021, 9:34pm UTC](https://discuss.elastic.co/t/field-type-conflict-where-indices-with-conflicting-type-do-not-exist/288788/5 "2021-11-10T21:34:38Z")

</div>

@adamsm Glad to hear! Newer versions refresh the field list automatically which would have prevented this confusion.

---

<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 8, 2021, 9:34pm UTC](https://discuss.elastic.co/t/field-type-conflict-where-indices-with-conflicting-type-do-not-exist/288788/6 "2021-12-08T21:34:47Z")

</div>

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