# Mapping timestamp in epoch\_second format

**URL:** <https://discuss.elastic.co/t/mapping-timestamp-in-epoch-second-format/235380>\
**Category:** Elasticsearch\
**Created:** [June 2, 2020, 5:05pm UTC](https://discuss.elastic.co/t/mapping-timestamp-in-epoch-second-format/235380 "2020-06-02T17:05:48Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![YvorL](https://avatars.discourse-cdn.com/v4/letter/y/9fc348/32.png) [@YvorL](https://discuss.elastic.co/u/YvorL)\
**Post date:** [June 2, 2020, 5:05pm UTC](https://discuss.elastic.co/t/mapping-timestamp-in-epoch-second-format/235380/1 "2020-06-02T17:05:48Z")

</div>

Hi,

I run into [this blog post](https://engineering.mixmax.com/blog/30x-faster-elasticsearch-queries) regarding storing timestamps.  
If I let Elasticsearch map the @timestamp field (as date) and there aren't milliseconds (always 000) in the logs, I'd assume that explicitly mapping that date as `epoch_second` won't change much. Am I right?

Thanks!

---

<div class="post-metadata">

**Author:** ![YvorL](https://avatars.discourse-cdn.com/v4/letter/y/9fc348/32.png) [@YvorL](https://discuss.elastic.co/u/YvorL)\
**Post date:** [June 8, 2020, 7:50am UTC](https://discuss.elastic.co/t/mapping-timestamp-in-epoch-second-format/235380/2 "2020-06-08T07:50:38Z")

</div>

No takers? ☹

---

<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 6, 2020, 7:50am UTC](https://discuss.elastic.co/t/mapping-timestamp-in-epoch-second-format/235380/3 "2020-07-06T07:50:43Z")

</div>

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