[
https://issues.apache.org/jira/browse/IGNITE-26148?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pavel Pereslegin updated IGNITE-26148:
--------------------------------------
Description:
To ensure multi-node connection works fine:
* We need to modify the existing JDBC test configuration so that it uses a
multi-node cluster and the driver connects to all nodes (see
AbstractJdbcSelfTest).
* Introduce test with JDBC connection pool
* Introduce tests to check partition awareness
* Figure out how to check various connection options introduced in IGNITE-26005
(at least they should be allowed by the driver).
was:
To ensure multi-node connection works fine:
* We need to modify the existing JDBC test configuration so that it uses a
multi-node cluster and the driver connects to all nodes (see
AbstractJdbcSelfTest).
* Introduce test with JDBC connection pool
* Figure out how to check various connection options introduced in IGNITE-26005
(at least they should be allowed by the driver).
> Sql. Jdbc. Multinode connection tests
> -------------------------------------
>
> Key: IGNITE-26148
> URL: https://issues.apache.org/jira/browse/IGNITE-26148
> Project: Ignite
> Issue Type: New Feature
> Components: jdbc ai3, sql ai3
> Reporter: Pavel Pereslegin
> Priority: Major
> Labels: ignite-3
>
> To ensure multi-node connection works fine:
> * We need to modify the existing JDBC test configuration so that it uses a
> multi-node cluster and the driver connects to all nodes (see
> AbstractJdbcSelfTest).
> * Introduce test with JDBC connection pool
> * Introduce tests to check partition awareness
> * Figure out how to check various connection options introduced in
> IGNITE-26005 (at least they should be allowed by the driver).
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
