[jira] [Updated] (IGNITE-16925) Thin 3.0: Add partition awareness to executeColocated
[ https://issues.apache.org/jira/browse/IGNITE-16925?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vyacheslav Koptilin updated IGNITE-16925: - Fix Version/s: 3.0.0-beta2 (was: 3.0.0-beta1) > Thin 3.0: Add partition awareness to executeColocated > - > > Key: IGNITE-16925 > URL: https://issues.apache.org/jira/browse/IGNITE-16925 > Project: Ignite > Issue Type: Improvement > Components: clients >Reporter: Pavel Tupitsyn >Assignee: Pavel Tupitsyn >Priority: Major > Labels: ignite-3 > Fix For: 3.0.0-beta2 > > > 1. Compute key hash on the client > 2. Retrieve and maintain up-to-date partitionMap > 2. Send the request directly to the target node if a connection exists -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-16925) Thin 3.0: Add partition awareness to executeColocated
[ https://issues.apache.org/jira/browse/IGNITE-16925?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Igor Sapego updated IGNITE-16925: - Fix Version/s: 3.0.0-alpha6 (was: 3.0.0-alpha5) > Thin 3.0: Add partition awareness to executeColocated > - > > Key: IGNITE-16925 > URL: https://issues.apache.org/jira/browse/IGNITE-16925 > Project: Ignite > Issue Type: Improvement > Components: clients >Reporter: Pavel Tupitsyn >Assignee: Pavel Tupitsyn >Priority: Major > Labels: ignite-3 > Fix For: 3.0.0-alpha6 > > > 1. Compute key hash on the client > 2. Retrieve and maintain up-to-date partitionMap > 2. Send the request directly to the target node if a connection exists -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Updated] (IGNITE-16925) Thin 3.0: Add partition awareness to executeColocated
[ https://issues.apache.org/jira/browse/IGNITE-16925?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pavel Tupitsyn updated IGNITE-16925: Description: 1. Compute key hash on the client 2. Retrieve and maintain up-to-date partitionMap 2. Send the request directly to the target node if a connection exists was: Currently, key hash is calculated on the server side by serializing key columns into a BinaryRow. A portable key hash computation algorithm that can be implemented on the client side is yet to be defined. > Thin 3.0: Add partition awareness to executeColocated > - > > Key: IGNITE-16925 > URL: https://issues.apache.org/jira/browse/IGNITE-16925 > Project: Ignite > Issue Type: Improvement > Components: clients >Reporter: Pavel Tupitsyn >Assignee: Pavel Tupitsyn >Priority: Major > Labels: ignite-3 > Fix For: 3.0.0-alpha5 > > > 1. Compute key hash on the client > 2. Retrieve and maintain up-to-date partitionMap > 2. Send the request directly to the target node if a connection exists -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Updated] (IGNITE-16925) Thin 3.0: Add partition awareness to executeColocated
[ https://issues.apache.org/jira/browse/IGNITE-16925?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pavel Tupitsyn updated IGNITE-16925: Summary: Thin 3.0: Add partition awareness to executeColocated (was: Thin 3.0: Support key hash calculation for all data types) > Thin 3.0: Add partition awareness to executeColocated > - > > Key: IGNITE-16925 > URL: https://issues.apache.org/jira/browse/IGNITE-16925 > Project: Ignite > Issue Type: Improvement > Components: clients >Reporter: Pavel Tupitsyn >Assignee: Pavel Tupitsyn >Priority: Major > Labels: ignite-3 > Fix For: 3.0.0-alpha5 > > > Currently, key hash is calculated on the server side by serializing key > columns into a BinaryRow. > A portable key hash computation algorithm that can be implemented on the > client side is yet to be defined. -- This message was sent by Atlassian Jira (v8.20.7#820007)
