LocationTech GeoMesa 2.1.0 Release Review

Type: 
Release
State: 
Successful
End Date of the Review Period: 

Reviews run for a minimum of one week. The outcome of the review is decided on this date. This is the last day to make comments or ask questions about this review.

Wednesday, August 15, 2018
Release: 

2.1.0

Description: 

The 2.1.0 release is the first minor release for GeoMesa version 2. New features include:

  • Support for Spark 2.3 and improved Pyspark interoperability
  • Type inference for auto ingestion of data
  • Kafka 'event-time' message ordering and support for log compaction
  • Improved support for 'wide' schemas (ones with many attributes)
  • Apache Kudu data store implementation
  • FileSystem data store support for non-point geometries
API Certification: 

The project leadership certifies that the APIs in this release are "Eclipse Quality".

Architectural Issues: 

GeoMesa has done significant work in this release to standardize the converter framework for ingesting data. Pureconfig is used to simplify and standardize converter definitions. The new architecture allows for programatically generating converter defintiions based on custom user data files, lowering the barrier to entry.

GeoMesa still has a significant overlap with some other spatial indexing projects.

Security Issues: 

GeoMesa has upgraded various dependent libraries to patch vulnerabilities, where possible given our environment.

Updated version include:

  • typesafe config 1.2.1 -> 1.3.3
  • json4s 3.2.10 -> 3.5.4
  • scalatra 2.3.0 -> 2.6.3
  • commons-compress 1.4.1 -> 1.16
  • orc 1.4.1 -> 1.4.4
  • specs2 2.6.3 -> 4.3.2
Non-Code Aspects: 

Documentation has been updated and hosted on geomesa.org. Older documentation is still available corresponding to released versions. Tutorials and examples have been updated on github. Older versions are still available as git tags.

Conforms To UI/UX Guidelines: 
Not applicable (project doesn't provide UI)
End of Life: 

The original converter framework has been deprecated in favor of a simpler API. The SftBuilder class has been deprecated and replaced with SchemaBuilder.

Standards: 

GeoMesa continues to support OGC standards through the use of GeoTools and GeoServer.

Communities: 

GeoMesa has established a robust forum for users and adopters on Gitter (https://gitter.im/locationtech/geomesa), where discussions take place most days. As a result, the user mailing list has seen a drop in traffic.

GeoMesa is also active on StackOverflow and StackExchange, responding to all relevant questions that are tagged.