[
https://issues.apache.org/jira/browse/IGNITE-2663?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15204118#comment-15204118
]
Igor Sapego commented on IGNITE-2663:
-------------------------------------
On second thought it's not that good idea to list all the supported Apache
Ignite versions because we may not have all information on which protocol
version used by which Apache Ignite version. For example lets imagine that
Apache Ignite versions 1.5, 1.6, 1.7 are all using the same protocol version.
But if the client with unknown version will try to connect to Apache Ignite 1.6
it would get only 1.5 and 1.6 in a list of supported versions, while 1.7 is
also supported.
So instead I propose to respond with the following message: "Can not perform
connection: unsupported protocol version. The last known protocol version
supported by host released with Apache Ignite 1.6. Driver uses protocol version
released with Apache Ignite 1.8"
> ODBC: Add protocol version to protocol packet header.
> -----------------------------------------------------
>
> Key: IGNITE-2663
> URL: https://issues.apache.org/jira/browse/IGNITE-2663
> Project: Ignite
> Issue Type: Sub-task
> Components: odbc
> Affects Versions: 1.5.0.final
> Reporter: Igor Sapego
> Assignee: Igor Sapego
> Fix For: 1.6
>
>
> Currently, there is no way for server to find out that ODBC driver uses
> incompatible protocol version. Consider adding {{protocolVersion}} field to
> ODBC protocol message header.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
