5.3.0 Release Notes

Hazelcast was sending requests to Kubernetes API when deploying an application with embedded Hazelcast and service-dns (DNS lookup mode) specified to a Kubernetes cluster. This was causing the requests to be unsuccessful and the application not to start. This mechanism has been improved by creating Kubernetes client only for the DNS lookup mode. #23883

When advanced networking is enabled, the Kubernetes discovery plugin might have been discovering several endpoints (per each port) for each member’s pod. The discovery plugin now matches only the private IP per endpoint, ignoring the port values. #23766

Added support of IMDSv2 for Hazelcast’s AWS Discovery plugin. #23545

Added the support of discovering ECS and EC2 members on AWS. See Deploying a Cluster on Amazon AWS. #22411

Enterprise Edition Enhanced the experience of using Hazelcast with persistence under Kubernetes by removing requirements for manual interventions. Previously, when there was a restart on such a cluster, the cluster states were needed to be changed manually. For some cases, this might have led to data loss. Now, the shutdown process is automated. See Configuring Kubernetes for details. #21844

Disk tier option of Tiered Storage is now disabled by default. #23747

Hazelcast no longer depends on JRuby; the JRuby ScriptFactory dependency must be explicitly added to the application. #23355

Added the Kafka Connect extension to the distribution. #23312

Shaded dependencies for Hazelcast Platform have been combined in a dedicated package (com.hazelcast.shaded). #23124

Added socket options for per-socket keep-alive configuration: keep-count, keep-idle-seconds, and keep-interval-seconds. You can set these options using either the advanced network configurations or Hazelcast system properties. See Configuring TCP Keep-Alive. #23816, #24050

The CREATE MAPPING statement for Compact Serialization now supports nullable primitives. #24300

Implemented the GET_DDL function. #23595

Implemented the SHOW DATA CONNECTIONS statement to show the connections created by the CREATE CONNECTIONS statement. #24028

Added support for providing declarative partitioning strategies based on attributes. These attributes represent specific partition keys for a map. You can also configure this strategy dynamically. #23535, #23954

Improved the nested loop joins algorithm by making the CreateDagVisitor interface generic. #23368

Implemented the TO_CHAR function which is capable of formatting dates, timestamps, and numbers. #22529

Implemented JSON=VARCHAR comparison. #22746

Each Jet engine job was creating a client for connecting to the remote cluster, resulting in an excessive number of clients. This has been fixed by introducing a single data connection which can be reused for all job instances. #23472, #23849

Added MongoDB read (source) and write (sink) processors. #23348

Introduced JobStatusListener as an alternative to retrieve a job status via the Job.getStatus() method. #23193

Updated the job API to add the ability to distinguish the user-cancelled jobs from the failed ones. #22924

Added flock to guard all the concurrent pip executions (upgrading pip and protobuf versions) in the Jet-to-Python script. #22829

Added the TLS configuration property keyMaterialDuration which allows using a configurable timeout for caching keyStores and trustStores. See TLS Configuration for the details on how to configure this property. #23307

Hazelcast now allows serializing unsupported types via zero-configuration provided that there is an explicit serializer implemented for the unsupported type. #23449

Setting a generic record now fails if the value is not of the same type of generic record. #23522

Introduced clearer exception messages for Generic MapStore, instead of UndefinedErrorCodeException. #22765

Added the REST endpoint /hazelcast/rest/wan/sync/progress which allows tracking the WAN synchronization progress. #22958

Added support for predicates in DML (Data Manipulation Language) in JDBC SQL connector. #24521

Added the ability to provide host, username, password, and authDB when connecting to a MongoDB, as an alternative to specifying a connection string. #24238

Added the ability to create a mapping with a MongoDB data connections that provides unbounded (streaming) results. #24356

Added compound identifier for the externalName() method. #23772

Added an option for the MongoDB source to perform reading with a single processor instance. Usually distributing the operations is the best practice; however, the $function aggregation method is not supported by the Atlas Serverless instances. In this case, this newly introduced option can be used to query such instances in one processor. See the option’s documentation. #24198

Added additional permission checks to JDBC connectors (source and sink). The previous checks in some cases used only the jdbc: name in ConnectorPermission. The newly introduced checks get the JDBC URL from existing connection metadata and check if the permission is granted. If you want to grant a ConnectorPermission to all JDBC URLs, you may use wildcards, e.g., jdbc:*. #23716

Added DataConnection for Kafka consumers and producers, and for MongoDB #23886, #23837

Jet engine’s connector for MongoDB is now a part of the Hazelcast Platform distribution. #22565

Added name of the job to the job-specific metrics. #23744

Added Tiered Storage compactor metrics to be exposed by the tools and interfaces such as Management Center, JMX, and diagnostics. #23643

Added a new tag to the CP Subsystem metrics to display the client names for CP sessions on Hazelcast Management Center. #23387

Added entry eviction and expiration counts to local map statistics and metrics. #23318

External Data Store references have been renamed as _Data Connections. This includes the renaming of the external-data-store configuration element as data-connection. #24224

Added the ability to test whether the connection with a JDBC data link is valid (testConnection method for JdbcDataConnection). #23405

Upgraded Apache Calcite to 1.32.0. #22849

Added confirmation that Hazelcast Platform has been tested on x86_64 and AArch64/ARM64 system architectures from Platform 5.3.