[
https://issues.apache.org/jira/browse/IGNITE-21858?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mirza Aliev updated IGNITE-21858:
---------------------------------
Description:
In https://issues.apache.org/jira/browse/IGNITE-18991 we moved
stable/pending/planned keys handling to zone, and now they work with
{{ZonePartitionId}}, but all these changes lead to changes in PlacementDriver
api changes, because the accepted {{ReplicationGroupId}} which is
{{TablePartitionId}}.
We need to change all places where {{PlacementDriver}} API is used and where
{{TablePartitionId}} is passed
was:In https://issues.apache.org/jira/browse/IGNITE-18991 we moved
stable/pending/planned keys handling to zone, and now they work with
{{ZonePartitionId}}, but all these changes lead to changes in PlacementDriver
api changes, because the accepted {{ReplicationGroupId}} which is
> Move from TablePartitionId to ZonePartitionId for all PlacementDriver API
> usages
> --------------------------------------------------------------------------------
>
> Key: IGNITE-21858
> URL: https://issues.apache.org/jira/browse/IGNITE-21858
> Project: Ignite
> Issue Type: Improvement
> Reporter: Mirza Aliev
> Assignee: Mirza Aliev
> Priority: Major
> Labels: ignite-3
>
> In https://issues.apache.org/jira/browse/IGNITE-18991 we moved
> stable/pending/planned keys handling to zone, and now they work with
> {{ZonePartitionId}}, but all these changes lead to changes in PlacementDriver
> api changes, because the accepted {{ReplicationGroupId}} which is
> {{TablePartitionId}}.
> We need to change all places where {{PlacementDriver}} API is used and where
> {{TablePartitionId}} is passed
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
