GeoMesa 3.1.0 Release Notes

Owned by James Hughes
Last updated: Oct 27, 2020 by Emilio Lahr-Vivaz
2 min read

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

Dependency Version Updates and new Supported Versions

  • Updated to GeoTools 23.3 (from 23.0) and GeoServer 2.17.3 (from 2.17.0)
  • Updated to Avro 1.8.2 (from 1.7.5)

Notable Features 

  • Query Guards
    • Created an API for Query Guards to block overly-broad queries from running
    • Implemented temporal and graduated spatial-temporal query guards
  • GeoMesa-NiFi
    • New GetGeoMesaKafkaRecord processor reads from Kafka and creates NiFi Records
    • New GeoAvro RecordSetWriter to convert NiFi Records into Avro with geometries
    • The GeoMesa NiFi processors can accept NiFi Records, allowing for more flexibility when creating flows

  • HBase

    • GeoMesa's HBase integration now supports data age-off

  • Various

    • Json filter improvements
    • Optimizations for GeoTools/GeoServer integration points (GeoTools visitors and other query patterns)

Bug Fixes

  • Various Arrow Memory leaks have been addressed
  • Various corner cases around handing Kryo data, metadata, and configuration.

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.1.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.

Upgrading

GeoMesa 3.1.0 supports upgrade in place from previous versions of 2.x or 3.0.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.