epoch time was something originally on the plate for 2.0 - last i was aware it was still going to make it, but I will double check with team.
Based on what team has told me this was deferred from 2.0. We will take this as a candidate for the next release.
There are a few different scenarios here we need to assess and prioritize for 2.1 :
1) simply provide a conversion function of any field from integer (epoch format) to readable date-time string so they can be understood. High priority
2) provide some kind of operations on Datetime data types ( like take delta between 2 datetimes or ??? more brainstorming required). Med-Low priority - there probably are some interesting use cases that may dictate this.
3) support epoch as the primary datetime stamp for entire message ( not a 1-off field) . High priority