Versions Compared

Old Version 2

changes.mady.by.user Pavel Tupitsyn

Saved on

compared with

New Version 3

changes.mady.by.user Pavel Tupitsyn

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Note about alternative approach

...

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
boolcompactFooter
bytebinaryNameMapperMode (0 = basic full name, 1 = basic simple name, 2 = custom)

Assumptions

// TODO Describe project risks, such as API or binary compatibility issues, major protocol changes, etcAn 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.

...