[
https://issues.apache.org/jira/browse/IGNITE-17394?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17577938#comment-17577938
]
Alexander Lapin commented on IGNITE-17394:
------------------------------------------
[~isapego]
>Will I get an exception in this case? Why?
It depends on the API you are going to use.
Generally speaking, as far as I remember, partition pruning logic assumes that
there's some extra data transferred between client and server in order to mark
request as partition aware. So that if partition aware request missed target
primary replicas because they were changed it will succeed in processing the
request itself (extra rerouting included) and return new distribution besides
common result.
However if you will use ReplicaService interface directly with expected replica
as target cluster node you will actually get PrimaryReplicaMissException.
> 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)
