[ 
https://issues.apache.org/jira/browse/IGNITE-26150?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Pavel Pereslegin updated IGNITE-26150:
--------------------------------------
    Description: 
We need to update the JDBC driver documentation:

* describe that the driver can connect to multiple cluster nodes (not just one 
as currently stated).
* describe connection properties

It is also worth noting the compatibility limitation that the new JDBC driver 
implementation is not compatible with old cluster nodes (which have a version 
lower than the driver version with multiple endpoints support).


  was:
We need to update the JDBC driver documentation:

* describe that the driver can connect to multiple cluster nodes (not just one 
as currently stated).
* describe recommended setups for multinode connection (including setup for 
kubernetes headless service (DNS names with multiple A records))

It is also worth noting the compatibility limitation that the new JDBC driver 
implementation is not compatible with old cluster nodes (which have a version 
lower than the driver version with multiple endpoints support).



> Sql. Jdbc. Improve driver documentation
> ---------------------------------------
>
>                 Key: IGNITE-26150
>                 URL: https://issues.apache.org/jira/browse/IGNITE-26150
>             Project: Ignite
>          Issue Type: Improvement
>          Components: jdbc ai3, sql ai3
>            Reporter: Pavel Pereslegin
>            Priority: Major
>              Labels: ignite-3
>
> We need to update the JDBC driver documentation:
> * describe that the driver can connect to multiple cluster nodes (not just 
> one as currently stated).
> * describe connection properties
> It is also worth noting the compatibility limitation that the new JDBC driver 
> implementation is not compatible with old cluster nodes (which have a version 
> lower than the driver version with multiple endpoints support).



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Reply via email to