[
https://issues.apache.org/jira/browse/IGNITE-21858?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mirza Aliev resolved IGNITE-21858.
----------------------------------
Fix Version/s: 3.0.0-beta2
Resolution: Done
> Analyse moving 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: Task
> Reporter: Mirza Aliev
> Assignee: Mirza Aliev
> Priority: Major
> Labels: ignite-3
> Fix For: 3.0.0-beta2
>
> Attachments: Untitled spreadsheet.xlsx
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> h3. Motivation
> 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, because the accepted {{ReplicationGroupId}} which is
> {{TablePartitionId}}.
> We need to analyse all places where {{PlacementDriver}} API is used and where
> {{TablePartitionId}} is passed.
> h3. Definition of done
> As outcome, we need to create several tickets where corresponding places in
> the code base where PlacementDriver API was used using TablePartitionId will
> be changed to ZonePartitionId
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
