...
- Hard to improve, fix any aspect of serdes process. As an example of complexity to add any new BinaryType one can look into BinaryArray implementation
- Can't deliver thin client as tiny jar. Thin client included in
ignite-code
module, because, binary infrastracture inside of core. - Can't be replaced with other implementation, e.g. JSONB
To unlock further improvements of Ignite in this aspects and possibly provide a way to plugin different implementation of Binary serdes (msgpack, jsonb as an exampleexamples) we must to refactor Ignite and extract all Binary related classes to separate module
...
IEP concentrated on code structure only and must not break any public benavior or API.
- Does this proposal affect the user in any way?
- Does it introduce or remove features?
- Does it affect compatibility?
Discussion Links
Tickets
Jira |
---|
server | ASF JIRA |
---|
columnIds | issuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution |
---|
columns | key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution |
---|
maximumIssues | 20 |
---|
jqlQuery | labels = IEP-115 |
---|
serverId | 5aa69414-a9e9-3523-82ec-879b028fb15b |
---|
|