# "no cached mapping for this field"

**URL:** https://discuss.elastic.co/t/no-cached-mapping-for-this-field/255514
**Category:** Kibana
**Created:** [November 16, 2020, 11:45am UTC](https://discuss.elastic.co/t/no-cached-mapping-for-this-field/255514 "2020-11-16T11:45:28Z")
**Posts on this page:** 5
**Page:** 1

<div class="post-metadata">

### Author: ![obloboblo](https://avatars.discourse-cdn.com/v4/letter/o/f05b48/32.png) [@obloboblo](https://discuss.elastic.co/u/obloboblo)
#### Post date: [November 16, 2020, 11:45am UTC](https://discuss.elastic.co/t/no-cached-mapping-for-this-field/255514/1 "2020-11-16T11:45:28Z")

</div>

hello  
I've seen that a warning from the topic subject makes some troubles also for other users on this forum, but I believe this one is new here.  
this warning shows for a field with epoch timestamp value. after some time I finally did ingest (via syslog) it with a set indexing template (otherwise it would be interpreted as a number).  
while looking at the event in Kibana the field is "Unkonwn field" and the value (shows as a number) has this "no cached ...".  
`GET my_index/_mapping/field/timestamp_event`

```
 {
      "my_index" : {
        "mappings" : {
          "timestamp_event" : {
            "full_name" : "timestamp_event",
            "mapping" : {
              "timestamp_event" : {
                "type" : "date",
                "format" : "epoch_second"

```

I would like to see it as a human readable date not a strange number, but can't make it even though countless refreshing, index deletes, ingests and Kibana restarts.  
Any idea what I did wrong? Seems I can't find it myself 😕

regards!

---

<div class="post-metadata">

### Author: ![obloboblo](https://avatars.discourse-cdn.com/v4/letter/o/f05b48/32.png) [@obloboblo](https://discuss.elastic.co/u/obloboblo)
#### Post date: [November 17, 2020, 12:15pm UTC](https://discuss.elastic.co/t/no-cached-mapping-for-this-field/255514/2 "2020-11-17T12:15:19Z")

</div>

heh, ok. i don't know what has happened. just checked this afternoon.  
machine restart (it's a single virtual machine with the elastic + kibina on it) helped. but this not sth that I would like to see on production environment or a diagnosing method. date is correct and no warning info in Kibana.  
any ideas? both Kibana and Elastic logs are clear. also API output doesn't shown any signs of concern.

regards

---

<div class="post-metadata">

### Author: ![warkolm](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/warkolm/32/39224_2.png) [@warkolm](https://discuss.elastic.co/u/warkolm)
#### Post date: [November 17, 2020, 11:03pm UTC](https://discuss.elastic.co/t/no-cached-mapping-for-this-field/255514/3 "2020-11-17T23:03:26Z")

</div>

Did you try to refresh the mapping of the index pattern?

---

<div class="post-metadata">

### Author: ![obloboblo](https://avatars.discourse-cdn.com/v4/letter/o/f05b48/32.png) [@obloboblo](https://discuss.elastic.co/u/obloboblo)
#### Post date: [November 18, 2020, 7:36am UTC](https://discuss.elastic.co/t/no-cached-mapping-for-this-field/255514/4 "2020-11-18T07:36:58Z")

</div>

yes, that was the first thing I did. actually, few times. event tried to get rid of the index and populate it from the very beginning.

---

<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 16, 2020, 7:37am UTC](https://discuss.elastic.co/t/no-cached-mapping-for-this-field/255514/5 "2020-12-16T07:37:02Z")

</div>

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