[ https://issues.apache.org/jira/browse/IGNITE-19827?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17739468#comment-17739468 ]
Igor Sapego commented on IGNITE-19827: -------------------------------------- Looks good to me. > Java thin 3.0: Partition awareness uses wrong node id > ----------------------------------------------------- > > Key: IGNITE-19827 > URL: https://issues.apache.org/jira/browse/IGNITE-19827 > Project: Ignite > Issue Type: Bug > Components: thin client > Affects Versions: 3.0.0-beta1 > Reporter: Pavel Tupitsyn > Assignee: Pavel Tupitsyn > Priority: Blocker > Labels: ignite-3 > Fix For: 3.0.0-beta2 > > Time Spent: 10m > Remaining Estimate: 0h > > There is a confusion between *Local Node ID* (which we get from > protocolContext().clusterNode().id()) and *Consistent Node ID* (which is the > same as Node Name, comes from protocolContext().clusterNode().name()). > Partition assignment (returned by ClientTablePartitionAssignmentGetRequest on > the server) is based on *Consistent Node ID*. > All partition awareness tests use FakeServer, so we never tested that it > actually works. -- This message was sent by Atlassian Jira (v8.20.10#820010)