[
https://issues.apache.org/jira/browse/IGNITE-16038?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17452326#comment-17452326
]
Aleksey Plekhanov commented on IGNITE-16038:
--------------------------------------------
[~ashapkin], this change will break compatibility (as already mentioned in
IEP). For example, if the server was configured with PDS and default binary
configuration (compact footer = true), and the client was configured with
default binary configuration (compact footer = false), after upgrading to the
new Ignite version thin client will get server's settings and can't read keys
stored by old thin client version.
> Java Thin Client: Retrieve binary configuration from server
> -----------------------------------------------------------
>
> Key: IGNITE-16038
> URL: https://issues.apache.org/jira/browse/IGNITE-16038
> Project: Ignite
> Issue Type: Improvement
> Components: platforms
> Affects Versions: 2.11
> Reporter: Alexandr Shapkin
> Priority: Major
>
> Thin clients require manual binary configuration currently. Settings like
> compact footer and simple/full name mapper should be set to match the cluster
> settings. Extend the protocol to retrieve those settings automatically on
> start.
>
> I.e. it's impossible to read a value inserted by a thick client with java
> thin client without specifying compactFooter=true
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
