Re: What is jdbc:ignite:cfg ??

[Konstantin Boudnik]

On Wed, Jan 20, 2016 at 03:32PM, Andrey Gura wrote:
> Dmitry,
> 
> We can suggest to Zepplin comunity introduce parameters per
> notebook/paragraph that can be passed to interpreter.
> 
> The second option is adding some keywords that can be parsed by
> interpreter.
> 
> I think that Val's suggestion is more suitable at this moment.

I actually like Val's ideas as well. What he is proposing is the way to
improve UX of the product. See, more and more ppl - especially in this
FastData arena - aren't developers. They won't know an exception even if you
hit them over the head with one. Hence, whenever an exception is thrown in the
UI like Zeppelin, that's the end of the world for most of them.

Ideally, we need to go an extra mile to hide all this complexity as much as
possible. In fact, the complexity is what killing all these cool technologies.
In order to run some simple linear regression calculation, one has to be an
expert in Unix, Java, system integration, and god knows what else ;) 

Cos

> On Wed, Jan 20, 2016 at 1:10 AM, Dmitriy Setrakyan 
> wrote:
> 
> > Can we just start a different client connection per-notebook? This way user
> > can specify different default cache per notebook, no?
> >
> > Andrey, we already have the explanation for why it does not work. Can you
> > provide some ideas on what needs to happen to make it work?
> >
> > D.
> >
> > On Tue, Jan 19, 2016 at 11:22 AM, Valentin Kulichenko <
> > valentin.kuliche...@gmail.com> wrote:
> >
> > > Andrey,
> > >
> > > My answers are inline...
> > >
> > > On Tue, Jan 19, 2016 at 4:14 AM, Andrey Gura  wrote:
> > >
> > > > Val,
> > > >
> > > > I have a couple of questions:
> > > >
> > > > 1. What cache should be used by JDBC driver for query execution when no
> > > > cache name in JDBC URL? I see only one option: any user cache. But it
> > can
> > > > bring some random behavior. Caches can be created/deleted dynamically
> > and
> > > > JDBC connection can refer to removed cache.
> > > >
> > >
> > > If cache name is not provided in the URL, all cache names have to be
> > > provided in the query (except the default cache if it exists). If one of
> > > the names refers to non-existing cache, exception will be thrown. Default
> > > cache is not different from this standpoint - if the query contains a
> > type
> > > without cache name specified and default cache doesn't exist, exception
> > is
> > > thrown as well.
> > >
> > >
> > > >
> > > > 2. How user should refer to default cache in queries in case when some
> > > non
> > > > default cache name used as connection parameter?
> > > >
> > >
> > > This is something that is not possible now anyway, right? Actually, I've
> > > never seen an example of the default cache being used, especially if
> > > multiple caches are used. So I would not sacrifice usability to support
> > > this use case. If one wants to query the default cache, leave it blank in
> > > the URL and explicitly specify names of all other caches.
> > >
> > >
> > > >
> > > >
> > > >
> > > > On Tue, Jan 19, 2016 at 12:47 AM, Valentin Kulichenko <
> > > > valentin.kuliche...@gmail.com> wrote:
> > > >
> > > > > I think we can just remove the requirement of having the default
> > cache
> > > > when
> > > > > no cache name is provided in the JDBC URL. I don't see any reason to
> > > > refuse
> > > > > connection in this case, because if query doesn't properly specify
> > > cache
> > > > > names for all participating types, the exception will be thrown
> > anyway.
> > > > >
> > > > > Thoughts?
> > > > >
> > > > > -Val
> > > > >
> > > > > On Mon, Jan 18, 2016 at 6:35 AM, Andrey Gura 
> > > wrote:
> > > > >
> > > > > > Cos,
> > > > > >
> > > > > > if cache name isn't specified in JDBC URL then default cache will
> > be
> > > > > used.
> > > > > >
> > > > > > If default cache isn't created then driver will throw exception
> > with
> > > > > > "Client is invalid. Probably cache name is wrong" message.
> > > > > >
> > > > > > You can use workaround and just create default cache. I understand
> > > that
> > > > > > this solution is not what you want :)
> > > > > >
> > > > > > I don't have any idea about how to avoid using cache name because
> > > > Ignite
> > > > > > API requires named cache instance in order to execute query.
> > > > > >
> > > > > >
> > > > > >
> > > > > > On Sat, Jan 16, 2016 at 10:44 AM, Konstantin Boudnik <
> > c...@apache.org
> > > >
> > > > > > wrote:
> > > > > >
> > > > > > > Thanks Andrey.
> > > > > > >
> > > > > > > I think option one is a bad UX, cause creating an interpreter
> > isn't
> > > > > > >  a) a simple button click (might be improved later on by Z.
> > folks)
> > > > > > >  b) what if I have 25 different caches and the equal number of
> > > > > > interpreters
> > > > > > > and need to make a change to all of them?
> > > > > > >
> > > > > > > The second option sounds good, yet the interpreter still needs to
> > > > have
> > > > > a
> > > > > > > 

Re: What is jdbc:ignite:cfg ??

[Andrey Gura]

Val,

I have a couple of questions:

1. What cache should be used by JDBC driver for query execution when no
cache name in JDBC URL? I see only one option: any user cache. But it can
bring some random behavior. Caches can be created/deleted dynamically and
JDBC connection can refer to removed cache.

2. How user should refer to default cache in queries in case when some non
default cache name used as connection parameter?



On Tue, Jan 19, 2016 at 12:47 AM, Valentin Kulichenko <
valentin.kuliche...@gmail.com> wrote:

> I think we can just remove the requirement of having the default cache when
> no cache name is provided in the JDBC URL. I don't see any reason to refuse
> connection in this case, because if query doesn't properly specify cache
> names for all participating types, the exception will be thrown anyway.
>
> Thoughts?
>
> -Val
>
> On Mon, Jan 18, 2016 at 6:35 AM, Andrey Gura  wrote:
>
> > Cos,
> >
> > if cache name isn't specified in JDBC URL then default cache will be
> used.
> >
> > If default cache isn't created then driver will throw exception with
> > "Client is invalid. Probably cache name is wrong" message.
> >
> > You can use workaround and just create default cache. I understand that
> > this solution is not what you want :)
> >
> > I don't have any idea about how to avoid using cache name because Ignite
> > API requires named cache instance in order to execute query.
> >
> >
> >
> > On Sat, Jan 16, 2016 at 10:44 AM, Konstantin Boudnik 
> > wrote:
> >
> > > Thanks Andrey.
> > >
> > > I think option one is a bad UX, cause creating an interpreter isn't
> > >  a) a simple button click (might be improved later on by Z. folks)
> > >  b) what if I have 25 different caches and the equal number of
> > interpreters
> > > and need to make a change to all of them?
> > >
> > > The second option sounds good, yet the interpreter still needs to have
> a
> > > particular cache name in the configuration, which now looks weird
> because
> > > I am
> > > working with multiple caches at once.
> > >
> > > It is possible to avoid specifying the cache name all together, in
> which
> > > case
> > > a user will have to simply go with what you call cross-cache queries?
> > >
> > > Cos
> > >
> > > On Thu, Jan 14, 2016 at 07:22PM, Andrey Gura wrote:
> > > > Cos,
> > > >
> > > > you have two options in order to create different notebooks for
> > separate
> > > > caches:
> > > >
> > > > 1. You can create separate interpreter with cpecific configuration
> for
> > > each
> > > > notebook. Then you can bind interpreters to notebooks. You can also
> > bind
> > > > many interpreters to oone notebook and use different interpreters in
> > > > different paragraphs.
> > > >
> > > > 2. You can use cross-cache like queries with one interpreter. From
> > docs:
> > > > "In this case, cache names act as schema names in regular SQL. This
> > means
> > > > all caches can be referred by cache names in quotes."
> > >
> >
> >
> >
> > --
> > Andrey Gura
> > GridGain Systems, Inc.
> > www.gridgain.com
> >
>



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

Re: What is jdbc:ignite:cfg ??

[Dmitriy Setrakyan]

Can we just start a different client connection per-notebook? This way user
can specify different default cache per notebook, no?

Andrey, we already have the explanation for why it does not work. Can you
provide some ideas on what needs to happen to make it work?

D.

On Tue, Jan 19, 2016 at 11:22 AM, Valentin Kulichenko <
valentin.kuliche...@gmail.com> wrote:

> Andrey,
>
> My answers are inline...
>
> On Tue, Jan 19, 2016 at 4:14 AM, Andrey Gura  wrote:
>
> > Val,
> >
> > I have a couple of questions:
> >
> > 1. What cache should be used by JDBC driver for query execution when no
> > cache name in JDBC URL? I see only one option: any user cache. But it can
> > bring some random behavior. Caches can be created/deleted dynamically and
> > JDBC connection can refer to removed cache.
> >
>
> If cache name is not provided in the URL, all cache names have to be
> provided in the query (except the default cache if it exists). If one of
> the names refers to non-existing cache, exception will be thrown. Default
> cache is not different from this standpoint - if the query contains a type
> without cache name specified and default cache doesn't exist, exception is
> thrown as well.
>
>
> >
> > 2. How user should refer to default cache in queries in case when some
> non
> > default cache name used as connection parameter?
> >
>
> This is something that is not possible now anyway, right? Actually, I've
> never seen an example of the default cache being used, especially if
> multiple caches are used. So I would not sacrifice usability to support
> this use case. If one wants to query the default cache, leave it blank in
> the URL and explicitly specify names of all other caches.
>
>
> >
> >
> >
> > On Tue, Jan 19, 2016 at 12:47 AM, Valentin Kulichenko <
> > valentin.kuliche...@gmail.com> wrote:
> >
> > > I think we can just remove the requirement of having the default cache
> > when
> > > no cache name is provided in the JDBC URL. I don't see any reason to
> > refuse
> > > connection in this case, because if query doesn't properly specify
> cache
> > > names for all participating types, the exception will be thrown anyway.
> > >
> > > Thoughts?
> > >
> > > -Val
> > >
> > > On Mon, Jan 18, 2016 at 6:35 AM, Andrey Gura 
> wrote:
> > >
> > > > Cos,
> > > >
> > > > if cache name isn't specified in JDBC URL then default cache will be
> > > used.
> > > >
> > > > If default cache isn't created then driver will throw exception with
> > > > "Client is invalid. Probably cache name is wrong" message.
> > > >
> > > > You can use workaround and just create default cache. I understand
> that
> > > > this solution is not what you want :)
> > > >
> > > > I don't have any idea about how to avoid using cache name because
> > Ignite
> > > > API requires named cache instance in order to execute query.
> > > >
> > > >
> > > >
> > > > On Sat, Jan 16, 2016 at 10:44 AM, Konstantin Boudnik  >
> > > > wrote:
> > > >
> > > > > Thanks Andrey.
> > > > >
> > > > > I think option one is a bad UX, cause creating an interpreter isn't
> > > > >  a) a simple button click (might be improved later on by Z. folks)
> > > > >  b) what if I have 25 different caches and the equal number of
> > > > interpreters
> > > > > and need to make a change to all of them?
> > > > >
> > > > > The second option sounds good, yet the interpreter still needs to
> > have
> > > a
> > > > > particular cache name in the configuration, which now looks weird
> > > because
> > > > > I am
> > > > > working with multiple caches at once.
> > > > >
> > > > > It is possible to avoid specifying the cache name all together, in
> > > which
> > > > > case
> > > > > a user will have to simply go with what you call cross-cache
> queries?
> > > > >
> > > > > Cos
> > > > >
> > > > > On Thu, Jan 14, 2016 at 07:22PM, Andrey Gura wrote:
> > > > > > Cos,
> > > > > >
> > > > > > you have two options in order to create different notebooks for
> > > > separate
> > > > > > caches:
> > > > > >
> > > > > > 1. You can create separate interpreter with cpecific
> configuration
> > > for
> > > > > each
> > > > > > notebook. Then you can bind interpreters to notebooks. You can
> also
> > > > bind
> > > > > > many interpreters to oone notebook and use different interpreters
> > in
> > > > > > different paragraphs.
> > > > > >
> > > > > > 2. You can use cross-cache like queries with one interpreter.
> From
> > > > docs:
> > > > > > "In this case, cache names act as schema names in regular SQL.
> This
> > > > means
> > > > > > all caches can be referred by cache names in quotes."
> > > > >
> > > >
> > > >
> > > >
> > > > --
> > > > Andrey Gura
> > > > GridGain Systems, Inc.
> > > > www.gridgain.com
> > > >
> > >
> >
> >
> >
> > --
> > Andrey Gura
> > GridGain Systems, Inc.
> > www.gridgain.com
> >
>

Re: What is jdbc:ignite:cfg ??

[Valentin Kulichenko]

Andrey,

My answers are inline...

On Tue, Jan 19, 2016 at 4:14 AM, Andrey Gura  wrote:

> Val,
>
> I have a couple of questions:
>
> 1. What cache should be used by JDBC driver for query execution when no
> cache name in JDBC URL? I see only one option: any user cache. But it can
> bring some random behavior. Caches can be created/deleted dynamically and
> JDBC connection can refer to removed cache.
>

If cache name is not provided in the URL, all cache names have to be
provided in the query (except the default cache if it exists). If one of
the names refers to non-existing cache, exception will be thrown. Default
cache is not different from this standpoint - if the query contains a type
without cache name specified and default cache doesn't exist, exception is
thrown as well.


>
> 2. How user should refer to default cache in queries in case when some non
> default cache name used as connection parameter?
>

This is something that is not possible now anyway, right? Actually, I've
never seen an example of the default cache being used, especially if
multiple caches are used. So I would not sacrifice usability to support
this use case. If one wants to query the default cache, leave it blank in
the URL and explicitly specify names of all other caches.


>
>
>
> On Tue, Jan 19, 2016 at 12:47 AM, Valentin Kulichenko <
> valentin.kuliche...@gmail.com> wrote:
>
> > I think we can just remove the requirement of having the default cache
> when
> > no cache name is provided in the JDBC URL. I don't see any reason to
> refuse
> > connection in this case, because if query doesn't properly specify cache
> > names for all participating types, the exception will be thrown anyway.
> >
> > Thoughts?
> >
> > -Val
> >
> > On Mon, Jan 18, 2016 at 6:35 AM, Andrey Gura  wrote:
> >
> > > Cos,
> > >
> > > if cache name isn't specified in JDBC URL then default cache will be
> > used.
> > >
> > > If default cache isn't created then driver will throw exception with
> > > "Client is invalid. Probably cache name is wrong" message.
> > >
> > > You can use workaround and just create default cache. I understand that
> > > this solution is not what you want :)
> > >
> > > I don't have any idea about how to avoid using cache name because
> Ignite
> > > API requires named cache instance in order to execute query.
> > >
> > >
> > >
> > > On Sat, Jan 16, 2016 at 10:44 AM, Konstantin Boudnik 
> > > wrote:
> > >
> > > > Thanks Andrey.
> > > >
> > > > I think option one is a bad UX, cause creating an interpreter isn't
> > > >  a) a simple button click (might be improved later on by Z. folks)
> > > >  b) what if I have 25 different caches and the equal number of
> > > interpreters
> > > > and need to make a change to all of them?
> > > >
> > > > The second option sounds good, yet the interpreter still needs to
> have
> > a
> > > > particular cache name in the configuration, which now looks weird
> > because
> > > > I am
> > > > working with multiple caches at once.
> > > >
> > > > It is possible to avoid specifying the cache name all together, in
> > which
> > > > case
> > > > a user will have to simply go with what you call cross-cache queries?
> > > >
> > > > Cos
> > > >
> > > > On Thu, Jan 14, 2016 at 07:22PM, Andrey Gura wrote:
> > > > > Cos,
> > > > >
> > > > > you have two options in order to create different notebooks for
> > > separate
> > > > > caches:
> > > > >
> > > > > 1. You can create separate interpreter with cpecific configuration
> > for
> > > > each
> > > > > notebook. Then you can bind interpreters to notebooks. You can also
> > > bind
> > > > > many interpreters to oone notebook and use different interpreters
> in
> > > > > different paragraphs.
> > > > >
> > > > > 2. You can use cross-cache like queries with one interpreter. From
> > > docs:
> > > > > "In this case, cache names act as schema names in regular SQL. This
> > > means
> > > > > all caches can be referred by cache names in quotes."
> > > >
> > >
> > >
> > >
> > > --
> > > Andrey Gura
> > > GridGain Systems, Inc.
> > > www.gridgain.com
> > >
> >
>
>
>
> --
> Andrey Gura
> GridGain Systems, Inc.
> www.gridgain.com
>

Re: What is jdbc:ignite:cfg ??

[Andrey Gura]

Dima,

because notebook doesn't have any settings for it.

On Thu, Jan 14, 2016 at 11:30 PM, Dmitriy Setrakyan 
wrote:

> Andrey, I am still a bit unclear. Why not have ability to specify a default
> cache per notebook, not per-interpreter?
>
> On Thu, Jan 14, 2016 at 8:42 AM, Andrey Gura  wrote:
>
> > Hello,
> >
> > JFYI, I created ticket as result of this discussion:
> > https://issues.apache.org/jira/browse/IGNITE-2382
> >
> >
> >
> > On Thu, Dec 10, 2015 at 10:29 PM, Dmitriy Setrakyan <
> dsetrak...@apache.org
> > >
> > wrote:
> >
> > > Andrey,
> > >
> > > I agree on both points. However, I still think that we should provide
> > > sample step-by-step guide with a sample configuration. This
> configuration
> > > should include a couple of data types, like Person and Organization,
> > define
> > > indexes for them, etc.
> > >
> > > This guide should include:
> > >
> > > 1. Start Ignite Servers
> > > 2. Populate data - should have example with configuration.
> > > 3. Query data using JDBC driver - example code and, if needed,
> > > configuration to support it.
> > >
> > > Do you mind adding it?
> > >
> > > D.
> > >
> > > On Thu, Dec 10, 2015 at 7:50 AM, Andrey Gura 
> wrote:
> > >
> > > > I didn't think that we should force client mode at moment of
> > > > implementation. But I can't provide any reason not to do it.
> > > >
> > > > So we need two small improvements to JDBC driver:
> > > >
> > > > 1. Always force client mode.
> > > > 2. Use default configuration in cases when user did't specify any
> URL.
> > > This
> > > > configuration should just use client mode and default values for rest
> > > > properties.
> > > >
> > > > Right?
> > > >
> > > > On Thu, Dec 10, 2015 at 9:05 AM, Dmitriy Setrakyan <
> > > dsetrak...@apache.org>
> > > > wrote:
> > > >
> > > > > On Wed, Dec 9, 2015 at 10:04 PM, Valentin Kulichenko <
> > > > > valentin.kuliche...@gmail.com> wrote:
> > > > >
> > > > > > Actually, why don't we set it automatically? It doesn't make much
> > > sense
> > > > > to
> > > > > > have a server node in a JDBC driver.
> > > > > >
> > > > >
> > > > > Completely agree.
> > > > >
> > > > >
> > > > > >
> > > > > > -Val
> > > > > >
> > > > > > On Wed, Dec 9, 2015 at 10:02 PM, Dmitriy Setrakyan <
> > > > > dsetrak...@apache.org>
> > > > > > wrote:
> > > > > >
> > > > > > > On Wed, Dec 9, 2015 at 6:46 PM, Konstantin Boudnik <
> > c...@apache.org
> > > >
> > > > > > wrote:
> > > > > > >
> > > > > > > > On Wed, Dec 09, 2015 at 04:01PM, Dmitriy Setrakyan wrote:
> > > > > > > > > Thanks Andrey!
> > > > > > > > >
> > > > > > > > > Why are we enabling peer class loading for the JDBC driver
> in
> > > > your
> > > > > > > > example?
> > > > > > > > > To my knowledge, we are not deploying any classes, are we?
> > > Also,
> > > > > the
> > > > > > > TCP
> > > > > > > > > discovery with multicast is the default, so no reason to
> > > specify
> > > > it
> > > > > > > > either.
> > > > > > > > >
> > > > > > > > > It seems that the only properly required is
> clientMode=true,
> > > no?
> > > > > > > >
> > > > > > > > If this is the case, then _no_ config is really needed,
> > perhaps?
> > > > > > > >
> > > > > > >
> > > > > > > Well, we still need to specify clientMode, no?
> > > > > > >
> > > > > > >
> > > > > > > >
> > > > > > > > >
> > > > > > > > > D.
> > > > > > > > >
> > > > > > > > > On Wed, Dec 9, 2015 at 8:54 AM, Andrey Gura <
> > > ag...@gridgain.com>
> > > > > > > wrote:
> > > > > > > > >
> > > > > > > > > > Configuration sample added.
> > > > > > > > > >
> > > > > > > > > > On Tue, Dec 8, 2015 at 10:20 PM, Dmitriy Setrakyan <
> > > > > > > > dsetrak...@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 <
> > > > > ag...@gridgain.com
> > > > > > >
> > > > > > > > wrote:
> > > > > > > > > > >
> > > > > > > > > > > > Done. I hope that is more clear now.
> > > > > > > > > > > >
> > > > > > > > > > > > On Tue, Dec 8, 2015 at 1:14 AM, Dmitriy Setrakyan <
> > > > > > > > > > dsetrak...@apache.org
> > > > > > > > > > > >
> > > > > > > > > > > > wrote:
> > > > > > > > > > > >
> > > > > > > > > > > > > On Mon, Dec 7, 2015 at 10:17 AM, Andrey Gura <
> > > > > > > ag...@gridgain.com
> > > > > > > > >
> > > > > > > > > > > wrote:
> > > > > > > > > > > > >
> > > > > > > > > > > > > > Cos,
> > > > > > > > > > > > > >
> > > > > > > > > > > > > >  sepcifies configuration file for
> > Ignite
> > > > > client
> > > > > > > > node
> > > > > > > > > > that
> > > > > > > > > > > > > will
> > > > > > > > > > > > > > be started during connection establishing by JDBC
> > > > driver.
> > > 

Re: What is jdbc:ignite:cfg ??

[Konstantin Boudnik]

Thanks Andrey.

I think option one is a bad UX, cause creating an interpreter isn't 
 a) a simple button click (might be improved later on by Z. folks)
 b) what if I have 25 different caches and the equal number of interpreters
and need to make a change to all of them? 

The second option sounds good, yet the interpreter still needs to have a
particular cache name in the configuration, which now looks weird because I am
working with multiple caches at once.

It is possible to avoid specifying the cache name all together, in which case
a user will have to simply go with what you call cross-cache queries?

Cos

On Thu, Jan 14, 2016 at 07:22PM, Andrey Gura wrote:
> Cos,
> 
> you have two options in order to create different notebooks for separate
> caches:
> 
> 1. You can create separate interpreter with cpecific configuration for each
> notebook. Then you can bind interpreters to notebooks. You can also bind
> many interpreters to oone notebook and use different interpreters in
> different paragraphs.
> 
> 2. You can use cross-cache like queries with one interpreter. From docs:
> "In this case, cache names act as schema names in regular SQL. This means
> all caches can be referred by cache names in quotes."


signature.asc
Description: Digital signature

Re: What is jdbc:ignite:cfg ??

[Andrey Gura]

Hello,

JFYI, I created ticket as result of this discussion:
https://issues.apache.org/jira/browse/IGNITE-2382



On Thu, Dec 10, 2015 at 10:29 PM, Dmitriy Setrakyan 
wrote:

> Andrey,
>
> I agree on both points. However, I still think that we should provide
> sample step-by-step guide with a sample configuration. This configuration
> should include a couple of data types, like Person and Organization, define
> indexes for them, etc.
>
> This guide should include:
>
> 1. Start Ignite Servers
> 2. Populate data - should have example with configuration.
> 3. Query data using JDBC driver - example code and, if needed,
> configuration to support it.
>
> Do you mind adding it?
>
> D.
>
> On Thu, Dec 10, 2015 at 7:50 AM, Andrey Gura  wrote:
>
> > I didn't think that we should force client mode at moment of
> > implementation. But I can't provide any reason not to do it.
> >
> > So we need two small improvements to JDBC driver:
> >
> > 1. Always force client mode.
> > 2. Use default configuration in cases when user did't specify any URL.
> This
> > configuration should just use client mode and default values for rest
> > properties.
> >
> > Right?
> >
> > On Thu, Dec 10, 2015 at 9:05 AM, Dmitriy Setrakyan <
> dsetrak...@apache.org>
> > wrote:
> >
> > > On Wed, Dec 9, 2015 at 10:04 PM, Valentin Kulichenko <
> > > valentin.kuliche...@gmail.com> wrote:
> > >
> > > > Actually, why don't we set it automatically? It doesn't make much
> sense
> > > to
> > > > have a server node in a JDBC driver.
> > > >
> > >
> > > Completely agree.
> > >
> > >
> > > >
> > > > -Val
> > > >
> > > > On Wed, Dec 9, 2015 at 10:02 PM, Dmitriy Setrakyan <
> > > dsetrak...@apache.org>
> > > > wrote:
> > > >
> > > > > On Wed, Dec 9, 2015 at 6:46 PM, Konstantin Boudnik  >
> > > > wrote:
> > > > >
> > > > > > On Wed, Dec 09, 2015 at 04:01PM, Dmitriy Setrakyan wrote:
> > > > > > > Thanks Andrey!
> > > > > > >
> > > > > > > Why are we enabling peer class loading for the JDBC driver in
> > your
> > > > > > example?
> > > > > > > To my knowledge, we are not deploying any classes, are we?
> Also,
> > > the
> > > > > TCP
> > > > > > > discovery with multicast is the default, so no reason to
> specify
> > it
> > > > > > either.
> > > > > > >
> > > > > > > It seems that the only properly required is clientMode=true,
> no?
> > > > > >
> > > > > > If this is the case, then _no_ config is really needed, perhaps?
> > > > > >
> > > > >
> > > > > Well, we still need to specify clientMode, no?
> > > > >
> > > > >
> > > > > >
> > > > > > >
> > > > > > > D.
> > > > > > >
> > > > > > > On Wed, Dec 9, 2015 at 8:54 AM, Andrey Gura <
> ag...@gridgain.com>
> > > > > wrote:
> > > > > > >
> > > > > > > > Configuration sample added.
> > > > > > > >
> > > > > > > > On Tue, Dec 8, 2015 at 10:20 PM, Dmitriy Setrakyan <
> > > > > > dsetrak...@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 <
> > > ag...@gridgain.com
> > > > >
> > > > > > wrote:
> > > > > > > > >
> > > > > > > > > > Done. I hope that is more clear now.
> > > > > > > > > >
> > > > > > > > > > On Tue, Dec 8, 2015 at 1:14 AM, Dmitriy Setrakyan <
> > > > > > > > dsetrak...@apache.org
> > > > > > > > > >
> > > > > > > > > > wrote:
> > > > > > > > > >
> > > > > > > > > > > On Mon, Dec 7, 2015 at 10:17 AM, Andrey Gura <
> > > > > ag...@gridgain.com
> > > > > > >
> > > > > > > > > wrote:
> > > > > > > > > > >
> > > > > > > > > > > > Cos,
> > > > > > > > > > > >
> > > > > > > > > > > >  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 <
> > > > > > c...@apache.org
> > > > > > > > >
> > > > > > > > > > > wrote:
> > > > > > > > > > > >
> > > > > > > > > > > > > Thanks Andrey!
> > > > > > > > > > > > >
> > > > > > > > > > > > > Still a bit unclear: the doc says
> > > > > > > > > > > > > " is required and represents any valid
> > URL
> > > > > which
> > > > > > > > points
> > > > > > > > > > to
> > > > > > > > > > > > > Ignite configuration file"
> > > > > > > > > > > > >
> > > > > > > > > > > 

Re: What is jdbc:ignite:cfg ??

[Dmitriy Setrakyan]

Andrey, I am still a bit unclear. Why not have ability to specify a default
cache per notebook, not per-interpreter?

On Thu, Jan 14, 2016 at 8:42 AM, Andrey Gura  wrote:

> Hello,
>
> JFYI, I created ticket as result of this discussion:
> https://issues.apache.org/jira/browse/IGNITE-2382
>
>
>
> On Thu, Dec 10, 2015 at 10:29 PM, Dmitriy Setrakyan  >
> wrote:
>
> > Andrey,
> >
> > I agree on both points. However, I still think that we should provide
> > sample step-by-step guide with a sample configuration. This configuration
> > should include a couple of data types, like Person and Organization,
> define
> > indexes for them, etc.
> >
> > This guide should include:
> >
> > 1. Start Ignite Servers
> > 2. Populate data - should have example with configuration.
> > 3. Query data using JDBC driver - example code and, if needed,
> > configuration to support it.
> >
> > Do you mind adding it?
> >
> > D.
> >
> > On Thu, Dec 10, 2015 at 7:50 AM, Andrey Gura  wrote:
> >
> > > I didn't think that we should force client mode at moment of
> > > implementation. But I can't provide any reason not to do it.
> > >
> > > So we need two small improvements to JDBC driver:
> > >
> > > 1. Always force client mode.
> > > 2. Use default configuration in cases when user did't specify any URL.
> > This
> > > configuration should just use client mode and default values for rest
> > > properties.
> > >
> > > Right?
> > >
> > > On Thu, Dec 10, 2015 at 9:05 AM, Dmitriy Setrakyan <
> > dsetrak...@apache.org>
> > > wrote:
> > >
> > > > On Wed, Dec 9, 2015 at 10:04 PM, Valentin Kulichenko <
> > > > valentin.kuliche...@gmail.com> wrote:
> > > >
> > > > > Actually, why don't we set it automatically? It doesn't make much
> > sense
> > > > to
> > > > > have a server node in a JDBC driver.
> > > > >
> > > >
> > > > Completely agree.
> > > >
> > > >
> > > > >
> > > > > -Val
> > > > >
> > > > > On Wed, Dec 9, 2015 at 10:02 PM, Dmitriy Setrakyan <
> > > > dsetrak...@apache.org>
> > > > > wrote:
> > > > >
> > > > > > On Wed, Dec 9, 2015 at 6:46 PM, Konstantin Boudnik <
> c...@apache.org
> > >
> > > > > wrote:
> > > > > >
> > > > > > > On Wed, Dec 09, 2015 at 04:01PM, Dmitriy Setrakyan wrote:
> > > > > > > > Thanks Andrey!
> > > > > > > >
> > > > > > > > Why are we enabling peer class loading for the JDBC driver in
> > > your
> > > > > > > example?
> > > > > > > > To my knowledge, we are not deploying any classes, are we?
> > Also,
> > > > the
> > > > > > TCP
> > > > > > > > discovery with multicast is the default, so no reason to
> > specify
> > > it
> > > > > > > either.
> > > > > > > >
> > > > > > > > It seems that the only properly required is clientMode=true,
> > no?
> > > > > > >
> > > > > > > If this is the case, then _no_ config is really needed,
> perhaps?
> > > > > > >
> > > > > >
> > > > > > Well, we still need to specify clientMode, no?
> > > > > >
> > > > > >
> > > > > > >
> > > > > > > >
> > > > > > > > D.
> > > > > > > >
> > > > > > > > On Wed, Dec 9, 2015 at 8:54 AM, Andrey Gura <
> > ag...@gridgain.com>
> > > > > > wrote:
> > > > > > > >
> > > > > > > > > Configuration sample added.
> > > > > > > > >
> > > > > > > > > On Tue, Dec 8, 2015 at 10:20 PM, Dmitriy Setrakyan <
> > > > > > > dsetrak...@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 <
> > > > ag...@gridgain.com
> > > > > >
> > > > > > > wrote:
> > > > > > > > > >
> > > > > > > > > > > Done. I hope that is more clear now.
> > > > > > > > > > >
> > > > > > > > > > > On Tue, Dec 8, 2015 at 1:14 AM, Dmitriy Setrakyan <
> > > > > > > > > dsetrak...@apache.org
> > > > > > > > > > >
> > > > > > > > > > > wrote:
> > > > > > > > > > >
> > > > > > > > > > > > On Mon, Dec 7, 2015 at 10:17 AM, Andrey Gura <
> > > > > > ag...@gridgain.com
> > > > > > > >
> > > > > > > > > > wrote:
> > > > > > > > > > > >
> > > > > > > > > > > > > Cos,
> > > > > > > > > > > > >
> > > > > > > > > > > > >  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 

Re: What is jdbc:ignite:cfg ??

[Dmitriy Setrakyan]

Andrey,

I agree on both points. However, I still think that we should provide
sample step-by-step guide with a sample configuration. This configuration
should include a couple of data types, like Person and Organization, define
indexes for them, etc.

This guide should include:

1. Start Ignite Servers
2. Populate data - should have example with configuration.
3. Query data using JDBC driver - example code and, if needed,
configuration to support it.

Do you mind adding it?

D.

On Thu, Dec 10, 2015 at 7:50 AM, Andrey Gura  wrote:

> I didn't think that we should force client mode at moment of
> implementation. But I can't provide any reason not to do it.
>
> So we need two small improvements to JDBC driver:
>
> 1. Always force client mode.
> 2. Use default configuration in cases when user did't specify any URL. This
> configuration should just use client mode and default values for rest
> properties.
>
> Right?
>
> On Thu, Dec 10, 2015 at 9:05 AM, Dmitriy Setrakyan 
> wrote:
>
> > On Wed, Dec 9, 2015 at 10:04 PM, Valentin Kulichenko <
> > valentin.kuliche...@gmail.com> wrote:
> >
> > > Actually, why don't we set it automatically? It doesn't make much sense
> > to
> > > have a server node in a JDBC driver.
> > >
> >
> > Completely agree.
> >
> >
> > >
> > > -Val
> > >
> > > On Wed, Dec 9, 2015 at 10:02 PM, Dmitriy Setrakyan <
> > dsetrak...@apache.org>
> > > wrote:
> > >
> > > > On Wed, Dec 9, 2015 at 6:46 PM, Konstantin Boudnik 
> > > wrote:
> > > >
> > > > > On Wed, Dec 09, 2015 at 04:01PM, Dmitriy Setrakyan wrote:
> > > > > > Thanks Andrey!
> > > > > >
> > > > > > Why are we enabling peer class loading for the JDBC driver in
> your
> > > > > example?
> > > > > > To my knowledge, we are not deploying any classes, are we? Also,
> > the
> > > > TCP
> > > > > > discovery with multicast is the default, so no reason to specify
> it
> > > > > either.
> > > > > >
> > > > > > It seems that the only properly required is clientMode=true, no?
> > > > >
> > > > > If this is the case, then _no_ config is really needed, perhaps?
> > > > >
> > > >
> > > > Well, we still need to specify clientMode, no?
> > > >
> > > >
> > > > >
> > > > > >
> > > > > > D.
> > > > > >
> > > > > > On Wed, Dec 9, 2015 at 8:54 AM, Andrey Gura 
> > > > wrote:
> > > > > >
> > > > > > > Configuration sample added.
> > > > > > >
> > > > > > > On Tue, Dec 8, 2015 at 10:20 PM, Dmitriy Setrakyan <
> > > > > dsetrak...@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 <
> > ag...@gridgain.com
> > > >
> > > > > wrote:
> > > > > > > >
> > > > > > > > > Done. I hope that is more clear now.
> > > > > > > > >
> > > > > > > > > On Tue, Dec 8, 2015 at 1:14 AM, Dmitriy Setrakyan <
> > > > > > > dsetrak...@apache.org
> > > > > > > > >
> > > > > > > > > wrote:
> > > > > > > > >
> > > > > > > > > > On Mon, Dec 7, 2015 at 10:17 AM, Andrey Gura <
> > > > ag...@gridgain.com
> > > > > >
> > > > > > > > wrote:
> > > > > > > > > >
> > > > > > > > > > > Cos,
> > > > > > > > > > >
> > > > > > > > > > >  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 <
> > > > > c...@apache.org
> > > > > > > >
> > > > > > > > > > wrote:
> > > > > > > > > > >
> > > > > > > > > > > > Thanks Andrey!
> > > > > > > > > > > >
> > > > > > > > > > > > Still a bit unclear: the doc says
> > > > > > > > > > > > " 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
> > > > > > > > > > > >
> > > > > 

Re: What is jdbc:ignite:cfg ??

[Andrey Gura]

I didn't think that we should force client mode at moment of
implementation. But I can't provide any reason not to do it.

So we need two small improvements to JDBC driver:

1. Always force client mode.
2. Use default configuration in cases when user did't specify any URL. This
configuration should just use client mode and default values for rest
properties.

Right?

On Thu, Dec 10, 2015 at 9:05 AM, Dmitriy Setrakyan 
wrote:

> On Wed, Dec 9, 2015 at 10:04 PM, Valentin Kulichenko <
> valentin.kuliche...@gmail.com> wrote:
>
> > Actually, why don't we set it automatically? It doesn't make much sense
> to
> > have a server node in a JDBC driver.
> >
>
> Completely agree.
>
>
> >
> > -Val
> >
> > On Wed, Dec 9, 2015 at 10:02 PM, Dmitriy Setrakyan <
> dsetrak...@apache.org>
> > wrote:
> >
> > > On Wed, Dec 9, 2015 at 6:46 PM, Konstantin Boudnik 
> > wrote:
> > >
> > > > On Wed, Dec 09, 2015 at 04:01PM, Dmitriy Setrakyan wrote:
> > > > > Thanks Andrey!
> > > > >
> > > > > Why are we enabling peer class loading for the JDBC driver in your
> > > > example?
> > > > > To my knowledge, we are not deploying any classes, are we? Also,
> the
> > > TCP
> > > > > discovery with multicast is the default, so no reason to specify it
> > > > either.
> > > > >
> > > > > It seems that the only properly required is clientMode=true, no?
> > > >
> > > > If this is the case, then _no_ config is really needed, perhaps?
> > > >
> > >
> > > Well, we still need to specify clientMode, no?
> > >
> > >
> > > >
> > > > >
> > > > > D.
> > > > >
> > > > > On Wed, Dec 9, 2015 at 8:54 AM, Andrey Gura 
> > > wrote:
> > > > >
> > > > > > Configuration sample added.
> > > > > >
> > > > > > On Tue, Dec 8, 2015 at 10:20 PM, Dmitriy Setrakyan <
> > > > dsetrak...@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 <
> ag...@gridgain.com
> > >
> > > > wrote:
> > > > > > >
> > > > > > > > Done. I hope that is more clear now.
> > > > > > > >
> > > > > > > > On Tue, Dec 8, 2015 at 1:14 AM, Dmitriy Setrakyan <
> > > > > > dsetrak...@apache.org
> > > > > > > >
> > > > > > > > wrote:
> > > > > > > >
> > > > > > > > > On Mon, Dec 7, 2015 at 10:17 AM, Andrey Gura <
> > > ag...@gridgain.com
> > > > >
> > > > > > > wrote:
> > > > > > > > >
> > > > > > > > > > Cos,
> > > > > > > > > >
> > > > > > > > > >  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 <
> > > > c...@apache.org
> > > > > > >
> > > > > > > > > wrote:
> > > > > > > > > >
> > > > > > > > > > > Thanks Andrey!
> > > > > > > > > > >
> > > > > > > > > > > Still a bit unclear: the doc says
> > > > > > > > > > > " 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
> > > 

Re: What is jdbc:ignite:cfg ??

[Konstantin Boudnik]

Yup, much better now! Thanks man!

On Wed, Dec 09, 2015 at 07:54PM, Andrey Gura wrote:
> Configuration sample added.
> 
> On Tue, Dec 8, 2015 at 10:20 PM, Dmitriy Setrakyan 
> 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  wrote:
> >
> > > Done. I hope that is more clear now.
> > >
> > > On Tue, Dec 8, 2015 at 1:14 AM, Dmitriy Setrakyan  > >
> > > wrote:
> > >
> > > > On Mon, Dec 7, 2015 at 10:17 AM, Andrey Gura 
> > wrote:
> > > >
> > > > > Cos,
> > > > >
> > > > >  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 
> > > > wrote:
> > > > >
> > > > > > Thanks Andrey!
> > > > > >
> > > > > > Still a bit unclear: the doc says
> > > > > > " 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 <
> > c...@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


signature.asc
Description: Digital signature

Re: What is jdbc:ignite:cfg ??

[Dmitriy Setrakyan]

Thanks Andrey!

Why are we enabling peer class loading for the JDBC driver in your example?
To my knowledge, we are not deploying any classes, are we? Also, the TCP
discovery with multicast is the default, so no reason to specify it either.

It seems that the only properly required is clientMode=true, no?

D.

On Wed, Dec 9, 2015 at 8:54 AM, Andrey Gura  wrote:

> Configuration sample added.
>
> On Tue, Dec 8, 2015 at 10:20 PM, Dmitriy Setrakyan 
> 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  wrote:
> >
> > > Done. I hope that is more clear now.
> > >
> > > On Tue, Dec 8, 2015 at 1:14 AM, Dmitriy Setrakyan <
> dsetrak...@apache.org
> > >
> > > wrote:
> > >
> > > > On Mon, Dec 7, 2015 at 10:17 AM, Andrey Gura 
> > wrote:
> > > >
> > > > > Cos,
> > > > >
> > > > >  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  >
> > > > wrote:
> > > > >
> > > > > > Thanks Andrey!
> > > > > >
> > > > > > Still a bit unclear: the doc says
> > > > > > " 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 <
> > c...@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
>

Re: What is jdbc:ignite:cfg ??

[Konstantin Boudnik]

On Wed, Dec 09, 2015 at 04:01PM, Dmitriy Setrakyan wrote:
> Thanks Andrey!
> 
> Why are we enabling peer class loading for the JDBC driver in your example?
> To my knowledge, we are not deploying any classes, are we? Also, the TCP
> discovery with multicast is the default, so no reason to specify it either.
> 
> It seems that the only properly required is clientMode=true, no?

If this is the case, then _no_ config is really needed, perhaps?

> 
> D.
> 
> On Wed, Dec 9, 2015 at 8:54 AM, Andrey Gura  wrote:
> 
> > Configuration sample added.
> >
> > On Tue, Dec 8, 2015 at 10:20 PM, Dmitriy Setrakyan 
> > 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  wrote:
> > >
> > > > Done. I hope that is more clear now.
> > > >
> > > > On Tue, Dec 8, 2015 at 1:14 AM, Dmitriy Setrakyan <
> > dsetrak...@apache.org
> > > >
> > > > wrote:
> > > >
> > > > > On Mon, Dec 7, 2015 at 10:17 AM, Andrey Gura 
> > > wrote:
> > > > >
> > > > > > Cos,
> > > > > >
> > > > > >  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  > >
> > > > > wrote:
> > > > > >
> > > > > > > Thanks Andrey!
> > > > > > >
> > > > > > > Still a bit unclear: the doc says
> > > > > > > " 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 <
> > > c...@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
> >


signature.asc
Description: 

Re: What is jdbc:ignite:cfg ??

[Andrey Gura]

Configuration sample added.

On Tue, Dec 8, 2015 at 10:20 PM, Dmitriy Setrakyan 
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  wrote:
>
> > Done. I hope that is more clear now.
> >
> > On Tue, Dec 8, 2015 at 1:14 AM, Dmitriy Setrakyan  >
> > wrote:
> >
> > > On Mon, Dec 7, 2015 at 10:17 AM, Andrey Gura 
> wrote:
> > >
> > > > Cos,
> > > >
> > > >  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 
> > > wrote:
> > > >
> > > > > Thanks Andrey!
> > > > >
> > > > > Still a bit unclear: the doc says
> > > > > " 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 <
> c...@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

Re: What is jdbc:ignite:cfg ??

[Andrey Gura]

Done. I hope that is more clear now.

On Tue, Dec 8, 2015 at 1:14 AM, Dmitriy Setrakyan 
wrote:

> On Mon, Dec 7, 2015 at 10:17 AM, Andrey Gura  wrote:
>
> > Cos,
> >
> >  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 
> wrote:
> >
> > > Thanks Andrey!
> > >
> > > Still a bit unclear: the doc says
> > > " 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 
> > > 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

Re: What is jdbc:ignite:cfg ??

[Dmitriy Setrakyan]

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  wrote:

> Done. I hope that is more clear now.
>
> On Tue, Dec 8, 2015 at 1:14 AM, Dmitriy Setrakyan 
> wrote:
>
> > On Mon, Dec 7, 2015 at 10:17 AM, Andrey Gura  wrote:
> >
> > > Cos,
> > >
> > >  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 
> > wrote:
> > >
> > > > Thanks Andrey!
> > > >
> > > > Still a bit unclear: the doc says
> > > > " 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  >
> > > > 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
>

Re: What is jdbc:ignite:cfg ??

[Andrey Gura]

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

Re: What is jdbc:ignite:cfg ??

[Dmitriy Setrakyan]

On Mon, Dec 7, 2015 at 10:17 AM, Andrey Gura  wrote:

> Cos,
>
>  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  wrote:
>
> > Thanks Andrey!
> >
> > Still a bit unclear: the doc says
> > " 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 
> > 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
>

Re: What is jdbc:ignite:cfg ??

[Konstantin Boudnik]

Thanks Andrey!

Still a bit unclear: the doc says 
" 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  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


signature.asc
Description: Digital signature

Re: What is jdbc:ignite:cfg ??

[Andrey Gura]

Cos,

 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.

On Mon, Dec 7, 2015 at 8:59 PM, Konstantin Boudnik  wrote:

> Thanks Andrey!
>
> Still a bit unclear: the doc says
> " 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 
> 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