Hello Pavel, Changing the "compact footer" property for an existing database can lead to compatibility issues. Some clients (at least java) have "false" as the default value of the "compact footer" property, but the default value for the server-side is "true". If thin client will receive binary configuration from the server it will be unable to get values using user-defined type as a key inserted by previous versions of the client (see [1]). Also, AFAIK, some clients still don't have compact footer support. So we should think carefully about how to provide compatibility using this feature (for example, enable this feature only for clusters with no data inserted into caches by previous versions of thin clients)
[1]: https://issues.apache.org/jira/browse/IGNITE-10960 пн, 1 февр. 2021 г. в 19:33, Pavel Tupitsyn <[email protected]>: > Igniters, > > Please review the IEP [1] and let me know your thoughts. > > [1] > > https://cwiki.apache.org/confluence/display/IGNITE/IEP-66%3A+Thin+Client+Automatic+Binary+Configuration >
