Hazelcast v3.12-BETA Release Notes
Release Date: 2019-03-15 // about 5 years ago-
π This document includes the new features, enhancements and fixed issues for Hazelcast IMDG v3.12-BETA-2, Open Source edition release.
π₯ Breaking Changes
- π Support for JDK 6 and 7 has been dropped. The minimum Java version that Hazelcast supports now is Java 8. See the Supports JVMs section.
π New Features
- CP Subsystem: Implementing the Raft consensus algorithm, Hazelcast introduces its CP subsystem which runs within a Hazelcast cluster and offers linearizable implementations of Hazelcast's concurrency APIs. See the CP Subsystem chapter.
- Querying JSON Strings: You can now query JSON strings stored inside your Hazelcast clusters. See the Querying JSON Strings section.
- Pipelining: Introduced pipelining mechanism using which you can send multiple requests in parallel to Hazelcast members or clients, and read the responses in a single step. See the Pipelining section.
- π Support for Multiple Endpoints When Configuring Memberβs Networking: Added the ability to configure the Hazelcast members with separate server sockets for different protocols. See the Advanced Network Configuration section.
- π§ YAML Configuration Support: Added the support for configuring Hazelcast in YAML. See the Configuring Declaratively with YAML section.
β¨ Enhancements
- Client Instance Names and Attributes: You can now retrieve the names of client instances on the member side. Moreover, client attributes have been introduced so that you can group your clients and/or perform special operations for specific clients. See the Defining Client Attributes section.
- Composite Indexes: Introduced the ability to recognize the queries that use all the indexed properties and treat them as a composite, e.g.,
foo = 1 and bar = 2 and foobar = 3
. See the Composite Indexes section. - REST Endpoint Groups: With this enhancement you can enable or disable:
- REST API completely
- Memcache protocol
- REST endpoint groups
π See the Using the REST Endpoint Groups section.
The following are the other improvements performed to solve the enhancement issues opened by the Hazelcast customers/team.
3.12-BETA-2
- β Removed group password from the Hazelcastβs default XML configuration file. Also improved the non-empty password
INFO
message. It's now only logged if security is disabled, password is not empty and password is not the Hazelcast default one. [#14603]
3.12-BETA-1
- π Improved the Javadoc of
HazelcastClient
so that the code comments now use "unisocket client" instead of "dumb client". [#14213] - Introduced the
/ready
endpoint to the REST API to allow checking a member if it is ready to be used after it joins to the cluster. [#14089] - π Improved the syncing of XSD files. [#14070]
- π The
IMap.removeAll()
method now supportsPartitionPredicate
. [#12238] - π Improved the diagnostics tool so that it automatically creates the configured directory for the diagnostic outputs. [#11946]
π Fixes
3.12-BETA-2
- π Fixed an issue where the IP client selector was not working for the local clients. [#14654]
- π Fixed the wording of a misleading error in the first attempt to connect to a wrongly configured cluster. The error message has been changed to βUnable to connect to any clusterβ. [#14574]
- π Fixed the REST service which was not working when the REST endpoint is configured for
AdvancedNetworkConfig
. [#14516] - π Fixed an issue where the
setAsync()
method was throwingNullPointerException
. [#14445] - π Fixed an issue where the collection attributes indexed with
[any]
were causing incorrect SQL query results, if the first data inserted to the map has no value for the attribute or the collection is empty. [#14358] - π Fixed an issue where
mapEvictionPolicy
couldnβt be specified in the JSON configuration file. [#14092] - π Fixed the discrepancy between the XSD on the website and the one in the download package. [#13011]
- π Fixed an issue where
TcpIpConnectionManager
was putting the connections in a map under the remote endpoint bind address but not under the address to which Hazelcast connects. [#11256]
3.12-BETA-1
- π Fixed an issue where the REST API was not handling the HTTP requests without headers correctly: when a client sends an HTTP request without headers to the Hazelcast REST API, the
HttpCommand
class was wrongly expecting an additional new line. [#14353] - π Fixed an issue where
QueryCache
was not returning the copies of the found objects. [#14280] - π Fixed an issue where the locks were not cleaned up after the members are restarted. [#14215]
- π Fixed an issue where the MultiMap's
RemoveOperation
was iterating through the backing collection, which caused performance degradation (when using theSET
collection type). [#14145] - π Fixed an issue where the user code deployment feature was throwing
NullPointerException
while loading multiple nested classes and using entry processors. [#14105] - π Fixed an issue where the newly joining members could not form a cluster when the existing members are killed. [#14051]
- π Fixed an issue where the
IMap.get()
method was not resetting the idle time counter whenread-backup-data
is enabled. [#14026] - π Fixed an issue where the
addIndex()
method was performing a full copy of entries when a new member joins the cluster, which is not needed. [#13964] - π
PagingPredicate
with comparator was failing to serialize when sending from the client or member when the cluster size is more than 1. This has been fixed by making thePagingPredicateQuery
comparator serializable. [#12208]
β Removed/Deprecated Features
- π
ILock
interface and implementation ofILock
has been deprecated, andFencedLock
has been introduced. - π The original implementations of
IAtomicLong
,IAtomicReference
,ISemaphore
andICountDownLatch
have been deprecated. Instead, the implementations provided by the CP Subsystem have been introduced. - π The following system properties are deprecated:
hazelcast.rest.enabled
hazelcast.mc.url.change.enabled
hazelcast.memcache.enabled
hazelcast.http.healthcheck.enabled