[ https://issues.apache.org/jira/browse/IGNITE-6456?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16323627#comment-16323627 ]
Roman Kondakov commented on IGNITE-6456: ---------------------------------------- [~ptupitsyn], * Exceptions look appropriate solution for this case due to multiple possible causes of failure - wrong client, disabled client or unsupported version. And exception here is a quite convenient way to stop execution and transfer an error message back to the client. * I've fixed error message. [~vozerov], [~ptupitsyn], please review. [TC run|https://ci.ignite.apache.org/viewLog.html?buildId=1034773&] is not OK, but failures are caused by problems in the master branch. JDBC tests are ok. > 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)