[IGNITE-16038] Java Thin Client: Retrieve binary configuration from server

• Type: Improvement
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 2.11
• Fix Version/s: 2.14
• Component/s: platforms
• Release Note: Java thin: Added automatic binary configuration. Name mapper and compact footer settings will be set according to cluster configuration.
• Ignite Flags: Docs Required, Release Notes Required
• Assignee: Pavel Tupitsyn
• Reporter: Alexandr Shapkin
• Created: 01/Dec/21 13:52
• Updated: 28/Jun/22 08:41
• Resolved: 15/Jun/22 06:53

Description

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

Issue Links

• causes: IGNITE-17247 testValidInvalidNodeAddressesMix hangs sometimes
• is related to: IGNITE-14103 .NET Thin Client: Retrieve binary configuration from server
• links to: GitHub Pull Request #10076
• links to: IEP-67: Thin Client Automatic Binary Configuration - Apache Ignite - Apache Software Foundation