21.1. Installing GeoMesa Kudu


GeoMesa currently supports Kudu version 1.7.x.

21.1.1. Installing the Binary Distribution

GeoMesa Kudu artifacts are available for download or can be built from source. The easiest way to get started is to download the most recent binary version from GitHub.


In the following examples, replace ${TAG} with the corresponding GeoMesa version (e.g. 3.3.0), and ${VERSION} with the appropriate Scala plus GeoMesa versions (e.g. 2.12-3.3.0).

Extract it somewhere convenient:

# download and unpackage the most recent distribution:
$ wget "https://github.com/locationtech/geomesa/releases/download/geomesa-${TAG}/geomesa-kudu_${VERSION}-bin.tar.gz"
$ tar xvf geomesa-kudu_${VERSION}-bin.tar.gz
$ cd geomesa-kudu_${VERSION}
$ ls
bin/  conf/  dist/  docs/  examples/  lib/  LICENSE.txt  logs/

21.1.2. Building from Source

GeoMesa Kudu may also be built from source. For more information refer to Building from Source in the developer manual, or to the README.md file in the the source distribution. The remainder of the instructions in this chapter assume the use of the binary GeoMesa Kudu distribution. If you have built from source, the distribution is created in the target directory of geomesa-kudu/geomesa-kudu-dist.

More information about developing with GeoMesa may be found in the Developer Manual.

21.1.3. Setting up the Kudu Command Line Tools

GeoMesa comes with a set of command line tools for managing Kudu features located in geomesa-kudu_${VERSION}/bin/ of the binary distribution. Configuring the Classpath

GeoMesa needs Hadoop JARs on the classpath. These are not bundled by default, as they should match the versions installed on the target system.

If the environment variable HADOOP_HOME is set, then GeoMesa will load the appropriate JARs and configuration files from those locations and no further configuration is required. Otherwise, you will be prompted to download the appropriate JARs the first time you invoke the tools. Environment variables can be specified in conf/*-env.sh and dependency versions can be specified in conf/dependencies.sh.

In order to run map/reduce jobs, the Hadoop *-site.xml configuration files from your Hadoop installation must be on the classpath. If HADOOP_HOME is not set, then copy them into geomesa-kudu_${VERSION}/conf.

GeoMesa also provides the ability to add additional JARs to the classpath using the environmental variable $GEOMESA_EXTRA_CLASSPATHS. GeoMesa will prepend the contents of this environmental variable to the computed classpath, giving it highest precedence in the classpath. Users can provide directories of jar files or individual files using a colon (:) as a delimiter. These entries will also be added the the map-reduce libjars variable.

Use the geomesa-kudu classpath command in order to see what JARs are being used.

Due to licensing restrictions, dependencies for shape file support must be separately installed. Do this with the following command:

$ ./bin/install-shapefile-support.sh


See Logging Configuration for information about configuring the SLF4J implementation.

Test the command that invokes the GeoMesa Tools:

$ bin/geomesa-kudu
INFO  Usage: geomesa-kudu [command] [command options]

For more details, see Using the Kudu Command-Line Tools.

21.1.4. Installing GeoMesa Kudu in GeoServer


See GeoServer Versions to ensure that GeoServer is compatible with your GeoMesa version.

The Kudu GeoServer plugin is bundled by default in a GeoMesa binary distribution. To install, extract $GEOMESA_KUDU_HOME/dist/gs-plugins/geomesa-kudu-gs-plugin_${VERSION}-install.tar.gz into GeoServer’s WEB-INF/lib directory.

Restart GeoServer after the JARs are installed.