thanks for the reply. Yes, after using
geomesa-hbase-distributed-runtime-hbase1_2.11-3.0.0.jar in all nodes,there are no errors while making WMS requests. I did not alter the existing HBase tables though. The coprocessor attribute is defined as:
If you're using hbase 1.4, you should use the
`geomesa-hbase-distributed-runtime-hbase1_2.11-3.0.0.jar`, not the
`hbase2` jar. You may also need to use the hbase shell to 'alter
table' and point to the new jar. If you ingest the example csv or
run the quickstart into a new table, you should be able to see the
correct coprocessor configs on that table, which you can then copy
to your existing tables. Also make sure the
geomesa-hbase-distributed-runtime jar is on each region server and
the master node (you can install it in hdfs to avoid having to copy
it around the cluster).
On 9/21/20 11:25 AM, Sangeetha S wrote:
In the last few days, I've been testing out the same
process with GeoMesa 3.0.0. This time, I encountered a
different error at a previous step. I'll start with the
steps I had done during installation and provide the error
details at the end of this message. That might perhaps give
a clue on why this is happening.
I stopped HBase and copied the geomesa-hbase-distributed-runtime-hbase2_2.11-3.0.0.jar
to the lib directory of hbase. Restarted HBase
In a fresh installation of GeoServer 2.17.0, I
installed the WPS extension.
Then, I copied all the jars in geomesa-hbase-gs-plugin_2.11-3.0.0-install.tar.gz
folder of GeoServer.
I copied the geomesa-process-wps_2.11-3.0.0.jar
to the same folder.
I copied the following jars into the same folder:
Created HBase GeoMesa datastore and a layer
When I preview the layer with Openlayers option, I get
an error: Could not
obtain the next
The entire stack
trace is attached with this email. WFS requests work fine,
but WMS does not work. I tried to apply the heatmap style
from here (https://www.geomesa.org/documentation/stable/tutorials/geomesa-examples-gdelt.html),
however, that results in the same error. The missing class
seems to be defined in geomesa-hbase-rpc_2.11-3.0.0.jar and this jar is already in
the WEB-INF/lib folder of the GeoServer. I tested with
GeoServer 2.16.0 also and the results are the same.
In the newly released 3.0 we've upgraded hbase client
version to 1.4.12. Also, the hbase client jars are no
longer bundled in a shaded jar, so you should be able to
swap them out to your specific version in a geoserver
instance without rebuilding the plugin.
On 6/25/20 4:50 AM, Sangeetha S wrote:
I haven't yet tried to change the HBase version
and rebuild the plugin jar. However, I installed the
newly released GeoMesa 2.4.1 and I hit the same
I hit the same error recently. I think something
changed in a recent bug-fix version of HBase 1.4.
For instance, it works with 1.4.4 but doesn't seem
to work with 1.4.12. At this point, I'd recommend
checking out the geomesa source code and modifying
the pom.xml <hbase.version> to 1.4.12, then
re-building the geomesa-hbase-gs-plugin shaded
On 5/22/20 10:18 AM, Sangeetha S wrote:
Thanks a lot for the detailed steps. I
followed the same, however there is an error
while creating a datastore in the GeoServer.
I have attached the error with this email.
Could you please look at it?
In a newly installed
GeoServer, I installed the
WPS extension and then
to WEB-INF/lib folder of
GeoServer. However, the
GeoServer does not start
your reply. I
have added to
all jars present
as well as the
let you know how
I think the
from using the
Could you try
list of jars
stored in an
is running on
top of Hadoop
HDFS. I have
layer in the
When I use the
style, I am
able to make
I execute the
process, I get
the error the