v3.3.0

• fixed a bug in the invalidation flow
• updated some libraries (most notably, jcache from 1.1.0 to 1.1.1)
• fetch requests are distributed among same-fetch-priority clients (if multiple same-fetch-priority clients are holding the requested key)

v3.2.0 [DO NOT USE]

• fixed a bug in the invalidation flow
• updated some libraries (most notably, jcache from 1.1.0 to 1.1.1)
• fetch requests are distributed among same-fetch-priority clients (if multiple same-fetch-priority clients are holding the requested key)
• upgraded target jdk version to 17

v3.1.0

• Thinned the payload of 'Load' requests from the cache-client. Cache value is no longer sent to server (it was not used). No behaviour changes

V3.0.0

This release contains a bug-fix for the cache-client. This fix could highlight issues in your application's invalidation procedure, we recommend to test that your cache invalidation/load procedures are working as intended.

• Fixed a bug where the cache-client would send to the server a PUT request instead of a LOAD request #182

V2.7.0

• Changed messageID generation for client-server messages (see #174)

v2.6.0

What's Changed

• #170 Cache server loose track of client known keys on concurrent fetch and invalidate

No breaking changes

v2.5.0

News:

• Dependencies upgrade

No breaking changes

v2.4.0

News:

• Support for ops/mem usage metrics

No breaking changes

v.2.3.0

News:

• Upgrade ZooKeeper to 3.6.1
• Upgrade Netty to 4.1.50Final
• Upgrade other libraries
• Make blazingcache-services package run on JDK14
• Fix a problem related to unexpected network condition on the server side
• Ensure compatibility with Java runtime from Java 8 up to Java 14

The upgrade from v2.x release line is straightforward, just update your dependencies

v2.2.0

This is a bugfix release.
It now supports officially JDK14