Skip to content

Hazelcast Node.js Client 5.1.0
Compare
Choose a tag to compare
@srknzl srknzl released this 29 Apr 12:46
· 70 commits to master since this release
v5.1.0
a1a047c

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

Assets 2
Loading