Mailing-List: contact user-help@ignite.apache.org; run by ezmlm
Precedence: bulk
Reply-To: user@ignite.apache.org
MIME-Version: 1.0
In-Reply-To: <1509561478178-0.post@n6.nabble.com>
References: <1509561478178-0.post@n6.nabble.com>
From: Ilya Kasnacheev <ilya.kasnacheev@gmail.com>
Date: Thu, 2 Nov 2017 19:39:05 +0300
Message-ID: <CAA-MoLgsetDy-chjKP4uGzaUtJgOJBwUyQxzLH78DGg0AquZEA@mail.gmail.com>
Subject: Re: Unable to query Ignite 2.3 table using 2.2 JDBC thin client
To: user@ignite.apache.org
Content-Type: multipart/alternative; boundary="94eb2c127f62638aec055d02a08d"
archived-at: Thu, 02 Nov 2017 16:39:11 -0000

--94eb2c127f62638aec055d02a08d
Content-Type: text/plain; charset="UTF-8"

Hello!

Unfortunately, it seems that metadata queries are not compatible between
2.1/2.2 and 2.3.

The richness of available JDBC metadata was considerably increased in 2.3,
and new type value was assigned to metadata responses.

Hence, 2.2 client can send metadata request to 2.3, but it is unable to
parse the response. And DBeaver relies heavily on JDBC metadata.

So the solution here is to upgrade JDBC thin client, there was a lot of
updates to it anyway.

Regards,


-- 
Ilya Kasnacheev

2017-11-01 21:37 GMT+03:00 blackfield <charles.katili@maxpoint.com>:

> Hey,
>
> I run *Ignite 2.3* locally for testing...just one node, persistence is
> enabled.
>
> Using DBeaver - using *Ignite 2.2 *JDBC thin client,
> 1. Create two simple tables, City and Person, from the Getting started
> example.
> 2. Insert rows to those tables
>
> When I execute 'select * from Person', I got "Unknown SQL listener request
> ID;[request ID=5]" error in the DBeaver UI.
>
> If I use 2.3 JDBC thin client, I can perform the above query.
>
>
> Is this a bug, Ignite does not support backward compatibility or else?
>
>
>
>
>
> --
> Sent from: http://apache-ignite-users.70518.x6.nabble.com/
>

--94eb2c127f62638aec055d02a08d
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div><div><div><div><div>Hello!<br><br></div>Unfortunately=
, it seems that metadata queries are not compatible between 2.1/2.2 and 2.3=
.<br><br></div>The richness of available JDBC metadata was considerably inc=
reased in 2.3, and new type value was assigned to metadata responses.<br><b=
r></div>Hence, 2.2 client can send metadata request to 2.3, but it is unabl=
e to parse the response. And DBeaver relies heavily on JDBC metadata.<br><b=
r></div>So the solution here is to upgrade JDBC thin client, there was a lo=
t of updates to it anyway.<br><br></div>Regards,<br><div><div><div><div><br=
><br></div></div></div></div></div><div class=3D"gmail_extra"><br clear=3D"=
all"><div><div class=3D"gmail_signature" data-smartmail=3D"gmail_signature"=
><div dir=3D"ltr"><div><div dir=3D"ltr">-- <br></div><div dir=3D"ltr">Ilya =
Kasnacheev<br></div></div></div></div></div>
<br><div class=3D"gmail_quote">2017-11-01 21:37 GMT+03:00 blackfield <span =
dir=3D"ltr">&lt;<a href=3D"mailto:charles.katili@maxpoint.com" target=3D"_b=
lank">charles.katili@maxpoint.com</a>&gt;</span>:<br><blockquote class=3D"g=
mail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-l=
eft:1ex">Hey,<br>
<br>
I run *Ignite 2.3* locally for testing...just one node, persistence is<br>
enabled.<br>
<br>
Using DBeaver - using *Ignite 2.2 *JDBC thin client,<br>
1. Create two simple tables, City and Person, from the Getting started<br>
example.<br>
2. Insert rows to those tables<br>
<br>
When I execute &#39;select * from Person&#39;, I got &quot;Unknown SQL list=
ener request<br>
ID;[request ID=3D5]&quot; error in the DBeaver UI.<br>
<br>
If I use 2.3 JDBC thin client, I can perform the above query.<br>
<br>
<br>
Is this a bug, Ignite does not support backward compatibility or else?<br>
<br>
<br>
<br>
<br>
<br>
--<br>
Sent from: <a href=3D"http://apache-ignite-users.70518.x6.nabble.com/" rel=
=3D"noreferrer" target=3D"_blank">http://apache-ignite-users.<wbr>70518.x6.=
nabble.com/</a><br>
</blockquote></div><br></div>

--94eb2c127f62638aec055d02a08d--