THIS IS A TEST INSTANCE. ALL YOUR CHANGES WILL BE LOST!!!!
| ID | IEP-66 |
| Author | |
| Sponsor | Pavel Tupitsyn |
| Created |
|
| Status | DRAFT |
Motivation
Thin clients currently require manual binary configuration for settings like compact footer and simple/full name mapper, which is complicated and error-prone.
Description
Extend the protocol to retrieve those settings automatically on start.
Feature Flag
BINARY_CONFIGURATION bitmask feature flag lets the client know that binary configuration can be requested.
Operation
Name | Code |
|---|---|
OP_BINARY_CONFIGURATION_GET | 3004 |
| Request |
|---|
| (empty) |
| Response | |
|---|---|
| bool | compactFooter |
| byte | binaryNameMapperMode (0 = basic full name, 1 = basic simple name, 2 = custom) |
Assumptions
An alternative approach is to include this information into the handshake, which eliminates an extra request. However, a single partition-aware client performs a handshake with multiple server nodes. Binary configuration is guaranteed to be the same on all nodes in the cluster, so the client only needs to request it once. As a result, it is more efficient to perform one extra request than extending the handshake message.
Discussion Links
// TODO Links to discussions on the devlist, if applicable.
Reference Links
PoC: https://github.com/apache/ignite/pull/8733
Tickets
Overview
Content Tools
Apps
