[
https://issues.apache.org/jira/browse/IGNITE-2663?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15204004#comment-15204004
]
Igor Sapego commented on IGNITE-2663:
-------------------------------------
Vladimir,
I was thinking about the several versions support issue as well and my thoughts
about this issue are pretty much the same. Thats why I have not included
expected version in the response message.
If we want to have more informational user error message we can make something
like that:
- Server (node) stores all the supported version of the protocol and associated
list of the Apache Ignite versions.
- Client stores only it's own protocol version and Apache Ignite version.
- Resulting error message looks like this: "Can not perform connection:
unsupported protocol version. Supported versions: [1, 2, ...], corresponding
Apache Ignite versions: [1.6, ...], driver uses protocol version X and is part
of Apache Ignite X.X".
> 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)
