Arenadata Hyperwave 4.3 adds geospatial analytics and HUE HA

On 9 July 2026, Arenadata introduced Hyperwave 4.3.0, an update to its hybrid data platform. The main changes cover geospatial processing, query history, high availability for the HUE interface, secret management and cluster operations. This is an infrastructure-focused release: its components address concrete analytics and operational tasks rather than adding a single showcase feature.

Geospatial processing through Apache Sedona

The platform now supports Apache Sedona for spatial processing in Spark 3. Arenadata says users can determine whether objects fall inside an area, calculate distances and routes and aggregate events over a coordinate grid.

Potential use cases include logistics, transport, environmental monitoring, mapping, retail and telecom infrastructure. A telecom team could analyse network-asset placement, service areas and operational events. Performance, however, will depend on data volume and quality, partitioning and query design; the announcement does not publish universal benchmark results.

Operational changes

The release includes several day-to-day operations features:

• Trino History Server retains query-execution history;
• HUE gains a high-availability mode using HAProxy across multiple instances;
• a host-level maintenance mode can disable services on selected nodes;
• Java 11 and Java 25 are supported;
• compatibility with Astra Linux 1.8 is stated.

Persistent Trino history can help investigate degradation and compare query changes. HUE high availability reduces dependence on one interface instance, but it does not automatically make the underlying storage, catalogues and compute services resilient. Their topology and recovery scenarios still require separate validation.

Secrets, authentication and isolation

HUE now supports OpenBao/Vault for sensitive configuration. Spark Connect integration and the multi-user Kyuubi gateway include user isolation, LDAP/Kerberos support and SPNEGO authentication for Kyuubi.

An available connector is not a complete access model. An implementation should test secret lifecycle, role separation, audit of administrative activity and behaviour when the secret store is unavailable.

Storage and data exchange

The release adds HBase support in Ozone and the ability to enable Kerberos on an existing Ozone cluster without redeployment. ADB Spark Connector now supports Greengage DB 7, extending exchange between Spark and the current Arenadata DB generation.

Connector upgrades need joint testing on both sides: data types, large batches, retries after faults and partial-failure behaviour. The general method is covered in our guide to external API and integration resilience.

What to test before upgrading

An operations team should obtain and record:

1. the compatibility matrix for current components, Java and the OS;
2. upgrade order and a tested rollback route;
3. HAProxy and HUE health-check requirements;
4. migration of configuration secrets to OpenBao/Vault;
5. Trino History Server retention and storage impact;
6. metadata backup and a recovery test;
7. a representative geospatial-query workload;
8. Ozone, HBase and Kerberos behaviour during partial outages.

Build observability before changing the cluster: establish baseline latency, error and resource metrics, then compare the new state after launch. The wider approach is described in IT infrastructure observability.

Practical conclusion

Hyperwave 4.3.0 expands the platform in three practical areas: spatial analytics, operational visibility and access management. Apache Sedona, Trino history, HUE HA and OpenBao/Vault integration are the most visible additions.

The announcement does not disclose performance results, upgrade duration or ready-made recovery objectives. A move should therefore follow a test with representative geodata, queries and failure scenarios rather than the component list alone.

Source: Arenadata’s official 9 July 2026 announcement.