[
https://issues.apache.org/jira/browse/IGNITE-24388?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vyacheslav Koptilin updated IGNITE-24388:
-----------------------------------------
Description:
Need to adopt the processing of the `BuildIndexReplicaRequest` to be aware of
the colocation track.
There are two possible options:
- move the processing to the `ZonePartitionReplicaListener`. This approach
requires moving `indexMetaStorage` and `txRwOperationTracker` to the zone
listener.
Note that in this case, `txRwOperationTracker` might be shared between
`PartitionReplicaListener` and `ZonePartitionReplicaListener`.
- the processing should stay in the `PartitionReplicaListener` and so the
`BuildIndexReplicaRequest` should extend the `TableAware` interface.
Therefore, it is worth trying the first approach unless some significant
obstacle is encountered.
was:
Need to adopt the processing of the `BuildIndexReplicaRequest` to be aware of
the colocation track.
There are two possible options:
- move the processing to the `ZonePartitionReplicaListener`. This approach
requires moving `indexMetaStorage` and `txRwOperationTracker` to the zone
listener.
Note that in this case, `txRwOperationTracker` might be shared between
`PartitionReplicaListener` and `ZonePartitionReplicaListener`.
- the processing should stay in the `PartitionReplicaListener` and so the
`BuildIndexReplicaRequest` should extend the `TableAware` interface.
The first option seems simpler and more straightforward.
> Adjust BuildIndexReplicaRequest to be TableAware one
> ----------------------------------------------------
>
> Key: IGNITE-24388
> URL: https://issues.apache.org/jira/browse/IGNITE-24388
> Project: Ignite
> Issue Type: Improvement
> Reporter: Alexander Lapin
> Assignee: Vyacheslav Koptilin
> Priority: Major
> Labels: ignite-3
>
> Need to adopt the processing of the `BuildIndexReplicaRequest` to be aware of
> the colocation track.
> There are two possible options:
> - move the processing to the `ZonePartitionReplicaListener`. This approach
> requires moving `indexMetaStorage` and `txRwOperationTracker` to the zone
> listener.
> Note that in this case, `txRwOperationTracker` might be shared between
> `PartitionReplicaListener` and `ZonePartitionReplicaListener`.
> - the processing should stay in the `PartitionReplicaListener` and so the
> `BuildIndexReplicaRequest` should extend the `TableAware` interface.
>
> Therefore, it is worth trying the first approach unless some significant
> obstacle is encountered.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
