# Unix timestamp (epoch) in date type **URL:** \ **Category:** Elasticsearch\ **Created:** [October 6, 2013, 6:01pm UTC](https://discuss.elastic.co/t/unix-timestamp-epoch-in-date-type/13860 "2013-10-06T18:01:18Z")\ **Posts on this page:** 9\ **Page:** 1
**Author:** ![Edward\_Fjellskal](https://avatars.discourse-cdn.com/v4/letter/e/3ab097/32.png) [@Edward\_Fjellskal](https://discuss.elastic.co/u/Edward_Fjellskal)\ **Post date:** [October 6, 2013, 6:01pm UTC](https://discuss.elastic.co/t/unix-timestamp-epoch-in-date-type/13860/1 "2013-10-06T18:01:18Z")
From: [http://www.elasticsearch.org/guide/en/elasticsearch/reference/current/mapping-core-types.html#date](http://www.elasticsearch.org/guide/en/elasticsearch/reference/current/mapping-core-types.html#date) "The date type will also accept a long number representing UTC milliseconds since the epoch, regardless of the format it can handle." Does that mean that I can save the epoch time + "000" and that will be a valid date field? Example: Epoch: 1381041397 ES-Epoch: 1381041397000 Will that work also for the Kibana @timestamp field out of the box etc? Regards, Edward -- You received this message because you are subscribed to the Google Groups "elasticsearch" group. To unsubscribe from this group and stop receiving emails from it, send an email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com). For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out). ---
**Author:** ![Boaz\_Leskes](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/boaz_leskes/32/723_2.png) [@Boaz\_Leskes](https://discuss.elastic.co/u/Boaz_Leskes)\ **Post date:** [October 9, 2013, 10:30am UTC](https://discuss.elastic.co/t/unix-timestamp-epoch-in-date-type/13860/2 "2013-10-09T10:30:55Z")
Hi Edward, Assuming your epoch time is in second, then yes, you need to multiply by 1000. About kibana - if it is mapped as a date field it will work - regardless of the input form - be it milliseconds epochs or an ISO formatted string. Cheers, Boaz On Sunday, October 6, 2013 8:01:18 PM UTC+2, Edward Fjellskål wrote: > From: > > [Elasticsearch Platform — Find real-time answers at scale | Elastic](http://www.elasticsearch.org/guide/en/elasticsearch/reference/current/mapping-core-types.html#date) > > "The date type will also accept a long number representing UTC > milliseconds since the epoch, regardless of the format it can handle." > > Does that mean that I can save the epoch time + "000" and that > will be a valid date field? > > Example: > Epoch: 1381041397 > ES-Epoch: 1381041397000 > > Will that work also for the Kibana @timestamp field out of the box etc? > > Regards, > Edward -- You received this message because you are subscribed to the Google Groups "elasticsearch" group. To unsubscribe from this group and stop receiving emails from it, send an email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com). For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out). ---
**Author:** ![Edward\_Fjellskal](https://avatars.discourse-cdn.com/v4/letter/e/3ab097/32.png) [@Edward\_Fjellskal](https://discuss.elastic.co/u/Edward_Fjellskal)\ **Post date:** [October 10, 2013, 3:50pm UTC](https://discuss.elastic.co/t/unix-timestamp-epoch-in-date-type/13860/3 "2013-10-10T15:50:09Z")
Hi Boaz, So my epoch is not a date field: "epoch" : { "type" : "long" }, I can probably test this fairly easy, but would that above work for kibana if I store epoch as "epoch X 1000" ? or would I need change the mapping to: "epoch" : { "type" : "date" }, and insert "epoch x 1000" ? Thanks for your resonse 🙂 Edward On 10/09/2013 12:30 PM, Boaz Leskes wrote: > Hi Edward, > > Assuming your epoch time is in second, then yes, you need to multiply by > 1000. > > About kibana - if it is mapped as a date field it will work - regardless > of the input form - be it milliseconds epochs or an ISO formatted string. > > Cheers, > Boaz > > On Sunday, October 6, 2013 8:01:18 PM UTC+2, Edward Fjellskål wrote: > > ``` > From: > http://www.elasticsearch.org/guide/en/elasticsearch/reference/current/mapping-core-types.html#date > > > "The date type will also accept a long number representing UTC > milliseconds since the epoch, regardless of the format it can handle." > > Does that mean that I can save the epoch time + "000" and that > will be a valid date field? > > Example: > Epoch: 1381041397 > ES-Epoch: 1381041397000 > > Will that work also for the Kibana @timestamp field out of the box etc? > > Regards, > Edward > > ``` > > -- > You received this message because you are subscribed to the Google > Groups "elasticsearch" group. > To unsubscribe from this group and stop receiving emails from it, send > an email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com). > For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out). -- You received this message because you are subscribed to the Google Groups "elasticsearch" group. To unsubscribe from this group and stop receiving emails from it, send an email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com). For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out). ---
**Author:** ![shadyabhi](https://avatars.discourse-cdn.com/v4/letter/s/edb3f5/32.png) [@shadyabhi](https://discuss.elastic.co/u/shadyabhi)\ **Post date:** [October 11, 2013, 4:30am UTC](https://discuss.elastic.co/t/unix-timestamp-epoch-in-date-type/13860/4 "2013-10-11T04:30:44Z")
Hi Edward, "type" should be "date" for Kibana to work. On Thu, Oct 10, 2013 at 9:20 PM, Edward Fjellskål [edwardfjellskaal@gmail.com](mailto:edwardfjellskaal@gmail.com) wrote: > Hi Boaz, > > So my epoch is not a date field: > > "epoch" : { > "type" : "long" > }, > > I can probably test this fairly easy, but would that above work for > kibana if I store epoch as "epoch X 1000" ? > > or would I need change the mapping to: > > "epoch" : { > "type" : "date" > }, > > and insert "epoch x 1000" ? > > Thanks for your resonse 🙂 > > Edward > > On 10/09/2013 12:30 PM, Boaz Leskes wrote: > > > Hi Edward, > > > > Assuming your epoch time is in second, then yes, you need to multiply by > > 1000. > > > > About kibana - if it is mapped as a date field it will work - regardless > > of the input form - be it milliseconds epochs or an ISO formatted string. > > > > Cheers, > > Boaz > > > > On Sunday, October 6, 2013 8:01:18 PM UTC+2, Edward Fjellskål wrote: > > > > ``` > > From: > > http://www.elasticsearch.org/guide/en/elasticsearch/reference/current/mapping-core-types.html#date > > > > > > "The date type will also accept a long number representing UTC > > milliseconds since the epoch, regardless of the format it can handle." > > > > Does that mean that I can save the epoch time + "000" and that > > will be a valid date field? > > > > Example: > > Epoch: 1381041397 > > ES-Epoch: 1381041397000 > > > > Will that work also for the Kibana @timestamp field out of the box etc? > > > > Regards, > > Edward > > > > ``` > > > > -- > > You received this message because you are subscribed to the Google > > Groups "elasticsearch" group. > > To unsubscribe from this group and stop receiving emails from it, send > > an email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com). > > For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out). > > -- > You received this message because you are subscribed to the Google Groups "elasticsearch" group. > To unsubscribe from this group and stop receiving emails from it, send an email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com). > For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out). -- Regards, Abhijeet Rastogi (shadyabhi) -- You received this message because you are subscribed to the Google Groups "elasticsearch" group. To unsubscribe from this group and stop receiving emails from it, send an email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com). For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out). ---
**Author:** ![Boaz\_Leskes](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/boaz_leskes/32/723_2.png) [@Boaz\_Leskes](https://discuss.elastic.co/u/Boaz_Leskes)\ **Post date:** [October 11, 2013, 6:56am UTC](https://discuss.elastic.co/t/unix-timestamp-epoch-in-date-type/13860/5 "2013-10-11T06:56:09Z")
HI Edward, As Abhijeet has already said - for kibana to work you must have your epoch field must be of the type date and if you send longs, it must be in milliseconds since the epoch. Cheers, Boaz On Fri, Oct 11, 2013 at 6:30 AM, Abhijeet Rastogi [abhijeet.1989@gmail.com](mailto:abhijeet.1989@gmail.com)wrote: > Hi Edward, > > "type" should be "date" for Kibana to work. > > On Thu, Oct 10, 2013 at 9:20 PM, Edward Fjellskål > [edwardfjellskaal@gmail.com](mailto:edwardfjellskaal@gmail.com) wrote: > > > Hi Boaz, > > > > So my epoch is not a date field: > > > > "epoch" : { > > "type" : "long" > > }, > > > > I can probably test this fairly easy, but would that above work for > > kibana if I store epoch as "epoch X 1000" ? > > > > or would I need change the mapping to: > > > > "epoch" : { > > "type" : "date" > > }, > > > > and insert "epoch x 1000" ? > > > > Thanks for your resonse 🙂 > > > > Edward > > > > On 10/09/2013 12:30 PM, Boaz Leskes wrote: > > > > > Hi Edward, > > > > > > Assuming your epoch time is in second, then yes, you need to multiply by > > > 1000. > > > > > > About kibana - if it is mapped as a date field it will work - regardless > > > of the input form - be it milliseconds epochs or an ISO formatted > > > string. > > > > > > Cheers, > > > Boaz > > > > > > On Sunday, October 6, 2013 8:01:18 PM UTC+2, Edward Fjellskål wrote: > > > > > > ``` > > > From: > > > > > > ``` > > [Elasticsearch Platform — Find real-time answers at scale | Elastic](http://www.elasticsearch.org/guide/en/elasticsearch/reference/current/mapping-core-types.html#date) > > > > ``` > > > < > > > > > > ``` > > [Elasticsearch Platform — Find real-time answers at scale | Elastic](http://www.elasticsearch.org/guide/en/elasticsearch/reference/current/mapping-core-types.html#date) > > > > ``` > > > "The date type will also accept a long number representing UTC > > > milliseconds since the epoch, regardless of the format it can > > > > > > ``` > > handle." > > > > ``` > > > Does that mean that I can save the epoch time + "000" and that > > > will be a valid date field? > > > > > > Example: > > > Epoch: 1381041397 > > > ES-Epoch: 1381041397000 > > > > > > Will that work also for the Kibana @timestamp field out of the box > > > > > > ``` > > etc? > > > > ``` > > > Regards, > > > Edward > > > > > > ``` > > > > > > -- > > > You received this message because you are subscribed to the Google > > > Groups "elasticsearch" group. > > > To unsubscribe from this group and stop receiving emails from it, send > > > an email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com). > > > For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out). > > > > -- > > You received this message because you are subscribed to the Google > > Groups "elasticsearch" group. > > To unsubscribe from this group and stop receiving emails from it, send > > an email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com). > > For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out). > > -- > Regards, > Abhijeet Rastogi (shadyabhi) -- You received this message because you are subscribed to the Google Groups "elasticsearch" group. To unsubscribe from this group and stop receiving emails from it, send an email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com). For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out). ---
**Author:** ![Edward\_Fjellskal](https://avatars.discourse-cdn.com/v4/letter/e/3ab097/32.png) [@Edward\_Fjellskal](https://discuss.elastic.co/u/Edward_Fjellskal)\ **Post date:** [October 11, 2013, 7:40pm UTC](https://discuss.elastic.co/t/unix-timestamp-epoch-in-date-type/13860/6 "2013-10-11T19:40:39Z")
Thanks for the input... Im coding up something now 🙂 Regards, Edward On 10/11/13, Boaz Leskes [b.leskes@gmail.com](mailto:b.leskes@gmail.com) wrote: > HI Edward, > > As Abhijeet has already said - for kibana to work you must have your epoch > field must be of the type date and if you send longs, it must be in > milliseconds since the epoch. > > Cheers, > Boaz > > On Fri, Oct 11, 2013 at 6:30 AM, Abhijeet Rastogi > [abhijeet.1989@gmail.com](mailto:abhijeet.1989@gmail.com)wrote: > > > Hi Edward, > > > > "type" should be "date" for Kibana to work. > > > > On Thu, Oct 10, 2013 at 9:20 PM, Edward Fjellskål > > [edwardfjellskaal@gmail.com](mailto:edwardfjellskaal@gmail.com) wrote: > > > > > Hi Boaz, > > > > > > So my epoch is not a date field: > > > > > > "epoch" : { > > > "type" : "long" > > > }, > > > > > > I can probably test this fairly easy, but would that above work for > > > kibana if I store epoch as "epoch X 1000" ? > > > > > > or would I need change the mapping to: > > > > > > "epoch" : { > > > "type" : "date" > > > }, > > > > > > and insert "epoch x 1000" ? > > > > > > Thanks for your resonse 🙂 > > > > > > Edward > > > > > > On 10/09/2013 12:30 PM, Boaz Leskes wrote: > > > > > > > Hi Edward, > > > > > > > > Assuming your epoch time is in second, then yes, you need to multiply > > > > by > > > > 1000. > > > > > > > > About kibana - if it is mapped as a date field it will work - > > > > regardless > > > > of the input form - be it milliseconds epochs or an ISO formatted > > > > string. > > > > > > > > Cheers, > > > > Boaz > > > > > > > > On Sunday, October 6, 2013 8:01:18 PM UTC+2, Edward Fjellskål wrote: > > > > > > > > ``` > > > > From: > > > > > > > > ``` > > > > [Elasticsearch Platform — Find real-time answers at scale | Elastic](http://www.elasticsearch.org/guide/en/elasticsearch/reference/current/mapping-core-types.html#date) > > > > > > ``` > > > > < > > > > > > > > ``` > > > > [Elasticsearch Platform — Find real-time answers at scale | Elastic](http://www.elasticsearch.org/guide/en/elasticsearch/reference/current/mapping-core-types.html#date) > > > > > > ``` > > > > "The date type will also accept a long number representing UTC > > > > milliseconds since the epoch, regardless of the format it can > > > > > > > > ``` > > > > handle." > > > > > > ``` > > > > Does that mean that I can save the epoch time + "000" and that > > > > will be a valid date field? > > > > > > > > Example: > > > > Epoch: 1381041397 > > > > ES-Epoch: 1381041397000 > > > > > > > > Will that work also for the Kibana @timestamp field out of the box > > > > > > > > ``` > > > > etc? > > > > > > ``` > > > > Regards, > > > > Edward > > > > > > > > ``` > > > > > > > > -- > > > > You received this message because you are subscribed to the Google > > > > Groups "elasticsearch" group. > > > > To unsubscribe from this group and stop receiving emails from it, send > > > > an email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com). > > > > For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out). > > > > > > -- > > > You received this message because you are subscribed to the Google > > > Groups "elasticsearch" group. > > > To unsubscribe from this group and stop receiving emails from it, send > > > an email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com). > > > For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out). > > > > -- > > Regards, > > Abhijeet Rastogi (shadyabhi) > > -- > You received this message because you are subscribed to the Google Groups > "elasticsearch" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com). > For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out). -- Edward Bjarte Fjellskål Senior Security Analyst [http://www.gamelinux.org/](http://www.gamelinux.org/) -- You received this message because you are subscribed to the Google Groups "elasticsearch" group. To unsubscribe from this group and stop receiving emails from it, send an email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com). For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out). ---
**Author:** ![karnamonkster](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/karnamonkster/32/67266_2.png) [@karnamonkster](https://discuss.elastic.co/u/karnamonkster)\ **Post date:** [April 17, 2014, 11:55am UTC](https://discuss.elastic.co/t/unix-timestamp-epoch-in-date-type/13860/7 "2014-04-17T11:55:02Z")
Does it work? after changing the {"type" : "date"} And setting a date format - { "messages" : { "\_timestamp" : { "enabled" : true }, "properties" : { "app\_event\_time" : { "type" : "date", "format" : "yyyy/MM/dd HH:mm:ss" }, "event\_time" : { "type" : "date", "format" : "yyyy/MM/dd HH:mm:ss" }, What could be the problem? On Saturday, October 12, 2013 1:10:39 AM UTC+5:30, Edward Fjellskål wrote: > Thanks for the input... > Im coding up something now 🙂 > > Regards, > Edward > > On 10/11/13, Boaz Leskes \<[b.le...@gmail.com](mailto:b.le...@gmail.com) \\> wrote: > > > HI Edward, > > > > As Abhijeet has already said - for kibana to work you must have your > > epoch > > field must be of the type date and if you send longs, it must be in > > milliseconds since the epoch. > > > > Cheers, > > Boaz > > > > On Fri, Oct 11, 2013 at 6:30 AM, Abhijeet Rastogi > > \<[abhije...@gmail.com](mailto:abhije...@gmail.com) \\>wrote: > > > > > Hi Edward, > > > > > > "type" should be "date" for Kibana to work. > > > > > > On Thu, Oct 10, 2013 at 9:20 PM, Edward Fjellskål > > > \<[edwardfj...@gmail.com](mailto:edwardfj...@gmail.com) \\> wrote: > > > > > > > Hi Boaz, > > > > > > > > So my epoch is not a date field: > > > > > > > > "epoch" : { > > > > "type" : "long" > > > > }, > > > > > > > > I can probably test this fairly easy, but would that above work for > > > > kibana if I store epoch as "epoch X 1000" ? > > > > > > > > or would I need change the mapping to: > > > > > > > > "epoch" : { > > > > "type" : "date" > > > > }, > > > > > > > > and insert "epoch x 1000" ? > > > > > > > > Thanks for your resonse 🙂 > > > > > > > > Edward > > > > > > > > On 10/09/2013 12:30 PM, Boaz Leskes wrote: > > > > > > > > > Hi Edward, > > > > > > > > > > Assuming your epoch time is in second, then yes, you need to > > > > > multiply > > > > > by > > > > > 1000. > > > > > > > > > > About kibana - if it is mapped as a date field it will work - > > > > > regardless > > > > > of the input form - be it milliseconds epochs or an ISO formatted > > > > > string. > > > > > > > > > > Cheers, > > > > > Boaz > > > > > > > > > > On Sunday, October 6, 2013 8:01:18 PM UTC+2, Edward Fjellskål wrote: > > > > > > > > > > ``` > > > > > From: > > > > > > > > > > ``` > > [Elasticsearch Platform — Find real-time answers at scale | Elastic](http://www.elasticsearch.org/guide/en/elasticsearch/reference/current/mapping-core-types.html#date) > > > > > > ``` > > > > > < > > > > > > > > > > ``` > > [Elasticsearch Platform — Find real-time answers at scale | Elastic](http://www.elasticsearch.org/guide/en/elasticsearch/reference/current/mapping-core-types.html#date) > > > > > > ``` > > > > > "The date type will also accept a long number representing UTC > > > > > milliseconds since the epoch, regardless of the format it can > > > > > > > > > > ``` > > > > > > handle." > > > > > > > > ``` > > > > > Does that mean that I can save the epoch time + "000" and that > > > > > will be a valid date field? > > > > > > > > > > Example: > > > > > Epoch: 1381041397 > > > > > ES-Epoch: 1381041397000 > > > > > > > > > > Will that work also for the Kibana @timestamp field out of the > > > > > > > > > > ``` > > box > > > > etc? > > > > > > > > ``` > > > > > Regards, > > > > > Edward > > > > > > > > > > ``` > > > > > > > > > > -- > > > > > You received this message because you are subscribed to the Google > > > > > Groups "elasticsearch" group. > > > > > To unsubscribe from this group and stop receiving emails from it, > > > > > send > > > > > an email to [elasticsearc...@googlegroups.com](mailto:elasticsearc...@googlegroups.com) \. > > > > > For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out). > > > > > > > > -- > > > > You received this message because you are subscribed to the Google > > > > Groups "elasticsearch" group. > > > > To unsubscribe from this group and stop receiving emails from it, > > > > send > > > > an email to [elasticsearc...@googlegroups.com](mailto:elasticsearc...@googlegroups.com) \. > > > > For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out). > > > > > > -- > > > Regards, > > > Abhijeet Rastogi (shadyabhi) > > > > -- > > You received this message because you are subscribed to the Google > > Groups > > "elasticsearch" group. > > To unsubscribe from this group and stop receiving emails from it, send > > an > > email to [elasticsearc...@googlegroups.com](mailto:elasticsearc...@googlegroups.com) \. > > For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out). > > -- > Edward Bjarte Fjellskål > Senior Security Analyst > [http://www.gamelinux.org/](http://www.gamelinux.org/) -- You received this message because you are subscribed to the Google Groups "elasticsearch" group. To unsubscribe from this group and stop receiving emails from it, send an email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com). To view this discussion on the web visit [https://groups.google.com/d/msgid/elasticsearch/299b6673-b6e2-4662-8e10-b50cb78c9fad%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/299b6673-b6e2-4662-8e10-b50cb78c9fad%40googlegroups.com). For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout). ---
**Author:** ![karnamonkster](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/karnamonkster/32/67266_2.png) [@karnamonkster](https://discuss.elastic.co/u/karnamonkster)\ **Post date:** [April 17, 2014, 11:56am UTC](https://discuss.elastic.co/t/unix-timestamp-epoch-in-date-type/13860/8 "2014-04-17T11:56:29Z")
Does it work? after changing the {"type" : "date"} > And setting a date format - > > { > "messages" : { > "\_timestamp" : { > "enabled" : true > }, > "properties" : { > "app\_event\_time" : { > "type" : "date", > "format" : "yyyy/MM/dd HH:mm:ss" > }, > "event\_time" : { > "type" : "date", > "format" : "yyyy/MM/dd HH:mm:ss" > }, > > What could be the problem? > > Cause mine does not work -- You received this message because you are subscribed to the Google Groups "elasticsearch" group. To unsubscribe from this group and stop receiving emails from it, send an email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com). To view this discussion on the web visit [https://groups.google.com/d/msgid/elasticsearch/0f3bfa6a-c8b1-4e68-8230-1a0eb8f61d33%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/0f3bfa6a-c8b1-4e68-8230-1a0eb8f61d33%40googlegroups.com). For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout). ---
**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, 2017, 1:35am UTC](https://discuss.elastic.co/t/unix-timestamp-epoch-in-date-type/13860/9 "2017-07-06T01:35:17Z")