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

[David Boyd <dboyd@xxxxxxxxxxxxxxxxx>]

Emilio:

   Thanks.  I puzzled it out in the end.

How would one date index historical data?  The data I have has numerous 
dates before the Epoch.   The exception I am
getting below.  Does this mean my feature did not get stored, or just 
the date was not indexed?    If the latter,  how would
this data behave on a query including the date?


> 2017-04-20 17:11:12,306 |  WARN | [Thread-7] | 
> (ICEWS_EntityExtractor.java:240) - StartDateString: 1968-01-01 
> StartDate: 1968-01-01T00:00:00.000-05:00 EndDateString: 1996-08-31 
> EndDate: 1996-08-31T00:00:00.000-04:00
> 2017-04-20 17:11:12,306 |  INFO | [Thread-7] | 
> (ICEWS_EntityExtractor.java:300) - Persisting 2 ICEWS records.
> 2017-04-20 17:11:12,556 | ERROR | [Thread-7] | 
> (AccumuloPersistor.java:1073) - requirement failed: Value out of 
> bounds ([0.0 604800.0]): -241200.0
> java.lang.IllegalArgumentException: requirement failed: Value out of 
> bounds ([0.0 604800.0]): -241200.0
>     at scala.Predef$.require(Predef.scala:224)
>     at 
> org.locationtech.geomesa.curve.NormalizedDimension$class.normalize(NormalizedDimension.scala:17)


On 4/20/17 6:07 PM, Emilio Lahr-Vivaz wrote:
> 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?
>
> _______________________________________________
> geomesa-users mailing list
> geomesa-users@xxxxxxxxxxxxxxxx
> To change your delivery options, retrieve your password, or 
> unsubscribe from this list, visit
> https://dev.locationtech.org/mailman/listinfo/geomesa-users

--
========= mailto:dboyd@xxxxxxxxxxxxxxxxx ============
David W. Boyd
VP,  Data Solutions
10432 Balls Ford, Suite 240
Manassas, VA 20109
office:   +1-703-552-2862
cell:     +1-703-402-7908
============== http://www.incadencecorp.com/ ============
ISO/IEC JTC1 WG9, editor ISO/IEC 20547 Big Data Reference Architecture
Chair ANSI/INCITS TC Big Data
Co-chair NIST Big Data Public Working Group Reference Architecture
First Robotic Mentor - FRC, FTC - www.iliterobotics.org
Board Member- USSTEM Foundation - www.usstem.org

The information contained in this message may be privileged
and/or confidential and protected from disclosure.
If the reader of this message is not the intended recipient
or an employee or agent responsible for delivering this message
to the intended recipient, you are hereby notified that any
dissemination, distribution or copying of this communication
is strictly prohibited.  If you have received this communication
in error, please notify the sender immediately by replying to
this message and deleting the material from any computer.