# Revision history [back]

Elasticsearch can consume just about every kind of standard date, or datetime strings.

datetime examples: yyyy-MM-dd HH:mm:ss (2019-08-08 17:55:26) yyyy-MM-dd HH:mm:ss.SSS (2019-08-08 17:55:26.472) yyyy-MM-ddTHH:mm:ss.SSS (2019-08-08T17:55:26.472-07:00)

It uses Java JodaTime implementation under the hood too.

But right at this moment I'm struggling with the same problem.

No matter how I transform the field that I want to use for the 'Time Basis', the Elasticsearch designation stage will only deliver a unix epoch to elasticsearch.

I think something is messed up, or the documentation is missing a minor detail. (Currently trying to get the entire stack to build in Eclipse so I can debug)

Elasticsearch can consume just about every kind of standard date, or datetime strings.

datetime examples: examples:

yyyy-MM-dd HH:mm:ss (2019-08-08 17:55:26)
yyyy-MM-dd HH:mm:ss.SSS (2019-08-08 17:55:26.472)
yyyy-MM-ddTHH:mm:ss.SSS (2019-08-08T17:55:26.472-07:00)(2019-08-08T17:55:26.472-07:00)


It uses Java JodaTime implementation under the hood too.

But right at this moment I'm struggling with the same problem.

No matter how I transform the field that I want to use for the 'Time Basis', the Elasticsearch designation stage will only deliver a unix epoch to elasticsearch.

I think something is messed up, or the documentation is missing a minor detail. (Currently trying to get the entire stack to build in Eclipse so I can debug)

Elasticsearch can consume just about every kind of standard date, or datetime strings.

datetime examples:

yyyy-MM-dd HH:mm:ss (2019-08-08 17:55:26)
yyyy-MM-dd HH:mm:ss.SSS (2019-08-08 17:55:26.472)
yyyy-MM-ddTHH:mm:ss.SSS (2019-08-08T17:55:26.472-07:00)


It uses Java JodaTime implementation under the hood too.

But right at this moment I'm struggling with the same problem.

No matter how I transform the field that I want to use for the 'Time Basis', the Elasticsearch designation stage will only deliver a unix epoch to elasticsearch.

I think something is messed up, or the documentation is missing a minor detail. (Currently trying to get the entire stack to build in Eclipse so I can debug)