|Re: [geowave-dev] Geowave and Hbase|
I think I manage to compile the hbase ok (although something strange, the geowave-deploy-0.9.3-SNAPSHOT-accumulo-singlejar.jar has a size of 173MB, and the geowave-deploy-0.9.3-SNAPSHOT-hbase-singlejar.jar only has 1.5MB).
As I'm using geowave from java code (not command line) is any java test available to check? Is SimpleHBaseIngestTest the right place to look at? Or do you think is better to wait for the final release?
De: geowave-dev-bounces@xxxxxxxxxxxxxxxx <geowave-dev-bounces@xxxxxxxxxxxxxxxx> en nombre de Rich Fecher <rfecher@xxxxxxxxx>
Enviado: lunes, 05 de diciembre de 2016 04:57 p.m.
Asunto: Re: [geowave-dev] Geowave and Hbase
The build args should be particular to the versions on your cluster (those are for having travis-ci run automated tests on a particular version of cloudera). If you don't override with your own versions, it will use HBase 1.2.3 with Hadoop 2.7.3, and GeoServer/GeoTools 2.10.0/16.0.
At the root level of the project this will build a single jar that you can drop into geoserver:
'mvn package -am -pl deploy -P geotools-container-singlejar'
This will build a jar that gives you all of geowave's commandline tools:
'mvn package -am -pl deploy -P geowave-tools-singlejar'
And if you choose to use HBase custom filters and coprocessors (ie. server-side processing, it will be faster), this is how you build a jar you can put on HBase's classpath. We'll have an rpm that finds HBase's home directory on HDFS and puts it in a lib directory.'mvn package -am -pl deploy -P hbase-container-singlejar'
On Mon, Dec 5, 2016 at 2:15 PM, Carl M <soloninguno@xxxxxxxxxxx> wrote:
Back to the top