Skip to main content

5.2 Release Notes

Patch Releases​

All patch release notes for 5.2.x are available on the releases page.

Configuration​

Replicated set_configuration​

The set_configuration operation now accepts "replicated": true to apply a configuration change to all cluster nodes in a single Operations API call, with per-node outcomes reported in the response's replicated array. Only cluster-appropriate parameters should be replicated — see Configuration Operations.

Replication​

Replicating the System Database with a Constrained Topology​

Controlled-flow replication can now include the system database while keeping a constrained (non-mesh) topology.

Previously, replicating system was discouraged when using controlled replication flow: because the node registry (hdb_nodes) lives in system and each node advertised itself as a full-mesh participant, replicating system caused every node to discover and directly connect to every other node — defeating the point of a constrained topology.

As of 5.2, a node with directional routes advertises a directional registry record derived from those routes (the neighbors it sends to / receives from) instead of a blanket "connect to everyone." Discovered non-neighbor nodes therefore never open direct connections. This lets central configuration — users, roles, and schemas — propagate transitively across the entire cluster while user-database connections stay on the routes you configured.

For example, in a roadside → middle → core aggregation tree, replicating system now lets a role created on a roadside node reach the core (through the middle tier) without the core ever opening a direct socket to a roadside node.

Behavior notes:

  • This applies only to nodes that have directional routes. A node with no directional routes keeps the legacy full-mesh advertisement, so existing full-mesh clusters are unaffected.
  • add_node / set_node with database-scoped sendsTo / receivesFrom entries now restrict replication to those databases (consistent with the config-route behavior). To replicate all databases while excluding specific tables, use a wildcard entry (excludeTables with no database).
  • Central visibility of every node is not guaranteed: an aggregation node may not list every distant leaf in its hdb_nodes registry. This does not open a connection either way.

See Controlling Replication Flow for configuration details.