ignite-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Pavel Tupitsyn (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (IGNITE-6456) Add flags to ClientConnectorConfiguration which enable/disable different clients
Date Fri, 12 Jan 2018 08:26:00 GMT

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

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

Looks good to me.

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

Mime
View raw message