Thank you very much Rich.
Great to know that Hbase support is almost ready. Do you have an estimated time for the 0.9.3 release?
In the meantime maybe i could play with it and build it myself, could you tell me the right BUILD_ARGS i need to use? I think I found one line in travis.yml in repo code, but I'm not sure if they are ok as they have a reference to accumulo
"ACCUMULO_VERSION='1.6.0-cdh5.1.4' ACCUMULO_API='1.6' HBASE_VERSION='1.2.0-cdh5.7.1' HADOOP_VERSION='2.6.0-cdh5.4.0' GEOTOOLS_VERSION='16.0' GEOSERVER_VERSION='2.10.0' PLATFORM_VERSION='cloudera' BUILD_DOCS=false"
As I understand, after building the client I would only need to change the guava version in geoserver, is that right?
De: geowave-dev-bounces@xxxxxxxxxxxxxxxx <geowave-dev-bounces@xxxxxxxxxxxxxxxx> en nombre de Rich Fecher <rfecher@xxxxxxxxx>
Enviado: lunes, 05 de diciembre de 2016 03:40 p.m.
Asunto: Re: [geowave-dev] Geowave and Hbase
Yes, we have been working hard to ensure *everything* is supported in HBase that is supported in Accumulo, to include the GeoServer plugin. Our upcoming 0.9.3 release is the first release that will have full HBase support with comparable performance
so one could reasonably choose between Accumulo and HBase based on your needs. 0.9.3 will officially be released very soon, currently we are in final stages of ensuring complete Google BigTable support in this release as well. In the meantime, if you were
to try to build the latest yourself, the most significant catch to having an HBase client within the same webapp as GeoServer is differing guava versions and in particular usage of conflicting Stopwatch calls between GeoServer and HBase's client (https://issues.apache.org/jira/browse/HBASE-15737
We have applied this patch to remedy our distribution - so our packaged jars and rpms that we distribute will work seamlessly without worrying about this conflict.
But I'm bringing it to your attention ahead of time in case you decide to build it yourself. Alternatively Guava 16.0 has proven to work with both HBase and GeoServer from our testing (GeoServer comes with Guava 17.0 however so you'd have to remove that and
add guava 16.0 to work around the problem this way).