...

For Ignite 3.x the concept is formulated for the distributed table. The table is the base object which allow component that allows a store and update updates data in the cluster. The table provides a base guaranty would it provide it is a of consistency of data entry writewrites/readreads.

Motivation

All distributed table structures required require to have redundant redundancy of storing data to avoid loosing losing entries when one of the member (or more) member(s) of the structure got goes down. More over Moreover, the data which is available should be consistent every time, while a part of the data available in the structure.

The atomic protocol should provide an ability to store redundant keep data redundancy level and keep data consistency until all copes the copies of the data lose the clusterare lost.

Interface

Table creation

For create any table you need to specify two parameters Table creation requires next parameters to be specified for the protocol purpose:

• Partitions Amount of partitions - this is the total number of part of parts the data will divided be distributed among in the cluster.Replicas - this is the number of copy of each partition would be created (1 means the cluster would have only
• copy without redundancyA number of replicas - a redundancy level, desired number of copies each partition should have (1 means no redundancy - a single copy of partition will be in a cluster).

Key value interface

The familiar interface for atomic storage in a table is available through the Key-Value view[1] of a table:

...

All batch methods won't have atomically guaranties guarantees and added for optimization on network communication.

It is an analogue of Ignite cache interface form from Ignite 2.x.

Implementation

...

Tickets