[
https://issues.apache.org/jira/browse/IGNITE-10308?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16806505#comment-16806505
]
Alexander Lapin edited comment on IGNITE-10308 at 4/1/19 8:10 AM:
------------------------------------------------------------------
[~vozerov] Ready for one more iteration of review. Please compare with
ignite-11287.
was (Author: alapin):
Ready for one more iteration of review. Please compare with ignite-11287.
> 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
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> 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)
