Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [geowave-dev] Ingest example data

try this instead:

<dataStore>
  <name>geowave.50m_admin_0_countries</name>
  <type>GeoWave Datastore - accumulo</type>
  <connectionParameters>
    <entry key="zookeeper">localhost:2181</entry>
    <entry key="Authorization Management Provider">empty</entry>
    <entry key="gwNamespace">geowave.50m_admin_0_countries</entry>
    <entry key="instance">accumulo</entry>
    <entry key="Lock Management">memory</entry>
    <entry key="user">geowave</entry>
    <entry key="password">XXXXXX</entry>
  </connectionParameters>
</dataStore>

updated documentation is on its way (our documentation is in the source and our scripts run during continuous integration autopush it so there will be a delay before it actually hits the site, but expect to see some critical updates within the next couple hours).  Please let us know if you have any other issues as you are our first guinea pig for 0.9.0 (lucky you...sorry).


On Tue, Feb 2, 2016 at 2:09 PM, Jose M <soloninguno@xxxxxxxxxxx> wrote:

Hi Rich, thanks for the fast answer!


Bad luck mine that i start with geowave yesterday hehe. But now is working :)


I had to add some more jars to classpath to run it

-accumulo-trace-1.6.0-cdh5.1.4.jar

-accumulo-fate-1.6.0-cdh5.1.4.jar

-libthrift.jar


Besides, yesterday when building the project I had some issues with some accumulo artifacts. I don't know if it was me but these three were not download from https://repository.cloudera.com/artifactory

-accumulo-core-1.6.0-cdh5.1.4.jar

-accumulo-minicluster-1.6.0-cdh5.1.4.jar

-accumulo-monitor-1.6.0-cdh5.1.4.jar

So i download and install them manually and after that everything compile ok.


One more question, now ingest is ok, but it seems I can't add a new datastore in geoserver. Does anything change in the *-geoserver-single.jar?

As I see the geoserver plugin is installed (at least i see it as an available datastore type), but when creating the datastore the geoserver ajax call return an error 500 without any specific error.

I tried adding the datastore through curl with this xml


<dataStore>
  <name>geowave.50m_admin_0_countries</name>
  <type>GeoWave Datastore</type>
  <connectionParameters>
    <entry key="ZookeeperServers">localhost:2181</entry>
    <entry key="Password">XXXXXX</entry>
    <entry key="Namespace">geowave.50m_admin_0_countries</entry>
    <entry key="UserName">geowave</entry>
    <entry key="Authorization Management Provider">empty</entry>
    <entry key="Lock Management">memory</entry>
    <entry key="InstanceName">accumulo</entry>
  </connectionParameters>
</dataStore>


And that works, but then in the geoserver web it seems the datatype is missing http://oi66.tinypic.com/2mmzcr6.jpg


Thanks for your help!



De: geowave-dev-bounces@xxxxxxxxxxxxxxxx <geowave-dev-bounces@xxxxxxxxxxxxxxxx> en nombre de Rich Fecher <rfecher@xxxxxxxxx>
Enviado: martes, 02 de febrero de 2016 03:05 p.m.
Para: geowave-dev@xxxxxxxxxxxxxxxx
Asunto: Re: [geowave-dev] Ingest example data
 
Hi Jose,
We did roll a 0.9.0 release this weekend, and are working updated documentation and release notes to match it.  I was going to send an email soon to this list with release notes, but overall there are some fairly significant changes.

Regarding your issue, the backend datastore is now completely pluggable with only 'accumulo' and 'memory' being the existing implementations but more are coming soon.  The commandline utility resolves the options to match a datastore implementation and it is actually resolving to the memory datastore in your case because the names of the accumulo options changed in 0.9.0.  It is now "-zookeeper" "-instance" "-user" and "-password" to be a little more distinct instead of "-z" "-i" "-u" and "-p".  Also "-n" changed to "-gwNamespace".  You can explicitly define your datastore that you want to bind to with "-datastore accumulo" to guarantee that for example a typo in the options doesn't give you unexpected results.  Furthermore you can get reasonable help for that specific datastore with "-datastore accumulo --help" if you need to discover what options are available for the datastore.  We will be coming out with a fairly significantly changed commandline tool as we work towards 0.9.1 to make this pluggable datastore concept a bit more intuitive with interacting with the commandline.  In the meantime, we will document these changes.

So, no you didn't make a silly mistake, it was our mistake that you were able to catch us right after these changes were released but before they're well documented.

Let us know if something like this works for you:
java -cp "geowave/deploy/target/geowave-deploy-0.9.1-SNAPSHOT-tools.jar:geowave/extensions/formats/geotools-vector/target/geowave-format-vector-0.9.1-SNAPSHOT.jar" mil.nga.giat.geowave.core.cli.GeoWaveMain -localingest -b ./ingest -gwNamespace geowave.50m_admin_0_countries -f geotools-vector -datastore accumulo -instance accumulo -user geowave -password XXXXXXX -zookeeper localhost:2181

Rich




On Tue, Feb 2, 2016 at 12:35 PM, Jose M <soloninguno@xxxxxxxxxxx> wrote:

Hi,


I'm testing geowave/accumulo, using cloudera 5.5 with accumulo 1.6, and last geowave from github. I already build the project and configure accumulo to start using it and i think i configure it ok (copying jar, the classpath configuration, geoserver, config, etc).


Now I'm trying to run the example from here https://ngageoint.github.io/geowave/documentation.html#ingest-example to ingest some data, but it seems not to be working, although i'm not getting any real exception.


This is how I'm calling the geowave utility


java -cp "geowave/deploy/target/geowave-deploy-0.9.1-SNAPSHOT-tools.jar:geowave/extensions/formats/geotools-vector/target/geowave-format-vector-0.9.1-SNAPSHOT.jar" mil.nga.giat.geowave.core.cli.GeoWaveMain -localingest -b ./ingest -i accumulo -n geowave.50m_admin_0_countries -f geotools-vector -n geowave -u geowave -p XXXXXXX -z localhost:2181


This is the output I get

Feb 02, 2016 12:15:42 PM org.geoserver.platform.GeoServerExtensions checkContext
WARNING: Extension lookup 'GeoServerResourceLoader', but ApplicationContext is unset.
Feb 02, 2016 12:15:42 PM org.geoserver.platform.GeoServerExtensions checkContext
WARNING: Extension lookup 'GeoServerResourceLoader', but ApplicationContext is unset.
Feb 02, 2016 12:15:42 PM org.geoserver.platform.GeoServerExtensions checkContext
WARNING: Extension lookup 'ExtensionFilter', but ApplicationContext is unset.
Feb 02, 2016 12:15:42 PM org.geoserver.platform.GeoServerExtensions checkContext
WARNING: Extension lookup 'ExtensionProvider', but ApplicationContext is unset.
Feb 02, 2016 12:15:42 PM org.geoserver.platform.GeoServerExtensions checkContext
WARNING: Extension lookup 'ExtensionFilter', but ApplicationContext is unset.
Feb 02, 2016 12:15:42 PM org.geoserver.platform.GeoServerExtensions checkContext
WARNING: Extension lookup 'GeoServerResourceLoader', but ApplicationContext is unset.
Feb 02, 2016 12:15:42 PM org.geoserver.platform.GeoServerExtensions checkContext
WARNING: Extension lookup 'GeoServerResourceLoader', but ApplicationContext is unset.
Feb 02, 2016 12:15:42 PM org.geoserver.platform.GeoServerExtensions checkContext
WARNING: Extension lookup 'ExtensionFilter', but ApplicationContext is unset.
Feb 02, 2016 12:15:42 PM org.geoserver.platform.GeoServerExtensions checkContext
WARNING: Extension lookup 'ExtensionProvider', but ApplicationContext is unset.
Feb 02, 2016 12:15:42 PM org.geoserver.platform.GeoServerExtensions checkContext
WARNING: Extension lookup 'ExtensionFilter', but ApplicationContext is unset.
Feb 02, 2016 12:15:43 PM org.geotools.image.ImageWorker <clinit>
INFO: Warp/affine reduction enabled: true


In fact I tried to use wrong info for example to zookeper parameter to force and error, but it doesn't throw any exception. What can I be missing? It seems I'm making a silly mistake here.


Thanks!

_______________________________________________
geowave-dev mailing list
geowave-dev@xxxxxxxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://www.locationtech.org/mailman/listinfo/geowave-dev



_______________________________________________
geowave-dev mailing list
geowave-dev@xxxxxxxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://www.locationtech.org/mailman/listinfo/geowave-dev



Back to the top