GeoMesa 3.0.0 Release Notes

GeoMesa 3.0.0 is the first major release in the 3.x line. This release includes 127 new features and bug fixes since the 2.4.0 release. Users should read the 3.0 Upgrade Guide.  Install bundles for LocationTech GeoMesa can be downloaded from GitHub or Maven central.  GeoMesa-NiFi Nars are available on GitHub and Maven central.

Dependency Version Updates and new Supported Versions

  • Update to GeoTools 23.0 and GeoServer 2.17
  • Added support for Accumulo 2.0 (Accumulo 1.9.x still supported)
  • Added support for HBase 2.x (HBase 1.4.x still supported).
  • Update Hadoop compile version to 2.8.5.  (And we've tested with Hadoop 3.x.)

Notable Features 

  • HBase

    • GeoMesa Coprocessors can be configured to yield ‘partial results’

    • GeoMesa Coprocessors can be enabled / disabled individually

    • Scan ranges are grouped by region instead of by region servers
  • Accumulo

    • Tested on Accumulo with S3

    • Switched unit tests from using MockAccumulo to MiniAccumuloCluster

  • Timeouts have been revamped.  Each DataStore will manage timeouts as it makes queries.
  • Various

    • Numerous improvemenst to the FileSystem DataStore
    • Cleaned up Arrow memory usage

    • Small enhancement in SFCurve which allows for improved range management

    • WKB improvements (both in serialization and handing for Z and M dimensions)


  • Raster support has been removed
  • The 'Native' API and Blob Storage have also been removed
  • See a complete list in the upgrade guide

Versions and Compatibility

The 2.x and 3.x lines of GeoMesa follows Semantic Versioning. It provides data compatibility with versions back to 1.2.0. GeoMesa 3.x offers public API compatibility with versions 3.x. It offers binary compatibility with versions 3.0.x.

Note that the GeoMesa public API is not currently well defined. Users with deep code integration with GeoMesa may need to update some calls.


GeoMesa 3.0.0 supports upgrade in place from previous versions of 2.x, by updating the GeoMesa JAR versions. Ensure that JARs are updated in all clients and servers. See the upgrade guide for information on changes that may affect you after the update.