# \_ingest.timestamp Invalid Format for Date field
**URL:** https://discuss.elastic.co/t/-ingest-timestamp-invalid-format-for-date-field/92718
**Category:** Elasticsearch
**Created:** [July 11, 2017, 9:43pm UTC](https://discuss.elastic.co/t/-ingest-timestamp-invalid-format-for-date-field/92718 "2017-07-11T21:43:05Z")
**Posts on this page:** 3
**Page:** 1
### Author:  [@mstruve](https://discuss.elastic.co/u/mstruve)
#### Post date: [July 11, 2017, 9:43pm UTC](https://discuss.elastic.co/t/-ingest-timestamp-invalid-format-for-date-field/92718/1 "2017-07-11T21:43:05Z")
I was reading the [docs](https://www.elastic.co/guide/en/elasticsearch/reference/master/accessing-data-in-pipelines.html#accessing-ingest-metadata) about how to use the timestamp from the ingest node to set a field on the document. However, when I try to set a date field(last\_indexed\_at) to the ingest.timestamp I get an Invalid format error which seems weird since I would assume the timestamp would be in a date format recognizable by elasticsearch.
The field I am trying to set to the ingest node timestamp is a date field, format dateOptionalTime.
Anyone know if there is a proper way to do this? Do I need to setup a second date processor to process the timestamp or do I need to change the mapping for the last\_indexed\_at field.
Thanks!
---
### Author:  [@rjernst](https://discuss.elastic.co/u/rjernst)
#### Post date: [July 12, 2017, 10:24pm UTC](https://discuss.elastic.co/t/-ingest-timestamp-invalid-format-for-date-field/92718/2 "2017-07-12T22:24:45Z")
This is fixed for 6.0.
>
In 5.5.0, you can use the new behavior by setting `ingest.new_date_format` to `true`.
---
### Author:  [@system](https://discuss.elastic.co/u/system)
#### Post date: [August 9, 2017, 10:24pm UTC](https://discuss.elastic.co/t/-ingest-timestamp-invalid-format-for-date-field/92718/3 "2017-08-09T22:24:48Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.