Hazelcast IMDG 3.9
Standard Support for IMDG 3.9 will end in October 2019.
Extended Support will continue for an additional 18 months.
Hazelcast IMDG 3.8
Standard Support for IMDG 3.8 ended in February 2019.
Extended Support will continue for an additional 18 months.
For more information see the full list of Version Support Windows.
Maven Repo URL Change
Latest News / Releases
Hazelcast Jet 3.1
- Apache Beam Runner for Hazelcast Jet is released. For more details please see here.
- New hazelcast-jet-contrib repository containing new connectors:
- New AggregateOperations: `filtering` and `flatMapping`
- SourceBuilder API has been extended to add support for fault tolerance
- Support for composite transforms in Pipeline API through the `apply` operator
- Jet now supports YAML configuration as well as XML
- Update Hazelcast IMDG version to 3.12.1
Hazelcast IMDG 3.12.1
Hazelcast IMDG Enterprise New Features
- Added support for updating the licenses of all the running members of a Hazelcast IMDG cluster using the REST API. See the License Information section.
Hazelcast IMDG Open Source Enhancements
- Introduced complete example configurations (XML and YAML) for Hazelcast Java client and client failover. See the Configuring Declaratively section.
- Updated Hazelcast JCache implementation to support JCache 1.1.1. This version of JCache does not introduce new functionalities; it resolves the errata and issues in JCache 1.1.0. See the Upgrading to JCache 1.1.1 section.
Management Center 3.12.1
- Introduced basic management operations for CP Subsystem including promoting a member to become a CP member, removing CP members from the subsystem and restarting the whole CP subsystem. See the CP Subsystem section for more information.
- The "To enter the Management Center license, go to …" hint on the "License" screen is now available only to the admin users.
- Introduced a notification warning when the Management Center user interface could not connect to its backend since, for example, its server is down.
- Added the "publisher ID" information to the WAN replication screen so that you can perform the "WAN Sync" operation in case separate publisher IDs are configured for WAN publishers.
- Added a loading splash during the initial launch for unauthenticated users and introduced a popup dialog to inform the users that their sessions are expired.
- Improved the percentage charts so that they now have predefined vertical axes (y-axes) instead of dynamically ranged values in them.
- Added the "delete configuration" button to the "Set up SMTP Server" dialog.
- Added the "clear history" button to the screen where all the previous instances of an alert are shown (alert history screen).
- Introduced a clustered JMX MBean showing which clusters are being monitored by a Management Center instance.
- Replaced the pie charts on the dashboard screen with the stacked bar charts.
- Added a text field to the page navigation part so that you can type the number of a page you want to view.
- The users are now redirected to the cluster selection dialog upon a successful cluster shutdown operation.
Hazelcast IMDG 3.11.4
Hazelcast IMDG Enterprise for PCF 1.6.5
- Upgrades Hazelcast Enterprise to v3.11.4.
.Net Client 3.12
- Built-in JSON value support.
- Performance improvements.
- Port 5701 usage as the preferred port in case it's not specified.
Python Client 3.12
- JSON Serializer: You can now use the JSON formatted strings or JSON serializable Python objects as objects in the Hazelcast cluster. Starting with Hazelcast IMDG 3.12, the JSON serialization is one of the formerly supported serialization methods. Creating JSON objects in the cluster does not require any server-side coding and hence you can just send a JSON formatted string or JSON serializable Python object to the cluster and query these objects by fields. See the JSON Serialization for details. Examples can be found here.
Node.js Client 3.12
- HazelcastJsonValue: Starting with Hazelcast IMDG 3.12, you can query JS objects stored inside the distributed data structures. Querying can also be made with HazelcastJsonValue using JSON strings.
- Performance: Buffer allocations are revised and string serialization/deserialization methods are replaced with standard API calls. With these changes, the overall performance of the client is significantly increased. There is up to 7000% throughput improvement on the benchmark of map's get operations with 100 KB.
- Custom Credentials: README is updated with a basic sample of custom credentials. Also, an extensive JAAS based custom credentials code sample is provided.
- Benchmarks: Self-throttling benchmarks are updated to reflect the true performance of the client.
C++ Client 3.12
- JSON Serializer: You can now use the JSON formatted strings as objects in the Hazelcast cluster. Starting with Hazelcast IMDG 3.12, the JSON serialization is one of the formerly supported serialization methods. Creating JSON objects in the cluster does not require any server-side coding and hence you can just send a JSON formatted string object to the cluster and query these objects by fields. See the JSON Serialization for details. Examples can be found here.
- Async API: Asynchronous methods are added for more powerful operations like batched writing or reading. The asynchronous methods do not block but return immediately with an ICompletableFuture interface. You can later query the result of the operation using this interface or even provide a callback method to be executed on the user executor threads when the response to the call is received. IMap, Ringbuffer and IAtomicLong support asynchronous operations. See the Using IMap Non-Blocking Async Methods, Using Ringbuffer Non-Blocking Async Methods and Using Atomic Long Non-Blocking Async Methods for details. Examples can be found here.
- Distributed Executor Service: Hazelcast C++ client allows you to asynchronously execute your tasks (logical units of work) in the cluster, such as database queries, complex calculations, and image rendering. With IExecutorService, you can execute tasks asynchronously and perform other useful tasks. If your task execution takes longer than expected, you can cancel it. See the Distributed Executor Service for details. Examples can be found here.
- Pipelining API: With the new Pipelining API, you can send multiple requests in parallel using a single thread and, therefore, increase the throughput. See the Pipelining for details. Examples can be found here.
- Added the missing HazelcastClient::getLocalEndpoint() API so that you can get the client UUID.
Hazelcast Enterprise Kubernetes Operator 0.1This is the initial release of Kubernetes Operator. You can download it from one of the following repositories:
Kubernetes Cloud Discovery 1.5.1
- Enable resolving node name by DNS instead of querying /nodes endpoint of Kubernetes API (used for external smart client scenario)