ignite-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Igor Sapego <isap...@apache.org>
Subject Re: Disabling ODBC/thin JDBC/thin .NET connectivity
Date Wed, 20 Sep 2017 12:26:23 GMT
I've filed a ticket for that: [1]

[1] - https://issues.apache.org/jira/browse/IGNITE-6456

Best Regards,
Igor

On Wed, Sep 20, 2017 at 2:33 PM, Vladimir Ozerov <vozerov@gridgain.com>
wrote:

> Agree. Do we have a ticket for this?
>
> On Wed, Sep 20, 2017 at 1:27 PM, Pavel Tupitsyn <ptupitsyn@apache.org>
> wrote:
>
> > Yes, I think it would make sense to add enableJdbc, enableOdbc,
> > enableThinClients
> > properties to ClientConnectorConfiguration (which replaces
> > SqlConnectorConfiguration).
> >
> > This way users will also have better understanding of the
> > ClientConnectorConfiguration purpose.
> >
> > Pavel
> >
> > On Wed, Sep 20, 2017 at 1:12 PM, Igor Sapego <isapego@apache.org> wrote:
> >
> > > Hi, Igniters,
> > >
> > > In current approach, ODBC, thin JDBC and thin .NET client all connect
> > > to the grid using ClientListenerProcessor, which listen on a single
> port.
> > >
> > > The problem is that 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.
> > >
> > > I believe, we should add options to disable/enable every single client,
> > > supported by the ClientListenerProcessor separately. Maybe we should
> > > add such options to the SqlConnectorConfiguration.
> > >
> > > What do you guys think?
> > >
> > > Best Regards,
> > > Igor
> > >
> >
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message