Re: [geomesa-users] Question about min and max times in indexing

[Emilio Lahr-Vivaz <elahrvivaz@xxxxxxxx>]

Hi David,

I don't believe that this is in our documentation, but it's commented in 
our source code. The min date will always be the unix epoch, and the max 
date depends on the indexing interval of your z-curve (the default 
interval is week):

https://github.com/locationtech/geomesa/blob/master/geomesa-z3/src/main/scala/org/locationtech/geomesa/curve/BinnedTime.scala#L15-L39

Thanks,

Emilio

On 04/20/2017 04:45 PM, David Boyd wrote:
> All:
>
>    Haven't found this in the documents yet so I thought I would ask.
>
> I have a two fields in my data representing a startTime and an endTime.
> Values for those string fields are normally dates but can also be 
> "beginning of time" and
> "end of time" respectively.
>
> I originally I tried setting beginning of time to be 01/01/1111 but I 
> would get an
> index out of range error (I assume it is because this was before the 
> standard Unix epoc).
>
> That error was down in the XZ3 index creation.
>
>
> I then tried using new DateTime(Long.MIN) and new DateTime(Long.MAX) 
> but the max
> now throws errors in Joda.Time.
>
> So what are the min and max Times supported by Geomesa in the indexes?