[
https://issues.apache.org/jira/browse/IGNITE-6456?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16322245#comment-16322245
]
Pavel Tupitsyn commented on IGNITE-6456:
----------------------------------------
[~rkondakov]
* Can we avoid using exceptions for control flow? I mean, we throw exception
and catch it right there.
* Unsupported version error looks dirty now: {{Client handshake failed:
'Unsupported version: ClientListenerProtocolVersion [major=-1, minor=-1,
maintenance=-1]'. Client version: -1.-1.-1. Server version: 1.0.0}}, it was
{{Client handshake failed: 'Unsupported version.'. Client version: -1.-1.-1.
Server version: 1.0.0}}.
> Add flags to ClientConnectorConfiguration which enable/disable different
> clients
> --------------------------------------------------------------------------------
>
> Key: IGNITE-6456
> URL: https://issues.apache.org/jira/browse/IGNITE-6456
> Project: Ignite
> Issue Type: Improvement
> Components: jdbc, odbc, thin client
> Affects Versions: 2.1
> Reporter: Igor Sapego
> Assignee: Roman Kondakov
> Labels: usability
> Fix For: 2.4
>
>
> There is currently no way to disable only one client. For example, currently
> you can't disallow thin JDBC driver connectivity alone, you can only disable
> the whole {{ClientListenerProcessor}}, which is going to disable ODBC and
> thin .NET clients as well.
> We should add options to disable/enable every single client, supported by the
> {{ClientListenerProcessor}} separately. For example, we can add flags to the
> {{ClientConnectorConfiguration}}:
> {{allowJdbc}}
> {{allowOdbc}}
> {{allowClient}}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
