[
https://issues.apache.org/jira/browse/IGNITE-24478?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Aleksandr Polovtsev updated IGNITE-24478:
-----------------------------------------
Description:
In the colocation track, a zone-wide Raft listener handles two types of
commands:
# Zone-wide commands, applicable to the whole zone partition;
# Table-wide commands, applicable to a partition of a single table.
The second type of commands are actually dispatched onto "Raft listeners",
which are reused listeners from the original table-wide Raft groups. But these
listeners no longer have any relation to a Raft STM, they are used simply for
code simplicity. It is proposed to hide such listeners behind a special
interface, so that later we can get rid of table-wide listeners and end up with
a class that only contains logic of working with a particular table storage.
> Introduce TableProcessor interface for Raft commands
> ----------------------------------------------------
>
> Key: IGNITE-24478
> URL: https://issues.apache.org/jira/browse/IGNITE-24478
> Project: Ignite
> Issue Type: Task
> Reporter: Aleksandr Polovtsev
> Assignee: Aleksandr Polovtsev
> Priority: Major
> Labels: ignite-3
> Time Spent: 10m
> Remaining Estimate: 0h
>
> In the colocation track, a zone-wide Raft listener handles two types of
> commands:
> # Zone-wide commands, applicable to the whole zone partition;
> # Table-wide commands, applicable to a partition of a single table.
> The second type of commands are actually dispatched onto "Raft listeners",
> which are reused listeners from the original table-wide Raft groups. But
> these listeners no longer have any relation to a Raft STM, they are used
> simply for code simplicity. It is proposed to hide such listeners behind a
> special interface, so that later we can get rid of table-wide listeners and
> end up with a class that only contains logic of working with a particular
> table storage.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
