|Re: [geowave-dev] Geowave and Hbase|
Oh thenI think i will wait for the release to continue my tests, as I need CQL (my plan is to be able to remove accumulo, going only with Hbase).
De: geowave-dev-bounces@xxxxxxxxxxxxxxxx <geowave-dev-bounces@xxxxxxxxxxxxxxxx> en nombre de Rich Fecher <rfecher@xxxxxxxxx>
Enviado: martes, 06 de diciembre de 2016 03:39 p.m.
Asunto: Re: [geowave-dev] Geowave and Hbase
The sizes of those jars will change with the actual release. We are working details of how we want each packaged and deployed now in a branch. For now, that accumulo jar is bloated by hbase dependencies (won't be the case in the release), and the hbase jar is very minimal. The HBase jar will work for server-side spatial and spatial-temporal filtering, but not for arbitrary CQL. We will be more inclusive with the release to enable all things for both datastores.Yes, the "examples" is a good place to look as a very basic starting point. Also, you may be able to find a lot of interesting examples in the "test" project. We use annotations to test all of our underlying datastores (and permutations of versions to support the latest release and the previous minor version release) with the same set of integration tests so that we can be sure we maintain support for all of our advertised capabilities on all of the underlying data store. So for more advanced examples, you can look through our integration tests. Here's an example of how the annotation is used to test basic ingest and query: https://github.com/ngageoint/geowave/blob/master/test/src/test/java/mil/nga/giat/geowave/test/basic/GeoWaveBasicSpatialVectorIT.java#L39
On Tue, Dec 6, 2016 at 1:10 PM, Carl M <soloninguno@xxxxxxxxxxx> wrote:
Back to the top