You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@ignite.apache.org by "Ignite TC Bot (JIRA)" <ji...@apache.org> on 2019/04/08 03:13:00 UTC

[jira] [Commented] (IGNITE-11309) JDBC Thin: add flag or property to disable best effort affinity

    [ https://issues.apache.org/jira/browse/IGNITE-11309?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16812061#comment-16812061 ] 

Ignite TC Bot commented on IGNITE-11309:
----------------------------------------

{panel:title=--&gt; Run :: All: No blockers found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
[TeamCity *--&gt; Run :: All* Results|https://ci.ignite.apache.org/viewLog.html?buildId=3514961&amp;buildTypeId=IgniteTests24Java8_RunAll]

> JDBC Thin: add flag or property to disable best effort affinity
> ---------------------------------------------------------------
>
>                 Key: IGNITE-11309
>                 URL: https://issues.apache.org/jira/browse/IGNITE-11309
>             Project: Ignite
>          Issue Type: Task
>          Components: jdbc
>    Affects Versions: 2.8
>            Reporter: Alexander Lapin
>            Assignee: Alexander Lapin
>            Priority: Major
>              Labels: iep-23
>          Time Spent: 10m
>  Remaining Estimate: 0h
>
> It's necessary to have an ability to disable best effort affinity among thin clients including thin jdbc client.
> It's not obvious whether it should be flag in connection string, app properties or some other place, so research required.



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