Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 4 Next »

GeoMesa 2.1.0 is the third minor release in the 2.x line. This release includes 75 bug fixes and improvements since the 2.2.0 release. Users should read the 2.3 upgrade guide.

Dependency Version Updates

  • Airlift Aircompressor compression library upgraded from 0.8 to 0.10.
  • Apache commons-pool2 upgraded from 2.4.2 to 2.6.1.
  • Apache Hive library hive-storage-api upgraded from 2.2.1 to 2.6.0.
  • Apache Orc upgraded from 1.4.4 to 1.5.4.
  • Switch to Geotools gt-epsg-wkt 20.0 (instead of gt-epsg-hsql)
  • Jedis (Redis client) upgraded 2.9.0 to 3.0.1
  • Support for Kafka 2.1.1 added.

Notable New Features and Improvements

  • New GeoMesa Redis DataStore implementation with support for all index types (spatial, spatio-temporal, attribute, and id).
  • GeoMesa Kafka DataStores
    • can read from Confluent Avro-serialized topics
    • support Kafka version 2.1.1.
    • can be configured to start reading from a Kafka topic on GeoServer/DataStore creation.
  • GeoMesa HBase DataStores
    • handle canceled queries and data corruption better.
    • now disable bloom filters by default.
  • GeoMesa FileSystem DataStore optimizations:
    • Metadata store is now pluggable and can use JDBC for persistence.
    • Various other improvements around query performance.
  • GeoMesa Cassandra DataStore has various bug fixes.
  • GeoMesa Spark
    • Improvements to help PySpark users leverage JTS in Spark without using a GeoMesa datastore.
  • GeoMesa Ingest
    • can now accept archive formats (e.g., tars and zips).
    • GeoMesa converters can now read from Avro Schema Registries
    • GeoMesa converters now support composite converters for JSON, and XML.
  • GeoMesa NiFi 
    • GeoMesa processors now support NiFi expressions and variables in configuration
  • GeoMesa Indexing:
    • Support for multiple spatial/spatio-temporal indices on different attributes
    • New API for implementing new index schemes.
  • GeoMesa query handling:
    • Query interceptors for adding custom business logic to queries.
    • Option to allow for or disable 'spatial4j' handling of large polygons.

Deprecated Features and Modules

  • Features
    • Accumulo table-sharing for new schemas (existing schemas still supported)
    • Accumulo pre-computed BIN values
    • Accumulo map-aggregating analytic scans
    • Z2/Z3 non-point support from geomesa-1.2.2 to geomesa-1.2.4 (use XZ instead)
  • Modules
    • Raster support
    • Native API
    • Blob store
    • Metrics


Versions and Compatibility

The 2.x line of GeoMesa follows Semantic Versioning. It provides data compatibility with versions back to 1.2.0. It offers public API compatibility with versions 2.x. It offers binary compatibility with versions 2.3.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 2.3.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.


  • No labels