[
https://issues.apache.org/jira/browse/IGNITE-16038?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17550953#comment-17550953
]
Pavel Tupitsyn commented on IGNITE-16038:
-----------------------------------------
[~alex_pl] [~ashapkin] I propose to do the following:
* Apply server-side binary configuration by default.
* Add *ClientConfiguration#autoBinaryConfigurationEnabled*, default *true* - as
a way to fall back to the old behavior when required.
* List this as a potentially breaking change in the release notes.
Here is a draft PR: https://github.com/apache/ignite/pull/10076
Please have a look and let me know your thoughts. If there are no objections,
I'll finalize the changes next week.
> 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
> Assignee: Pavel Tupitsyn
> Priority: Major
> Time Spent: 10m
> Remaining Estimate: 0h
>
> 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.7#820007)
