[jira] [Updated] (IGNITE-6456) Add flags to ClientConnectorConfiguration which enable/disable different clients
[
https://issues.apache.org/jira/browse/IGNITE-6456?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vladimir Ozerov updated IGNITE-6456:
Description:
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}}
was:
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
{{SqlConnectorConfiguration}}:
{{allowJdbc}}
{{allowOdbc}}
{{allowClient}}
> 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
> 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)
[jira] [Updated] (IGNITE-6456) Add flags to ClientConnectorConfiguration which enable/disable different clients
[
https://issues.apache.org/jira/browse/IGNITE-6456?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vladimir Ozerov updated IGNITE-6456:
Description:
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
{{SqlConnectorConfiguration}}:
{{allowJdbc}}
{{allowOdbc}}
{{allowClient}}
was:
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
{{SqlConnectorConfiguration}}:
{{enableJdbc}}
{{enableOdbc}}
{{enableThinClients}}
> 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
> 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
> {{SqlConnectorConfiguration}}:
> {{allowJdbc}}
> {{allowOdbc}}
> {{allowClient}}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (IGNITE-6456) Add flags to ClientConnectorConfiguration which enable/disable different clients
[
https://issues.apache.org/jira/browse/IGNITE-6456?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vladimir Ozerov updated IGNITE-6456:
Fix Version/s: (was: 2.3)
2.4
> 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
> 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
> {{SqlConnectorConfiguration}}:
> {{enableJdbc}}
> {{enableOdbc}}
> {{enableThinClients}}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (IGNITE-6456) Add flags to ClientConnectorConfiguration which enable/disable different clients
[
https://issues.apache.org/jira/browse/IGNITE-6456?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vladimir Ozerov updated IGNITE-6456:
Labels: usability (was: )
> 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
> Labels: usability
> Fix For: 2.3
>
>
> 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
> {{SqlConnectorConfiguration}}:
> {{enableJdbc}}
> {{enableOdbc}}
> {{enableThinClients}}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
