You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Alexander Lapin (JIRA)" <ji...@apache.org> on 2019/03/19 12:14:00 UTC

[jira] [Updated] (IGNITE-10308) Jdbc Thin: implement client side best effort affinity

     [ https://issues.apache.org/jira/browse/IGNITE-10308?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Alexander Lapin updated IGNITE-10308:
-------------------------------------
    Summary: Jdbc Thin: implement client side best effort affinity  (was: SQL: Pass partition pruning models to JDBC thin driver)

> Jdbc Thin: implement client side best effort affinity
> -----------------------------------------------------
>
>                 Key: IGNITE-10308
>                 URL: https://issues.apache.org/jira/browse/IGNITE-10308
>             Project: Ignite
>          Issue Type: Task
>          Components: jdbc, sql
>            Reporter: Vladimir Ozerov
>            Assignee: Alexander Lapin
>            Priority: Major
>              Labels: iep-24
>             Fix For: 2.8
>
>
> Once partitions are extracted from original query (IGNITE-10305), it might be useful for thin clients: they could apply arguments locally and try to guess the best node where to send the request. 
> Example: when there is only one partition, then it makes sense to send the request directly to that node, so that only one hop is needed.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)