# Epoch time in milliseconds with decimal

**URL:** https://discuss.elastic.co/t/epoch-time-in-milliseconds-with-decimal/52117
**Category:** Elasticsearch
**Created:** [June 7, 2016, 7:26pm UTC](https://discuss.elastic.co/t/epoch-time-in-milliseconds-with-decimal/52117 "2016-06-07T19:26:47Z")
**Posts on this page:** 5
**Page:** 1

<div class="post-metadata">

### Author: ![joeyd](https://avatars.discourse-cdn.com/v4/letter/j/13edae/32.png) [@joeyd](https://discuss.elastic.co/u/joeyd)
#### Post date: [June 7, 2016, 7:26pm UTC](https://discuss.elastic.co/t/epoch-time-in-milliseconds-with-decimal/52117/1 "2016-06-07T19:26:47Z")

</div>

Elasticsearch doesn't seem to recognize epoch time in milliseconds with a decimal (ex 1413680667.549). When importing the json logs with Logstash, the dynamic field created is "double". I've setup an index template forcing this field to "date" but get invalid format warnings.

:response=\>{"create"=\>{"\_index"=\>"aaa", "\_type"=\>"json", "\_id"=\>"AVUsTuWp2AOatQ9Jkzgr", "status"=\>400, "error"=\>{"type"=\>"mapper\_parsing\_exception", "reason"=\>"failed to parse [meta.timestamp]", "caused\_by"=\>{"type"=\>"illegal\_argument\_exception", "reason"=\>"Invalid format: "1413680667.549" is malformed at "680667.549""}}}}, :level=\>:warn}

Has anyone run into this before?

---

<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: [June 7, 2016, 11:23pm UTC](https://discuss.elastic.co/t/epoch-time-in-milliseconds-with-decimal/52117/2 "2016-06-07T23:23:56Z")

</div>

Epoch is in milliseconds AFAIK? Oh, no it is seconds, sorry!

---

<div class="post-metadata">

### Author: ![colings86](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/colings86/32/44960_2.png) [@colings86](https://discuss.elastic.co/u/colings86)
#### Post date: [June 8, 2016, 8:08am UTC](https://discuss.elastic.co/t/epoch-time-in-milliseconds-with-decimal/52117/3 "2016-06-08T08:08:30Z")

</div>

date fields are internally represented as long values. Currently Elasticsearch does not support decimal values of millisecond dates.

---

<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: [June 8, 2016, 8:16am UTC](https://discuss.elastic.co/t/epoch-time-in-milliseconds-with-decimal/52117/4 "2016-06-08T08:16:58Z")

</div>

It's coming in v5 though, thanks to bigint.

---

<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, 10:45pm UTC](https://discuss.elastic.co/t/epoch-time-in-milliseconds-with-decimal/52117/5 "2017-07-05T22:45:24Z")

</div>


