You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Sergey Uttsel (Jira)" <ji...@apache.org> on 2022/08/19 13:49:00 UTC
[jira] [Commented] (IGNITE-17477) Redesign RAFT commands in accordance with replication layer
[ https://issues.apache.org/jira/browse/IGNITE-17477?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17581863#comment-17581863 ]
Sergey Uttsel commented on IGNITE-17477:
----------------------------------------
LGTM
> 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)