Hazelcast Node.js Client 3.12

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

New Features

• HazelcastJsonValue: Starting with Hazelcast IMDG 3.12, one can query JS objects stored inside the distributed data structures. Querying can also be made with HazelcastJsonValue using JSON strings. #468

Enhancements

• Performance: Buffer allocations are revised and string serialization/deserialization methods are replaced with standard API calls. With these changes, overall performance of the client is significantly increased. There is up to 7000% throughput improvement on the Imap#get benchmark with 100KB string values. #473

• Custom Credentials: README is updated with a basic sample of custom credentials. Also, an extensive JAAS based custom credentials code sample is provided. #466

• Benchmarks: Self-throttling benchmarks are updated to reflect the true performance of the client. #467

Fixes

• Formerly, lifecycle event changes was not logged. Now, they are logged with the info level #471
• Missing statistics like os.processCpuTime are added and some statistics collection mechanisms are updated. #451
• Client connection was not sending ping to member when it is constantly reading but not writing any data. #450

Breaking Changes

• String Serialization: Hazelcast Node.js client now follows UTF-8 standard (RFC 3629) for string data type serialization of 4 byte UTF characters. This may lead to compatibility issues with Hazelcast IMDG 3.x and other client libraries for string and JSON values. See String Serialization section for more information.

Known Issues

None.

Hazelcast Node.js Client 0.10

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

Enhancements

• Added support for client statistics. [#275]
• Enhanced the client's documentation. [#340]
• Added support for the client so that it can connect to the cluster using SSL without specifying certificate authorities. [#403]
• Exposed ConfigBuilder so that the users can use it to extend their configurations. [#375]

Fixes

• Fixed an issue where the client was hanging forever without giving any errors, when the server side does not support the Open Binary Protocol. [#132]
• Fixed the bluebird deprecation warnings which had been logging while the client is connected to the Hazelcast instance. [#251]
• Fixed an issue where the client was reporting the previous release version. [#351 , #417]
• Fixed an issue where the ProxyManager's proxies map was using only the object names as keys. Now, this map uses the namespace including service name, too. [#361]

Breaking Changes

• Unified the API calls to register listeners. [#355]
• Calls such as client.getMap and client.getList now returns promises. See below.

Old API:

var map = client.getMap('mapName');
map.put('key', 'value');

New API:

client.getMap('mapName').then(function(map) {
    return map.put('key', 'value');
});

Hazelcast Node.js Client 0.9

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

Enhancements

• Improved logging on connection to the cluster. [#291]
• Added more recommended rules to tslint. [#296]
• Updated scripts. [#299]
• Implemented Hazelcast Cloud Discovery for Node.js client. [#303]
• Implemented AddressProvider and AddressTranslator. [#306]
• Added Readme for the code-samples repo folder. [#317]

Fixes

• Fixed an error in Portable Serialization when nested portables are used. [#292]
• Fixed an error in Client SSL Authentication Test. [#301]
• Fixed an error in Map Partition Aware Test. [#309]
• Fixed errors in Near Cache. [#312]

Breaking Changes

Plain strings are used to specify member addresses instead of Address objects when configuring Hazelcast Client programmatically.

Old configuration:

        var cfg = new Config.ClientConfig();
        cfg.networkConfig.addresses = [
            new Address('0.0.0.0', 5709),
            new Address('0.0.0.1', 5710)
        ];

New configuration:

        var cfg = new Config.ClientConfig();
        cfg.networkConfig.addresses = [
            '0.0.0.0:5709',
            '0.0.0.1:5710'
        ];

Hazelcast Node.js Client 0.8

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

New Features

• Fast Aggregations
• Flake Id Generator
• CRDT Counter
• Declarative Configuration

Enhancements

There are no enhancements for this release.

Fixes

• #260

Known Issues

None.

Hazelcast Node.js Client 0.7

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

New Features

• Eventually consistent near cache
• SSL Mutual authentication

Enhancements

There are no enhancements for this release.

Fixes

• #233
• #208
• #207
• #192

Known Issues

None.

Hazelcast Node.js Client 0.6.2

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

New Features

There are no new features for this release.

Enhancements

There are no enhancements for this release.

Fixes

• #193
• #187
• #185
• #180
• #179
• #175
• #174
• #167

Known Issues

None.

Hazelcast Node.js Client 0.6.1

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

New Features

• Atomic Long
• Semaphort
• Replicated Map

Enhancements

There are no enhancements for this release.

Fixes

• #168

Known Issues

None.

Hazelcast Node.js Client 0.6.0

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

New Features

• Near Cache support for Map

Enhancements

There are no enhancements for this release.

Fixes

• Fix string serialization error with high order unicode characters. #163
• Fix unhandled heartbeat reject. #150

Known Issues

None.

Hazelcast Node.js Client 0.5.0

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

New Features

• Secure connection to cluster using SSL (requires an enterprise cluster)
• Ringbuffer
• Reliable Topic

Enhancements

• Improved logging on connection failure; the error message issued when there is a connection failure should include addresses. [#147]

Fixes

• Fix error in cluster connect on Node.js version 6 and higher. [#143]

Known Issues

None.

Hazelcast Node.js Client 0.4.1

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

New Features

• Implemented Entry Processor support
• Added PartitionAware support for Map keys

Known Issues

None.