Hello! The Ignite team draws attention to the changed default behavior of Java thin clients since Ignite release 2.14.
Before release 2.14, the default value for the flag BinaryConfiguration#compactFooter differed on Java thin clients (false) and client/server nodes (true). For details about the flag, check out this doc [1]. This difference has an unexpected side effect for caches that use POJO as cache key. A key inserted from the thin client (with the default BinaryConfiguration) is not visible from client or server nodes, and vice versa. It means `get(PojoKey)` started on the server returns NULL for the `PojoKey` inserted by the thin client. This behavior was changed in release 2.14. Now the Java thin client retrieves BinaryConfiguration from the server and overrides the configured or default one. It fixes the side effect described above for new clients. But it might affect users who, at the same time, rely on the default BinaryConfiguration and use POJO as cache key in such cases: 1. Persistence is enabled, and the storage is filled by an older Java thin client (e.g., 2.13). After upgrading the thin client to 2.14, it will not observe existing keys. 2. Different versions of Java thin clients are used simultaneously (e.g., 2.13 and 2.14). Keys inserted by one client will not be visible to another. If this change affects you, there are two possible solutions: 1. Align configurations on server and thin clients: set `BinaryConfiguration#compactFooter = false` on server nodes. You must be confident that all data in the persistent storage is inserted only by thin clients. 2. Fallback to the previous behavior: set `ClientConfiguration#setAutoBinaryConfigurationEnabled = false` on Java thin clients. [1] https://ignite.apache.org/docs/latest/binary-client-protocol/data-format#schema On Wed, Oct 12, 2022 at 4:10 PM Pavel Tupitsyn <ptupit...@apache.org> wrote: > A small post about .NET changes: > https://ptupitsyn.github.io/Whats-New-In-Ignite-Net-2.14/ > > Cheers! > > On Tue, Oct 11, 2022 at 10:56 AM Taras Ledkov <tled...@apache.org> wrote: > > > The Apache Ignite Community is pleased to announce the release of > > Apache Ignite 2.14.0. > > > > Apache Ignite® is an in-memory computing platform for transactional, > > analytical, and streaming workloads delivering in-memory speeds at > > a petabyte scale. > > https://ignite.apache.org > > > > For the full list of changes, you can refer to the RELEASE_NOTES list > > which is trying to catalogue the most significant improvements for > > this version of the platform. > > https://ignite.apache.org/releases/2.14.0/release_notes.html > > > > Download the latest Ignite version from here: > > https://ignite.apache.org/download.cgi > > > > Please let us know if you encounter any problems: > > https://ignite.apache.org/community/resources.html#ask > > > > -- > > With best regards, > > Taras Ledkov > > >
