ignite-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Andrey Gura <ag...@gridgain.com>
Subject Re: What is jdbc:ignite:cfg ??
Date Wed, 09 Dec 2015 16:54:54 GMT
Configuration sample added.

On Tue, Dec 8, 2015 at 10:20 PM, Dmitriy Setrakyan <dsetrakyan@apache.org>
wrote:

> Thanks Andrey!
>
> In my view, we should also provide a sample XML configuration file,
> especially given that we refer to it in the sample URL.
>
> D.
>
> On Tue, Dec 8, 2015 at 10:17 AM, Andrey Gura <agura@gridgain.com> wrote:
>
> > Done. I hope that is more clear now.
> >
> > On Tue, Dec 8, 2015 at 1:14 AM, Dmitriy Setrakyan <dsetrakyan@apache.org
> >
> > wrote:
> >
> > > On Mon, Dec 7, 2015 at 10:17 AM, Andrey Gura <agura@gridgain.com>
> wrote:
> > >
> > > > Cos,
> > > >
> > > > <config_url> sepcifies configuration file for Ignite client node
that
> > > will
> > > > be started during connection establishing by JDBC driver. So this
> file
> > > > should be available for JDBC driver client.
> > > >
> > >
> > > Andrey, should this be documented here?
> > > https://apacheignite.readme.io/docs/jdbc-driver
> > >
> > > D.
> > >
> > >
> > > >
> > > > On Mon, Dec 7, 2015 at 8:59 PM, Konstantin Boudnik <cos@apache.org>
> > > wrote:
> > > >
> > > > > Thanks Andrey!
> > > > >
> > > > > Still a bit unclear: the doc says
> > > > > "<config_url> is required and represents any valid URL which
points
> > to
> > > > > Ignite configuration file"
> > > > >
> > > > > So, that's server side URL then, something like
> > > > >     jdbc:ignite:cfg:///etc/ignite/conf/default-config.xml
> > > > >
> > > > > assuming that server nodes have said configuration under
> > > > > /etc/ignite/conf/default-config.xml ? Sorry, it's either I am a bit
> > > > dense,
> > > > > or
> > > > > the doc isn't written to a layman
> > > > >
> > > > > Thanks in advance!
> > > > >   Cos
> > > > >
> > > > > On Mon, Dec 07, 2015 at 01:03PM, Andrey Gura wrote:
> > > > > > Cos,
> > > > > >
> > > > > > JDBC driver was reworked in order to use Ignite client node
> instead
> > > of
> > > > > > Ignite Java client. It gives better performance. So now JDBC
> dirver
> > > > uses
> > > > > > Ignite xml configuration file using jdbc:ignite:cfg protocol.
See
> > > > > > documentation for version 1.4
> > > > > > https://apacheignite.readme.io/v1.4/docs/jdbc-driver
> > > > > >
> > > > > > At the same time we still support old version of JDBC driver
that
> > > uses
> > > > > > jdbc:ignite protocol. See documentation for version 1.3
> > > > > > https://apacheignite.readme.io/v1.3/docs/jdbc-driver
> > > > > >
> > > > > > Thus you can control used JDBC driver type (new or old) just
with
> > > > choosen
> > > > > > protocol.
> > > > > >
> > > > > > Please, note, that old JDBC driver is deprecated and can be
> removed
> > > > from
> > > > > > future releases.
> > > > > >
> > > > > > On Mon, Dec 7, 2015 at 6:41 AM, Konstantin Boudnik <
> cos@apache.org
> > >
> > > > > wrote:
> > > > > >
> > > > > > > Guys, I am looking into [1] and see a reference to
> > > > > > >
> > > > > > > ignite.jdbc.url = "jdbc:ignite:cfg://"
> > > > > > >
> > > > > > > So, I am curious if there's a way to fetch node's config
via
> JDBC
> > > > > somehow?
> > > > > > > Or
> > > > > > > this is just a simple error in the doc, which needs to
be
> fixed?
> > > > > > >
> > > > > > > Would appreciate the insight from the team. Thanks!
> > > > > > >   Cos
> > > > > > >
> > > > > > > [1]
> > > > > > >
> > > > >
> > > >
> > >
> >
> https://zeppelin.incubator.apache.org/docs/0.5.5-incubating/interpreter/ignite.html
> > > > > > >
> > > > > > >
> > > > > >
> > > > > >
> > > > > > --
> > > > > > Andrey Gura
> > > > > > GridGain Systems, Inc.
> > > > > > www.gridgain.com
> > > > >
> > > >
> > > >
> > > >
> > > > --
> > > > Andrey Gura
> > > > GridGain Systems, Inc.
> > > > www.gridgain.com
> > > >
> > >
> >
> >
> >
> > --
> > Andrey Gura
> > GridGain Systems, Inc.
> > www.gridgain.com
> >
>



-- 
Andrey Gura
GridGain Systems, Inc.
www.gridgain.com

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