[
https://issues.apache.org/jira/browse/IGNITE-17394?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Igor Sapego updated IGNITE-17394:
---------------------------------
Description:
To implement Partition Awareness feature for clients, we need an internal or
public API that will provide us with the following mapping: [partition => node
id] (or [node id => partitions]).
We also need a lightweight mechanism that will allow us to discover that this
distribution has changed. In 2.x we used a topology version for this purpose,
assuming that if topology version has changed, partition distribution should be
refreshed.
was:
To implement Partition Awareness feature for clients, we need an internal or
public API that will provide us with the following mapping: [partition => node]
(or [node => partitions]).
We also need a lightweight mechanism that will allow us to discover that this
distribution has changed. In 2.x we used a topology version for this purpose,
assuming that if topology version has changed, partition distribution should be
refreshed.
> Implement API for getting partition mapping
> -------------------------------------------
>
> Key: IGNITE-17394
> URL: https://issues.apache.org/jira/browse/IGNITE-17394
> Project: Ignite
> Issue Type: New Feature
> Affects Versions: 3.0.0-alpha5
> Reporter: Igor Sapego
> Assignee: Mirza Aliev
> Priority: Major
> Labels: ignite-3
> Fix For: 3.0.0-alpha6
>
>
> To implement Partition Awareness feature for clients, we need an internal or
> public API that will provide us with the following mapping: [partition =>
> node id] (or [node id => partitions]).
> We also need a lightweight mechanism that will allow us to discover that this
> distribution has changed. In 2.x we used a topology version for this purpose,
> assuming that if topology version has changed, partition distribution should
> be refreshed.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
