[
https://issues.apache.org/jira/browse/IGNITE-11309?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16815194#comment-16815194
]
Alexander Lapin commented on IGNITE-11309:
------------------------------------------
[~vozerov]
{{bestEffortAffinityEnabled}} renamed to affinityAwareness. Below there's tiny
research about how other vendors call similar stuff:
* Oracle: "Database Sharding for JDBC"
[https://docs.oracle.com/en/database/oracle/oracle-database/12.2/jjdbc/database-sharding.html#GUID-1D7795CA-79DC-452B-9FCC-0EF430F87461]
* Cassandra: "load balancing"
[https://docs.datastax.com/en/developer/java-driver/3.6/manual/load_balancing]
* Mongo: "server selection"
[https://www.mongodb.com/blog/post/server-selection-next-generation-mongodb-drivers?jmp=docs]
* Hazelcast: "smart routing"
[https://docs.hazelcast.org/docs/3.3-RC3/manual/html/javaclient.html]
tests added;
> 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)
