# Indexmapping @timestamp fails

**URL:** <https://discuss.elastic.co/t/indexmapping-timestamp-fails/159306>\
**Category:** Elasticsearch\
**Created:** [December 4, 2018, 7:41am UTC](https://discuss.elastic.co/t/indexmapping-timestamp-fails/159306 "2018-12-04T07:41:48Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![mortenb123](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/mortenb123/32/37227_2.png) [@mortenb123](https://discuss.elastic.co/u/mortenb123)\
**Post date:** [December 4, 2018, 7:41am UTC](https://discuss.elastic.co/t/indexmapping-timestamp-fails/159306/1 "2018-12-04T07:41:48Z")

</div>

Usually my @timestamp index looks like:  
"@timestamp": {  
"type": "date",  
"format": "yyyy-MM-dd HH:mm:ss.SSS"  
},

But I find indexes where it looks like this:  
"@timestamp": {  
"type": "text",  
"fields": {  
"keyword": {  
"type": "keyword",  
"ignore\_above": 256  
}  
}  
},

Resulting in index pattern conflict. All data is inserted via the \_bulk api

Is this because data is inserted before index has been created or has the first line error?.  
How to prevent this?

Thanks

---

<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:** [January 1, 2019, 7:41am UTC](https://discuss.elastic.co/t/indexmapping-timestamp-fails/159306/2 "2019-01-01T07:41:53Z")

</div>

Closed on January 1, 2019, 7:41am UTC

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