Alexander Lapin created IGNITE-11661:
----------------------------------------
Summary: Jdbc Thin: Implement tests for best effort affinity
Key: IGNITE-11661
URL:
https://issues.apache.org/jira/browse/IGNITE-11661 Project: Ignite
Issue Type: Task
Components: jdbc
Reporter: Alexander Lapin
Test plan draft.
# Сheck that requests go to the expected number of nodes for different combinations of conditions
** Transactional
*** Without 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.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
Locked
