The 2.3.0 release is the third minor release in the 2.x line. New features include:
Support for multiple spatial/spatio-temporal indices on different attributes
Query interceptors for adding custom business logic to queries
New data store implementation backed by Redis
FIleSystem data store optimizations
The project leadership certifies that the APIs in this release are "Eclipse Quality".
GeoMesa has done significant work in this release to refactor the core indexing code, making it easier to extend and implement for new data stores. This effort was validated by adding a new Redis data store implementation.
GeoMesa still has a significant overlap with some other spatial indexing projects.
There have been no work on security issues related to this release.
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 following features have been deprecated:
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)
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. GeoMesa continues to maintain a developers (https://locationtech.org/mhonarc/lists/geomesa-dev/) and users (https://locationtech.org/mhonarc/lists/geomesa-users/) mailing list.
GeoMesa is also active on StackOverflow and StackExchange, responding to all relevant questions that are tagged.