Skip to main content
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [geomesa-users] Geomesa twitter-collect example question 
Hùng,
I just tried the most recent twitter collect and it worked for me...Do another pull from the repo and rebuild and it should work. Let me know if you need any help getting twitter keys. 

Andrew

On 01/27/2015 07:19 AM, Phan, Ngoc-Hung N. wrote:

Hi all,
I got the below errors when running the 'twitter-collect-accumulo1.5-1.0-SNAPSHOT.jar' with my Twitter's  developer info:

Exception in thread "main" java.lang.NoSuchMethodError: scala.Predef$.intWrapper(I)Lscala/runtime/RichInt;
         at com.twitter.joauth.UrlEncoder$.apply(UrlEncoder.scala:42)
         at com.twitter.joauth.UrlEncoder.apply(UrlEncoder.scala)
         at com.twitter.hbc.core.endpoint.BaseEndpoint.addPostParameter(BaseEndpoint.java:89)
         at com.twitter.hbc.core.endpoint.StatusesFilterEndpoint.locations(StatusesFilterEndpoint.java:51)
         at geomesa.example.twitter.collect.TwitterStreamCollector.collect(TwitterStreamCollector.java:80)
         at geomesa.example.twitter.collect.Runner.main(Runner.java:67)


Please help.  BTW, I just got a latest version from github.
Thanks in advance.

Hùng Phan
Senior Principal Engineer
GENERAL DYNAMICS
Mission Systems, Inc.
(703) 580-8536 (Mobile)
(703) 885-7737 (Office)



-----Original Message-----
From: geomesa-users-bounces@xxxxxxxxxxxxxxxx [mailto:geomesa-users-bounces@xxxxxxxxxxxxxxxx] On Behalf Of Chris Eichelberger
Sent: Monday, January 26, 2015 4:42 PM
To: Geomesa User discussions
Subject: Re: [geomesa-users] Geomesa GDELT example crashes

Manas,

If relocating works as advertised, then it should not only rename the packages as they are included in your output JAR, but it should also rename all of the references to those classes (again, renaming only those references that are included in your output JAR).

Given that, relocating the Joda package in your geomesa-distributed-runtime JAR that's distributed to your tablet servers should prevent the GeoMesa iterators from picking up the wrong version of Joda, because they will automatically be using the version you relocated.

That's the theory, anyway.  If that's not what you're seeing, then perhaps there's another disconnection.

Sincerely,
   -- Chris


On Sun, 2015-01-25 at 20:59 -0500, Manas Kar wrote:

Hi Chris,
  I tried relocating joda-time library with out any positive result. It
might be due to the fact I still don't know how the relocating classes
work.




I mean, even if my joda-time(V2.3) gets reallocated as
org.shaded.joda.time the Accumulo Iterator's won't use that unless I
modify Geomesa code to import org.shaded.joda.time.


I was thinking why not bypass the problem of calling the example via
hadoop jar.
Is there a spark example that pushes text data to Accumulo datastore
using Geomesa(I know there are spark example of ingesting Accumulo
datastore to render density Map)


Thanks again for your help so far.


..Manas



On Fri, Jan 23, 2015 at 11:42 AM, Manas Kar
<manasdebashiskar@xxxxxxxxx> wrote:
         Hi Geomesa experts,
          I have created a Accumulo1.6 + Geomesa(accumulo1.6 branch) on
         CDH5.3.
          The Quickstart program runs fine.
Now I am trying to run 
         the https://github.com/geomesa/geomesa-gdelt.git example which
         fails with the "java.lang.NoSuchMethodError:
         org.joda.time.DateTime.<init>" error.
STACK TRACE 
         ------------------------
Exception in thread "main" java.lang.NoSuchMethodError: 
         org.joda.time.DateTime.<init>(IIIIIILorg/joda/time/DateTimeZone;)V
         at org.locationtech.geomesa.core.index.IndexSchema
         $.<init>(IndexSchema.scala:92)
         at org.locationtech.geomesa.core.index.IndexSchema
         $.<clinit>(IndexSchema.scala)
         at
         org.locationtech.geomesa.core.index.IndexSchemaBuilder.randomNumber(IndexSchema.scala:370)
         at
         org.locationtech.geomesa.core.data.AccumuloDataStore.buildDefaultSpatioTemporalSchema(AccumuloDataStore.scala:100)
         at
         org.locationtech.geomesa.core.data.AccumuloDataStore.computeSpatioTemporalSchema(AccumuloDataStore.scala:370)
         at
         org.locationtech.geomesa.core.data.AccumuloDataStore.createSchema(AccumuloDataStore.scala:389)
         at
         org.locationtech.geomesa.core.data.AccumuloDataStore.createSchema(AccumuloDataStore.scala:484)
         at
         org.locationtech.geomesa.core.data.AccumuloDataStore.createSchema(AccumuloDataStore.scala:70)
         at geomesa.gdelt.GDELTIngest.main(GDELTIngest.java:115)
         at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
         at
         sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
         at
         sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
         at java.lang.reflect.Method.invoke(Method.java:606)
         at org.apache.hadoop.util.RunJar.main(RunJar.java:212)


_______________________________________________
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


_______________________________________________
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
_______________________________________________
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

Back to the top