Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Repo info
Activity
  • Jan 31 17:36
    schnerd starred locationtech/geowave
  • Jan 30 11:01
    hsg77 commented #1474
  • Jan 30 10:58
    hsg77 commented #1474
  • Jan 30 10:57
    hsg77 commented #1474
  • Jan 30 10:53
    hsg77 commented #1474
  • Jan 30 10:53
    hsg77 commented #1474
  • Jan 30 10:51
    hsg77 commented #1474
  • Jan 29 16:30
    JWileczek commented #1474
  • Jan 29 16:30
    JWileczek commented #1474
  • Jan 29 16:12
    rfecher commented #1474
  • Jan 29 10:44
    hsg77 commented #1474
  • Jan 28 22:47
    sunapi386 starred locationtech/geowave
  • Jan 28 21:12

    rfecher on gh-pages

    Lastest javadoc on successful t… (compare)

  • Jan 28 20:47

    rfecher on master

    fixing coveralls (#1488) (compare)

  • Jan 28 20:47
    rfecher closed #1488
  • Jan 28 20:47
    rfecher opened #1488
  • Jan 28 17:02

    rfecher on master

    Update README.md (compare)

  • Jan 28 16:53

    rfecher on master

    updated readme.md (#1486) (compare)

  • Jan 28 16:53
    rfecher closed #1486
JackLin
@linHbase
Now I want use geowave store spatial data in Hbase, however i have a question, can i use geowave rest module achieve this goal?
Byunghwa Yun
@combineads
I don't used rest api, but I hope locationtech/geowave#1348 to help.
Byunghwa Yun
@combineads
I personally recommend that you refer to SimpleIngest.java and you develop the api directly.
JackLin
@linHbase
A good suggestion! i will try it, thanks
rfecher
@rfecher
a good suggestion, the provided REST services simply expose the commandline operations via HTTP/JSON but if you want to do something fairly custom you are probably better off developing it directly as suggested - if you want to see more about what is provided the swagger docs are pretty good
you can grab this war and deploy it in a servelt container such as tomcat or jetty
rfecher
@rfecher
then the swagger docs will be at /api such as http://localhost:8080/geowave-restservices-1.0.0-RC1-apache/api
well here is the geowave swagger doc which you can load in swagger-ui :
but for bulk read/write I actually think gRPC is potentially a better choice than traditional REST
JackLin
@linHbase
@rfecher thanks
HuiWang
@scially
How to ingest to geowave from postgresql or mysql?
rfecher
@rfecher
if you have a table in either DB that can be used in GeoServer as a layer, than you could ingest it directly from the geowave CLI, otherwise you'll have to write some code to do the ingest
HuiWang
@scially
ok
Byunghwa Yun
@combineads
@rfecher I upgraded the HBase2 version and fixed the Coprocessor related error. I haven't tested much yet, but I'll share it for your reference. https://github.com/combineads/geowave/tree/hbase2
rfecher
@rfecher
That's great! The plan is immediately after the 1.0 release we wanted to upgrade to hbase 2. This will be very helpful, thanks!
Davis Silverman
@sinistersnare
Hey, when I run geowave gs listds I get an error that seems to be due to wrong Jersey version.
bash-4.4# geowave gs listds
2019-09-05 14:01:23,420 WARN  [main] cli.GeoWaveMain: Unable to execute operation
javax.ws.rs.ProcessingException: javax.ws.rs.core.MultivaluedMap.addAll(Ljava/lang/Object;Ljava/util/List;)V
    at org.glassfish.jersey.client.ClientRuntime.invoke(ClientRuntime.java:261)
    at org.glassfish.jersey.client.JerseyInvocation$1.call(JerseyInvocation.java:684)
    at org.glassfish.jersey.client.JerseyInvocation$1.call(JerseyInvocation.java:681)
    at org.glassfish.jersey.internal.Errors.process(Errors.java:315)
    at org.glassfish.jersey.internal.Errors.process(Errors.java:297)
    at org.glassfish.jersey.internal.Errors.process(Errors.java:228)
    at org.glassfish.jersey.process.internal.RequestScope.runInScope(RequestScope.java:444)
    at org.glassfish.jersey.client.JerseyInvocation.invoke(JerseyInvocation.java:681)
    at org.glassfish.jersey.client.JerseyInvocation$Builder.method(JerseyInvocation.java:411)
    at org.glassfish.jersey.client.JerseyInvocation$Builder.get(JerseyInvocation.java:311)
    at org.locationtech.geowave.cli.geoserver.GeoServerRestClient.getDatastores(GeoServerRestClient.java:703)
    at org.locationtech.geowave.cli.geoserver.GeoServerListDatastoresCommand.computeResults(GeoServerListDatastoresCommand.java:38)
    at org.locationtech.geowave.cli.geoserver.GeoServerListDatastoresCommand.execute(GeoServerListDatastoresCommand.java:29)
    at org.locationtech.geowave.core.cli.GeoWaveMain.run(GeoWaveMain.java:70)
    at org.locationtech.geowave.core.cli.GeoWaveMain.main(GeoWaveMain.java:41)
Caused by: java.lang.NoSuchMethodError: javax.ws.rs.core.MultivaluedMap.addAll(Ljava/lang/Object;Ljava/util/List;)V
    at org.glassfish.jersey.message.internal.InboundMessageContext.headers(InboundMessageContext.java:243)
    at org.glassfish.jersey.client.internal.HttpUrlConnector._apply(HttpUrlConnector.java:406)
    at org.glassfish.jersey.client.internal.HttpUrlConnector.apply(HttpUrlConnector.java:285)
    at org.glassfish.jersey.client.ClientRuntime.invoke(ClientRuntime.java:252)
    ... 14 more
Usage: geowave gs listds [options]
  Options:
    -ws, --workspace
       workspace name
       Default: geowave

Unable to execute operation: javax.ws.rs.core.MultivaluedMap.addAll(Ljava/lang/Object;Ljava/util/List;)V
Seems to be the case for any list* command
rfecher
@rfecher
try java -jar <path to tools jar> gs listds to eliminate anything extraneous on the classpath
the geowave command does try to find libraries for your local spark and hadoop install to add to the classpath which may be where the jersey version conflict comes from
Davis Silverman
@sinistersnare
Same error, my geowave command was aliased to java -cp /opt/hbase/conf:/opt/geowave-cli/geowave-tools.jar org.locationtech.geowave.core.cli.GeoWaveMain so it did the same thing
rfecher
@rfecher
and what version of the geowave tools jar is this?
Davis Silverman
@sinistersnare
bash-4.4# java -jar /opt/geowave-cli/geowave-tools.jar --version
.... # output
 project.branch=GEOWAVE-1565
 project.scm.revision=6f8bded00b20e1496228efad90e8af0893437784
 project.version=1.0.0-SNAPSHOT}
rfecher
@rfecher
hmm, a branch ... I tried this exact thing with the latest install and with RC1 and they worked fine ... maybe whatever commit that is from whatever branch had an issue? can you try perhaps with RC1? http://s3.amazonaws.com/geowave-rpms/release-jars/JAR/geowave-tools-1.0.0-RC1-apache.jar
Davis Silverman
@sinistersnare
Cool, that seems to fix that error. Now I just get a Unable to execute operation: java.net.ConnectException: Connection refused (Connection refused) Which is a step forward!
rfecher
@rfecher
cool! and you have geoserver up and still getting connection refused? if so thats odd, but totally related to networking I would think
glad to have helped!
Davis Silverman
@sinistersnare
yeah my geoserver is running. Would be nice to know which address was refused. Im in k8s, so maybe i messed up my service addresses somewhere
had to redo the config for geoserver. It works now! Thanks for the help, gotta fix the version hash we use for the RPM.
rfecher
@rfecher
the official 1.0.0 will be out by the end of the week so hang tight and grab that - but the commands have changed (to stay, guaranteed through 1.x)
rfecher
@rfecher
for example its geowave gs ds list or geowave gs datastore list instead of geowave gs listds in your version
rfecher
@rfecher
GeoWave 1.0.0 is officially released! See the announcement on the geowave-dev mailing list for more details.
Grigory
@pomadchin
@rfecher :tada: :tada: :tada:
Davis Silverman
@sinistersnare
Will there be a 1.0.0-apache.jar release on http://locationtech.github.io/geowave/packages.html ? I dont see anything right now.
Also congrats on 1.0! Great work Rich and co.
rfecher
@rfecher
The listing is limited to a certain number in that page but it is there. The JavaScript does an S3 bucket listing and just is missing a bunch that are there
Davis Silverman
@sinistersnare
I dont see the release for geowave-tools for 1.0.0
▶ aws s3 ls s3://geowave-rpms/release-jars/JAR/geowave-tools-1.0.0
2019-06-28 11:26:42  355540754 geowave-tools-1.0.0-RC1-apache-accumulo1.7.jar
2019-06-28 11:26:42  355829795 geowave-tools-1.0.0-RC1-apache.jar
2019-06-28 11:26:50  408998836 geowave-tools-1.0.0-RC1-cdh5.jar
2019-06-28 11:26:53  356281268 geowave-tools-1.0.0-RC1-hdp2.jar
2019-09-06 15:54:10  365597604 geowave-tools-1.0.0-hdp2.jar
jhickman-prominent
@jhickman-prominent

RE CLI for ingest: is there a setting for configuring the namespace separator character? My store configuration:

geowave store add -t accumulo -u userxxx -i gwinstance -p passxxx --gwNamespace geowave --zookeeper zk-accumulo:2181 geolife_store

When geowave subsequently attempts to great the metadata table, it uses the underscore (_) separator instead of the expected "dot" (.) separator between the namespace and the table name. I.e., it attempts to create "geowave_GEOWAVE_METADATA" instead of the expected "geowave.GEOWAVE_METADATA". This is failing because my user only has permission to create tables in the "geowave" namespace.

I'm using the new 1.0.0 release of geowave.

jhickman-prominent
@jhickman-prominent
image.png
I think this ^ might be a bug. In Line_110, the code truly is using the underscore (_) character rather than what I believe should be the "dot" (.) character as a namespace separator. I will dig a bit further on this.
rfecher
@rfecher
@jhickman-prominent the geowave namespace is a table prefix and underscores are used for suffixes. An accumulo namespace uses the '.' separator by convention. So if you want to use "geowave" as your accumulo namespace then your geowave namespace should include a '.' otherwise it will be using the default accumulo namespace. So for example with your store above if you used "geowave.geolife" then all your tables would have that prefix and the accumulo namespace would be "geowave" as you are expecting.
jhickman-prominent
@jhickman-prominent
@rfecher , I made the modifications you described and the artifacts were created correctly. Thanks!
rfecher
@rfecher
np, glad to help
gibranparvez
@gibranparvez
Hi, I was wondering where I could find out the storename of my geowave-hbase instance
I'm trying to write a Spark source using the GeoWaveRDDLoader and it seems to require a storename, but i'm not sure how I can figure that out. I can't perform any store operations in the geowave command line either since I don't know the storename
if I log into my hbase I can see the metadata but no key in there with that
Haocheng Wang
@HaochengNn
image.png
i'm running pseudo-distributed mode hbase 1.2.1 with hadoop2.7.7 on my computer, and everything goes well until I place the "geowave-deploy-1.1.0-SNAPSHOT-hbase.jar" to hbase/lib: Hregionserver will quit automatically after I start hbase, and then Hmaster quit. the log of regionserver is this. Can anyone give me some idea to solve this problem?
rfecher
@rfecher
@gibranparvez "storename" is a commandline concept only ... when you run geowave store add ...the primary required parameter is "storename" which is just an arbitrary name you give to that connection configuration so that you can reference it in any subsequent command without needing all the other options. For GeoWaveRDDLoader you need "DataStorePluginOptions" which can be instantiated with any of the data store's required options. So in your case you can use new DataStorePluginOptions(<HBaseRequiredOptions>) to get that. I'm not sure where you're seeing "storename" come from in GeoWaveRDDLoader, but hopefully that clarifies it
rfecher
@rfecher
@HaochengNn the error message appears to be a mismatch between the version of guava in the geowave jar in the version of guava in HBase. It appears that you are building the geowave jar from source, so perhaps just try adding <guava.version>12.0.1</guava.version> after this line and rebuild that geowave-hbase jar