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/28 09:08:00 UTC
[jira] [Commented] (IGNITE-11287) JDBC Thin: best effort affinity
[ https://issues.apache.org/jira/browse/IGNITE-11287?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16803720#comment-16803720 ]
Alexander Lapin commented on IGNITE-11287:
------------------------------------------
Test plan draft.
# Сheck that requests go to the expected number of nodes for different combinations of conditions
## Transactional
### No Params
#### Select
##### Different partition tree options(All/NONE/Group/CONST) produced by different query types.
#### DML
##### - // -
### With Params
#### - // -
## Non-Transactional
### - // -
# Check that request/response functionality works fine if server response lacks partition result.
# Check that partition result is supplied only in case of rendezvous affinity function without custom filters.
# Check that best effort functionality works fine for different partitions count.
# Сheck that a change in topology leads to jdbc thin affinity cache invalidation.
## Topology changed during partition result retrieval.
## Topology changed during cache distribution retrieval.
## Topology changed during best-effort-affinity-unrelated query.
# Check that jdbc thin best effort affinity works fine if cache is full and new data still coming. For given case we probably should decrease cache boundaries.
# Check that proper connection is used if set of nodes we are connected to and set of nodes derived from partitions
## Fully intersect;
## Partially intersect;
##
Doesn't intersect, i.e.
||User Specified||Derived from partitons||
|host:port1 - > UUID1
host:port2 -> UUID2|partition1 -> UUID3|
No intersection, so random connection should be used.
# Check client reconnection after failure.
# Check that jdbc thin best effort affinity skipped if it is switched off.
> JDBC Thin: best effort affinity
> -------------------------------
>
> Key: IGNITE-11287
> URL: https://issues.apache.org/jira/browse/IGNITE-11287
> Project: Ignite
> Issue Type: New Feature
> Components: jdbc
> Reporter: Alexander Lapin
> Priority: Major
> Labels: iep-23
> Fix For: 2.8
>
>
> It's an umbrella ticket for implementing [IEP-23|https://cwiki.apache.org/confluence/display/IGNITE/IEP-23%3A+Best+Effort+Affinity+for+thin+clients] within the scope of JDBC Thin driver.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)