GeoMesa Lambda 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 ($VERSION = 1.3.4)
and untar it somewhere convenient. For example, to download and prepare the geomesa-lambda binary:

GeoMesa Lambda 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 Lambda
distribution. If you have built from source, the distribution is created in the target directory of
geomesa-lambda/geomesa-lambda-dist.

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

GeoMesa comes with a set of command line tools located in geomesa-lambda_2.11-$VERSION/bin/ of the binary distribution.

Note

You can configure environment variables and classpath settings in geomesa-lambda_2.11-$VERSION/bin/geomesa-env.sh.

In the geomesa-lambda_2.11-$VERSION directory, run bin/geomesa-lambdaconfigure to set up the tools.

Warning

Please note that the $GEOMESA_LAMBDA_HOME variable points to the location of the geomesa-lambda_2.11-$VERSION
directory, not the main geomesa binary distribution directory.

Note

geomesa-lambda will read the $ACCUMULO_HOME, $HADOOP_HOME and $KAFKA_HOME environment variables
to load the runtime dependencies. If possible, we recommend installing the tools on the Accumulo master server,
as you may also need various configuration files from Hadoop/Accumulo in order to run certain commands.

GeoMesa provides the ability to provide additional jars on 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 mapreduce libjars variable.
Use the geomesaclasspath command to print the final classpath that will be used when executing geomesa
commands.

If you are running the tools on a system without Accumulo, Hadoop, or Kafka, the install-hadoop-accumulo.sh
and install-kafka.sh scripts in the bin directory may be used to download the required JARs into
the lib directory. You should edit this script to match the versions used by your installation.

After GeoServer is installed, you may install the WPS plugin if you plan to use GeoMesa processes. The GeoServer
WPS Plugin must match the version of the GeoServer instance. The GeoServer website includes instructions for
downloading and installing the WPS plugin.

Note

If using Tomcat as a web server, it will most likely be necessary to
pass some custom options:

The value of -Xmx should be as large as your system will permit; this
is especially important for the Kafka plugin. You
should also consider passing -DGEOWEBCACHE_CACHE_DIR=/tmp/$USER-gwc
and -DEPSG-HSQL.directory=/tmp/$USER-hsql
as well. Be sure to restart Tomcat for changes to take place.

To install the GeoMesa Lambda data store as a GeoServer plugin, unpack the contents of the
geomesa-lambda-gs-plugin_2.11-$VERSION-install.tar.gz file in geomesa-lambda_2.11-$VERSION/dist/geoserver/
in the binary distribution or geomesa-$VERSION/geomesa-lambda/geomesa-lambda-gs-plugin/target/ in the source
distribution into your GeoServer’s lib directory ($VERSION = 1.3.4):

There are additional JARs for Accumulo, Zookeeper, Hadoop, Thrift and Kafka that you will need to copy to GeoServer’s
WEB-INF/lib directory. The versions required will be specific to your installation. For example, GeoMesa only
requires Hadoop 2.2 or better, but if you are using Hadoop 2.5.0 you should use the JARs
that match the version of Hadoop you are running.

There are scripts in the geomesa-lambda_2.11-$VERSION/bin directory
(install-hadoop-accumulo.sh, install-kafka.sh) which will install these dependencies to a target directory
using wget (requires an internet connection).

Note

You may have to edit install-hadoop-accumulo.sh and/or install-kafka.sh to set the
versions of Accumulo, Zookeeper, Hadoop, Thrift and Kafka that you are running.

If you do no have an internet connection you can download the JARs manually via http://search.maven.org/.
These may include the JARs below; the specific JARs needed for some common configurations are listed below:

GeoMesa supports Accumulo 1.8 when built with the accumulo-1.8 profile. Accumulo 1.8
introduced a dependency on libthrift version 0.9.3 which is not compatible with Accumulo
1.7/libthrift 0.9.1. The default supported version for GeoMesa is Accumulo 1.7.x and
the published jars and distribution artifacts reflect this version. To upgrade, build
locally using the accumulo-1.8 profile.

Some GeoMesa-specific WPS processes such as geomesa:Density, which is used
in the generation of heat maps, also require geomesa-process-wps_2.11-$VERSION.jar.
This JAR is included in the geomesa-lambda_2.11-$VERSION/dist/gs-plugins directory of the binary
distribution, or is built in the geomesa-process module of the source
distribution.

To upgrade between minor releases of GeoMesa, the versions of all GeoMesa components
must match. This means that the version of the geomesa-distributed-runtime
JAR installed on Accumulo tablet servers must match the version of the
geomesa-plugin JARs installed in the WEB-INF/lib directory of GeoServer.

We strive to maintain backwards compatibility for data ingested with older
releases of GeoMesa, and in general data ingested with older releases
may be read with newer ones (note that the reverse does not apply). For example,
data ingested with GeoMesa 1.2.2 may be read with 1.2.3.

It should be noted, however, that data ingested with older GeoMesa versions may
not take full advantage of indexing improvements in newer releases. If
it is not feasible to reingest old data, see Updating Existing Data to the Latest Index Format
for more information on updating its index format.