THIS IS A TEST INSTANCE. ALL YOUR CHANGES WILL BE LOST!!!!
| ID | IEP-76 |
| Author | |
| Sponsor | |
| Created |
|
| Status | DRAFT |
Motivation
Thin client protocol will be the primary way to interact with Ignite 3.0 from code.
Description
Adapt Ignite 2.x protocol for Ignite 3.0. Main differences are:
- MsgPack as underlying binary format (IEP-75 Thin Client MsgPack Serialization)
- Different set of data types (IEP-54: Schema-first Approach)
- More flexible and extensible handshake with magic header string
TCP Socket
- Every Ignite node listens on a TCP port. Thin client implementations connect to any node in the cluster (possibly multiple nodes) through a TCP socket and perform Ignite operations using a well-defined binary protocol.
- Server-side connection parameters are defined in
ClientConnectorConfigurationclass.- Default port is 10800.
- Connector is enabled by default, no configuration changes needed.
- Netty is used on the server for network IO.
Data Format
MsgPack is used for data serialization.
Data Types Mapping
Ignite data types defined in IEP-54 map to MsgPack data types the following way:
Ignite Type | Size | MsgPack Type | Notes |
|---|---|---|---|
| Bitmask(n) | ⌈n/8⌉ bytes | bin8 / bin16 / bin32 | |
| IntX, UintX | 1-8 bytes | fixint / intX / uintX | |
| Float | 4 bytes | float32 | |
| Double | 8 bytes | float64 | |
| Number([n]) | Variable | ext16 | Extension 1 |
| Decimal | Variable | ext16 | Extension 2 |
| UUID | 16 bytes | fixext16 | Extension 3 |
| String | Variable | str | |
| Date | 3 bytes | ||
| Time | 4 bytes | ||
| Datetime | 7 bytes | ||
| Timestamp | 8 bytes | ||
| Binary | Variable |
| Name | Format | |
|---|---|---|
| UUID | ||
| Decimal | ||
| TODO: Dates |
Handshake
TODO: Magic word, features as map 
Risks and Assumptions
TODO
Discussion Links
- TODO
Reference Links
- IEP-75 Thin Client MsgPack Serialization
- IEP-9 Thin Client Protocol (Ignite 2.x protocol)
Tickets
Overview
Content Tools
Apps
