[
https://issues.apache.org/jira/browse/IGNITE-10308?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16806501#comment-16806501
]
Ignite TC Bot commented on IGNITE-10308:
----------------------------------------
{panel:title=--> Run :: All: No blockers
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
[TeamCity *--> Run :: All*
Results|https://ci.ignite.apache.org/viewLog.html?buildId=3454994&buildTypeId=IgniteTests24Java8_RunAll]
> 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)
