# \_timestamp path in ES 2.2

**URL:** <https://discuss.elastic.co/t/-timestamp-path-in-es-2-2/44736>\
**Category:** Elasticsearch\
**Created:** [March 17, 2016, 4:37pm UTC](https://discuss.elastic.co/t/-timestamp-path-in-es-2-2/44736 "2016-03-17T16:37:36Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![brianDFIR](https://avatars.discourse-cdn.com/v4/letter/b/c68b51/32.png) [@brianDFIR](https://discuss.elastic.co/u/brianDFIR)\
**Post date:** [March 17, 2016, 4:37pm UTC](https://discuss.elastic.co/t/-timestamp-path-in-es-2-2/44736/1 "2016-03-17T16:37:36Z")

</div>

I am upgrading from ES 1.7 to ES 2.2 and the \_timestamp deprecation broke what I was using it for.

My 1.7 mapping looks like:

> {  
> "doctype": {  
> "\_timestamp": {  
> "enabled": "true",  
> "format": "MM/dd/yyyy HH:mm:ss",  
> "path": "access\_time"  
> },  
> "properties": {  
> "access\_time": {  
> "format": "MM/dd/yyyy HH:mm:ss",  
> "type": "date"  
> },  
> }  
> }

I did this because I am using bulk\_inserts and need a timestamp to pick in Kibana that is universally in all doc\_types to see all the data in my index patter, but the timestamps are different for each doc\_type.

Due to the 2.2 deprecation of \_timestamp being limited to enabling the field, setting format and default value, this breaks my mapping. I could enable the \_timestamp field and just have it be the index time; that would work, but wouldn't be ideal. The deprecation notes say to use "date", but it doesn't look like I can use "path" with "date".

Any ideas?

Thanks

Brian

---

<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:** [July 5, 2017, 11:07pm UTC](https://discuss.elastic.co/t/-timestamp-path-in-es-2-2/44736/2 "2017-07-05T23:07:32Z")

</div>