Hi Adam,
I was just about to write sharing what I know. I tried to replicate
your issue, and I made it a little further than what you reported.
Thanks for sharing what you learned about Joda DateTime versions
being slightly out of sync.
My efforts focused on using the Spark-shell, and I ran into some
other serialization issues. I've worked with Andrew Hulbert a few
minutes this evening to try and address things. We'll be looking
into things some more. He said he'd have a little more time to look
into things tomorrow.
Out of curiosity, did you managed to your Spark job to run
successfully? If so, how have you been submitting your jobs?
Thanks for asking a great question,
Jim
On 11/24/2014 04:58 PM, Adam F wrote:
I've been working the error and discovered it was due to
conflicting versions of DateTime. My spark job was
requiring 2.4 and Geomesa requires 2.3. When I packaged my
job into an uber jar, it was only packaging 2.4. This is an
issues because apparently 2.4 of DateTime has issues with
using Long.MinValue and Long.MaxValue (reference https://github.com/JodaOrg/joda-time/issues/190)
when initializing a DateTime object. This same approach is
used to initialize a few DateTime objects in
org.locationtech.geomesa.core.index.scala (line 36/37).
Thanks
-- Adam
_______________________________________________
geomesa-users mailing list
geomesa-users@xxxxxxxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
http://www.locationtech.org/mailman/listinfo/geomesa-users
|