Date: Fri, 29 Mar 2024 07:37:48 +0000 (UTC) Message-ID: <1831371760.17.1711697868871@70ea7d456ec1> Subject: Exported From Confluence MIME-Version: 1.0 Content-Type: multipart/related; boundary="----=_Part_16_790336914.1711697868871" ------=_Part_16_790336914.1711697868871 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Content-Location: file:///C:/exported.html
GeoMesa 1.3.2 is the second bugfix release in the Ge= oMesa 1.3 line and includes over 180 fixes and improvements since the 1= .3.1 release!
Improvements / bug fixes
Improvements to= the converter/ETL library (JSON Path handling, etc)= span>
Improvements to Kerberos support for Accumulo and HBase
=Improvements to Spark and Spark SQL support
AgeOff Iterator
Enhancements to the StatsProcess
Tutorials for using GeoMesa with C*, Python, and the Lambda DS.=
Configuration options to permit use with Accumulo Kerberos cluster= s
Improvements to Batch handling and converter ingest error handling=
Additional fixes around classpath handling and UI configuration.= span>
Open-sourced project!
Includes GeoServer output formats for GeoMesa Avro and Arrow file = formats
Includes jar to add Accumulo visibilities to the KafkaDataStore.= span>
Updated to GeoMesa 1.3.2
Released new artifacts on quay.io (https://quay.io/organization/geomesa= )
Documentation here: geomesa.org (http://www.geomesa.org/documentation/tutorials/geodocker-= geomesa-spark-on-aws.html)
1.2 Maintenance Releases - GeoMesa will cont= inue to cut releases on the 1.2.x line of GeoMesa targeted at bugfixes and = stability improvements for existing Accumulo 1.6+ installations. Features m= ay be backported from 1.3 to 1.2, but in general new functionality will be = targeted to 1.3 in order to balance stability with innovation.
GeoMesa 1.3 Compatibility= - The 1.3 line of GeoMesa will be a stable line of GeoMesa release= s that is aimed at providing as much API compatibility= as possible. Our goal is to provide minor version interoperability me= aning that any 1.3.x client or server code can interoperate. This compatibi= lity feature will not be available during the 1.3.0 milestone re= lease phase.
GeoMesa 1.2 Compatibility- T= he 1.2 line of GeoMesa releases provides what we have termed <= em>data compatibility, meaning that data ingested with previo= us versions can still be used with new versions of the GeoMesa JARs. For ex= ample, data ingested with 1.2.0 can be read and written by 1.2.6. This comp= atibility requires that the GeoServer plugin, tools, and distributed runtim= e JARs all have to match in their minor version numbers.