[jira] [Commented] (IGNITE-6456) Add flags to ClientConnectorConfiguration which enable/disable different clients

["Pavel Tupitsyn (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/IGNITE-6456?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16318076#comment-16318076 ] 

Pavel Tupitsyn commented on IGNITE-6456:
----------------------------------------

I've added new config properties to .NET, tests should be green now.

May be we should include configuration property name in the exception text so that user knows where to look?
Like {{Thin client connection is disabled, see ClientConnectorConfiguration.thinClientEnabled.}}.

> 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)