The GeoMesa 2.0.0 release is a major release comprising over 150 bug fixes and improvements. Dependency versions have been updated, including GeoTools 18 and GeoServer 2.12, Spark 2.2.0 and Kafka 1.0. Functionality and configuration between different data store implementations has been standardized.
The project leadership certifies that the APIs in this release are "Eclipse Quality".
GeoMesa has done significant work in this release to clean up the back-end architecture, making things more modular and re-usable among the various databases supported. Core indexing code has been abstracted out. This greatly simplifies adding new back-ends, and makes bugs easier to fix in one place.
GeoMesa still has a significant overlap with some other spatial indexing projects.
GeoMesa has no know security vulnerabilities at this time.
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)
GeoMesa does not provide a user interface.
End of Life:
Data store connection parameters have been deprecated in favor of standardized keys. For example, "instanceId" has been replaced with "accumulo.instance.id". The old keys will still work, however.
The GeoMesa Spark SQL restful endpoint has been removed. This feature was not being utilized (to our knowledge), and was replaced with better Spark integration across the board.
GeoMesa continues to support OGC standards through the use of GeoTools and GeoServer.
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.