Hazelcast Node.js Client 5.3.0

This document includes the new features, enhancements, and fixed issues for the Hazelcast Node.js Client 5.3.0 release.

Breaking Changes

None

New Features

None

Enhancements

• Compact documentation update in #1447
• New types added to binary compatibility test for Portable [API-1677] in #1431
• Do not try to connect cluster members when the client is not connected to cluster [API-1588] in #1444
• Check for the minimum size of the bytes read only once per frame [API-1546] in #1411
• Don't allow empty memberlist on cluster id changes[API-1590] in #1452
• Update Readme and package.json about hazelcast and node.js client in #1471

Fixes

• Change logic around closing connections and writers API-1283 in #1442
• Logging does not work if written in lowercase(hazelcast.logging.level) [API-1740] in #1432

Known Issues

None

Full Changelog: v5.2.0...v5.3.0

Hazelcast Node.js Client 5.2.0

This document includes the new features, enhancements, and fixed issues for the Hazelcast Node.js Client 5.2.0 release.

Breaking Changes

None

New Features

Compact Serialization: Compact serialization was Beta and now it is stable. You can learn more here.
Note: This version of compact serialization works with 5.2 and newer server(where compact serialization is stable) versions

Enhancements

• Add test for proxy APIs to test if they throw serialization errors other than SchemaNotReplicatedError in #1277
• Add undefined to EntryListener interface [API-1417] in #1294
• Fix typos, missing information and not working code samples [API-1067] in #1343
• Port nested compact serialization sample [API-1332] in #1350
• Add map.RemoveAll() method [API-15] in #1364
• Add an example code for map.removeAll method [API-15] in #1369
• Nested compact field's serializer can be None if it is not registered [API-1415] in #1365
• Make ReadResultSet iterable [API-1315] in #1399
• Apply Compact Serialization Updates for Hz v5.2.0 I [API-1637] in #1409
• Add filter argument to ringbuffer readMany() method and a test for it API-1294 in #1414
• Change default cloud coordinator URL to point to Viridian[API-1680] in #1419
• Improve documentation for primitive-nullable primitive field interoperability [API-1579] in #1420
• Send client state to cluster in re-connections[API-1644] in #1415
• Check the member UUIDs that the schema is replicated in the client schema service [API-1646] in #1418
• Do not invoke urgent invocations that contains serialized data immediately[API-1647] in #1422
• Document update for compact in #1433

Fixes

• Add skip checks for 5.2-BETA compatiblity tests in #1356
• Fix memory leak in ReliableTopicListenerRunner.next API-1514 in #1377
• Add 5.2 version checks for the tests that are for map.removeAll in #1391
• Fix invalid error message [API-1490] in #1349
• Change doTryNextCluster logic to make it the same. [API-1354] in #1403
• Remove createDistributedObjectsOnCluster from client start for master branch [API-1224] in #1404

Known Issues

None

Full Changelog: v5.1.0...v5.2.0

Hazelcast Node.js Client 5.1.0

This document includes the new features, enhancements, and fixed issues for the Hazelcast Node.js Client 5.1.0 release.

Breaking Changes

None

New Features

• Compact Serialization Support (BETA): This serialization method is designed to be superior to all existing ones and replace them in the future. It has several advantages over others. You can learn more here.
• SQL JSON support in #1162. You can now use a new JSON type in your SQL queries. Note that this data type is not the same thing as the already existing json-flat mapping. You can learn more here.
• Add bytesSend and bytesReceived tcp metrics in #1087. You can now see these two metrics via Prometheus.
• Introduce security configuration in #1146. You can now use several security configurations easier.

Enhancements

• Add entry validation to setAll and putAll in #1079
• Refactor api doc and add validation errors in #1069
• Add readme sample and point to it from README in #1110
• Validate methods in config in #1080
• Change logo in README in #1124
• Improve security config validation in #1152
• Add caused by for more verbose errors in #1178
• Deprecate statistics props and add metrics props in #1136
• Update SQL JSON code sample for rerunability in #1257
• Add boundary unit tests to datetime classes in #1221
• Update copyright year to 2022 in #1271

Fixes

• Close connection on socket end as well as error in #1098
• Fix custom serializer doc in #1103
• Fix ClusterService's getMembers in #1111
• Fix typo in the token authentication documentation in #1149
• ClientClusterService apply events only with version larger than local version in #1163
• Fix LocalDateTime.fromDate in #1180
• Fix out of date serializers in #1197

Known Issues

• Compact serialization (BETA) does not work with lazy deserialization if the schema needs to be fetched. This is due to technical limitations. In the future, lazy deserialization may be removed to make compact work with such APIs.

Full Changelog: v5.0.0...v5.1.0

Hazelcast Node.js Client 5.0.4

This document includes the new features, enhancements, and fixed issues for the Hazelcast Node.js Client 5.0.4 release.

Breaking Changes

None

New Features

None

Enhancements

None

Fixes

• API-1178 Fix LocalDateTime.fromDate (#1180) [5.0.x] in #1193

Known Issues

None

Full Changelog: https://github.com/hazelcast/hazelcast-nodejs-client/compare/v5.0.3..v5.0.4

Hazelcast Node.js Client 5.0.3

This document includes the new features, enhancements, and fixed issues for the Hazelcast Node.js Client 5.0.3 release.

Breaking Changes

None

New Features

• [API-1018] Introduce security configuration in #1147

Enhancements

• Improve security config validation [5.0.x] in #1154

Fixes

• [BACKPORT 4.2.x] Close connection on socket end as well as error (#1098) in #1108

Known Issues

None

Full Changelog: v5.0.2...v5.0.3

Hazelcast Node.js Client 4.2.1

This document includes the new features, enhancements, and fixed issues for the Hazelcast Node.js Client 4.2.1 release.

Breaking Changes

None

New Features

• [API-1018] Introduce security configuration in #1148

Enhancements

• [BACKPORT] SQL related improvements (#929) in #940
• Improve security config validation [4.2.x] in #1153

Fixes

• [BACKPORT 4.2.x] Close connection on socket end as well as error (#1098) in #1108

Known Issues

None

Full Changelog: v4.2.0...v4.2.1

Hazelcast Node.js Client 5.0.2

This document includes the new features, enhancements, and fixed issues for the Hazelcast Node.js Client 5.0.2 release.

Breaking Changes

None

New Features

None

Enhancements

• Added new metrics tcp.bytesReceived and tcp.bytesSend #1090

Fixes

None

Known Issues

None

Hazelcast Node.js Client 5.0.1

There is no change since 5.0.0 except version change.

This release is needed to fix an npm related mistake in 5.0.0 release. Version 5.0.0 is deprecated in npm. You can use 5.0.1 instead.

Breaking Changes

None

New Features

None

Enhancements

None

Fixes

None

Known Issues

None

Hazelcast Node.js Client 5.0.0

This document includes the new features, enhancements, and fixed issues for the Hazelcast Node.js Client 5.0.0 release.

Breaking Changes

• Client.getSqlService() renamed to Client.getSql() #963
• Year field in LocalDate, LocalDateTime and OffsetDateTime classes is now sent as an integer. This means you should use the 5.0 version of the client with a 5.0 server for SQL compatibility with these types, as the SQL service became stable in 5.0 versions of the client and the server. #963
• SqlService.execute now returns a promise. When the returned promise resolves to the SqlResult, the SqlResult will receive the first response. Therefore, some API of the SqlResult changed because these APIs do not need to wait for execution response anymore. #1046

New Features

• Added distinct aggregator support #1007
• Portable support for DECIMAL, DATE, TIME, TIMESTAMP, TIMESTAMP WITH TIMEZONE #967
• BigInt serialization support #975
• New SQL classes for SQL types: LocalDate, LocalTime, LocalDateTime, OffsetDateTime and BigDecimal. Previously you were using explicit CASTs and strings, now you can use them directly without an explicit CAST. #963

Enhancements

• SQL service is now stabilized. The 5.0 client is fully compatible with the 5.0 version of the server in terms of SQL. #963
• SQL rows are deserialized lazily allowing partial deserialization. #1056
• HazelcastSqlException now has a suggestion field that you can use when your query fails. The field includes a remediation query that you can run to fix the exception. #1055
• Client.shutdown() will return the same promise on multiple calls. #1003
• Document and Validate client properties #1001
• Fail fast on configuration error #959
• Fail fast on wrong failover config key #977
• Documentation and API doc improvements and new code samples #1062 #1060 #1057 #1042 #1000 #993 #974 #973 #966 #956

Fixes

• Throw an error in the absence of a deserializer #957

Known Issues

• getDistributedObjects results in error if the send distributed objects is not known by the Node.js client. There is an ongoing discussion about how to fix this. #982

Hazelcast Node.js Client 4.2.0

This document includes the new features, enhancements, and fixed issues for Hazelcast Node.js Client 4.2.0 release.

New Features

• SQL support: Node.js client now supports querying against the new, state-of-the-art SQL engine introduced in IMDG 4.1. With the new engine:
  • You can query with many new SQL expressions.
  • You can efficiently query large amounts of data.

Note that this feature is currently in beta and requires Hazelcast IMDG 4.2. #918

Enhancements

• Client now fires membership events when hot persistence is enabled. #896
• Added validation for connection retry configuration. #895
• The log message for infinite cluster connection timeout is clearer now. #887
• The usage of defaultNumberType option is now clarified. #871
• The cluster connection timeout for client now is infinite by default, i.e., infinite reconnection attempts. #823
• Replaced UTF with String in reader/writer methods. #802

Fixes

• Now there is no race condition with locks when a CP session hasn't been issued yet. #904
• Fixed an issue where the tried addresses when the client cannot connect to cluster was not properly logged. #826
• Added missing registration for the default list serializers. #799

Breaking Changes

• None.

Known Issues

• None.