[
https://issues.apache.org/jira/browse/IGNITE-17477?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17581917#comment-17581917
]
Vladislav Pyatkov edited comment on IGNITE-17477 at 8/19/22 3:22 PM:
---------------------------------------------------------------------
Merged in the TX branch:
[ignite3_tx|https://github.com/gridgain/apache-ignite-3/commits/ignite3_tx]
b875396e6beda6b85cbb67bf77399663087b49c4
was (Author: v.pyatkov):
Merged in the TX branch: b875396e6beda6b85cbb67bf77399663087b49c4
> Redesign RAFT commands in accordance with replication layer
> -----------------------------------------------------------
>
> Key: IGNITE-17477
> URL: https://issues.apache.org/jira/browse/IGNITE-17477
> Project: Ignite
> Issue Type: Improvement
> Reporter: Vladislav Pyatkov
> Assignee: Vladislav Pyatkov
> Priority: Major
> Labels: ignite-3, transaction3_rw
>
> After we have implemented a replication layer, a part of the RAFT command are
> become useless: _GetAndDeleteCommand, UpsertCommand, GetAllCommand,
> GetCommand, DeleteExactCommand_ (the list can be changed) and another one
> required modification, because all raft command should apply _rowId_ and
> never try to match some row to its id (it is already done by replication
> layer).
> Also required to extract a primary index (for now, it is a map) from the RAFT
> state machine. It will be used by replication layer for read, but in the
> state machine will use it for modification only.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
