Hi Apache Ignite Community,
Thanks to Kenneth Shaw for Apache Ignite support to universal command-line
interface for SQL databases.
You can find details here:
https://github.com/xo/usql
Thanks,
Aleksandr
Hi All,
The same situation is for Go lang also.
There are no binaries.
Libraries are installed from source code repo, etc.:
go get -u github.com/amsokol/ignite-go-client
So the proposal is not really applicable to Go lang client.
Thanks,
Aleksandr
From: Pavel Petroshenko
Sent: 16 июня 2018 г.
Hi All,
Is there thin client protocol v1.1.0 release notes with summary of changes vs
v1.0.0?
It’s necessary to update Golang thin client.
I have added TLS and username/password support for connection already.
But I can’t find information about other changes.
Thanks,
Aleksandr
ub.com/apacheignite
>
> But I don't know who manage that.
>
> On Thu, May 17, 2018 at 9:22 PM, Aleksandr Sokolovskii
> wrote:
> > Hi Igor,
> >
> > Of course I am ready to donate code.
> >
> > You have to know that GitHub is source code repo and packa
Aleksandr,
> > I'm currently working on the improvement of the doc, so please,
> > feel free to participate with review and proposals here - [1].
> >
> > [1] -https://issues.apache.org/jira/browse/IGNITE-8039
> >
> > Best Regards,
> > Igor
> >
>
client
No problem with OP_QUERY_SQL_FIELDS.
I mean OP_QUERY_SQL.
But I overlooked "OP_QUERY_SQL - Done without unit test. Need help to
develop unit test."
Sorry. I remove my question so far)))
Thanks,
-Alexey
25.04.2018 15:40, Aleksandr Sokolovskii пишет:
> Hi Alexey,
>
>&
tion.authenticationEnabled
>
> Example of the Ignite cfg:
> https://github.com/apache/ignite/blob/master/modules/platfor
> ms/cpp/odbc-test/config/queries-auth.xml
>
> Default user (username/password) : ignite/ignite
>
> Regards,
> -Alexey
>
> 30.04.2018 17:4
Hi Alexey,
Do you have info about the following:
1) Is SSL\TLS supported for binary client protocol?
2) Are authentication and authorization supported for binary client protocol?
Thanks,
Aleksandr
From: Aleksandr Sokolovskii
Sent: 25 апреля 2018 г. 16:37
To: dev@ignite.apache.org
Subject: RE
"OP_QUERY_SQL - Done without unit test. Need help to
develop unit test."
Sorry. I remove my question so far)))
Thanks,
-Alexey
25.04.2018 15:40, Aleksandr Sokolovskii пишет:
> Hi Alexey,
>
>> Seems an important missed part is complex objects support.
>> And it's th
et the same values
which were inserted ?
Thanks,
-Alexey
[1] https://issues.apache.org/jira/browse/IGNITE-8039
[2] https://issues.apache.org/jira/browse/IGNITE-8212
25.04.2018 0:11, Aleksandr Sokolovskii пишет:
> ...forgot OP_RESOURCE_CLOSE that is implemented also.
>
> Thanks,
&g
...forgot OP_RESOURCE_CLOSE that is implemented also.
Thanks,
Aleksandr
Thanks,
Aleksandr
On 25 April 2018 at 00:06, Aleksandr Sokolovskii wrote:
> Hello All,
>
> Besides the SQL driver I implemented the following operations also:
> OP_CACHE_GET_NAMES
> OP_CACHE_C
nk you!
> > >
> > > However, let's make it clear that this client supports SQL only,
> > > and none of the other Thin Client protocol features.
> > >
> > > Pavel
> > >
> > > On Mon, Apr 23, 2018 at 10:41 PM, Aleksandr Sokolovskii
e it will be ready soon.
As far as NodeJS please note that it is already being developed by
community at the moment [1]. We hope to have it in Apache Ignite 2.6.
[1]
https://issues.apache.org/jira/browse/IGNITE-
пн, 23 апр. 2018 г. в 22:24, Aleksandr Sokolovskii :
> Hi All,
>
> I
Hi All,
I hope you are well.
I released Apache Ignite 2.4+ Go language client:
https://github.com/apache-ignite/go-client
I updated link here:
https://github.com/golang/go/wiki/SQLDrivers
Is it possible to add link to my repo to this page?:
https://apacheignite.readme.io/docs/binary-client-prot
belongs to some Ignite node, and it seems it is not
simple task to support transactions for 'thin' clients.
Thanks
On Fri, Jun 30, 2017 at 9:55 AM, Aleksandr Sokolovskii
wrote:
> Dear Vladimir,
>
> Thanks for your answer.
>
> Now I understand the difference between
works this
way):
>>> Client[platform]->*network*->EdgeNode[java]->network->Server[java]
Note additional network hop from client to edge node because thin client
lacks routing logic.
On Fri, Jun 30, 2017 at 12:38 AM, Aleksandr Sokolovskii
wrote:
> Dear Vladimir,
>
> Tha
thin
client could be faster only if you port many and many thousands of relevant
non-trivial Java code to native platform, which can be estimated not to
man-months, but to man-years to complete.
Having said that, I would recommend you to look closer to current JNI-based
implementation :-)
On
would
> have taken ages to develop true C++ and .NET libs.
>
> > It will not work for golang.
>
> Why?
>
> > Is there language-neutral protocol to communicate with Ignite server?
>
> REST, ODBC and JDBC only.
>
> —
> Denis
>
>
> > On Jun 28, 201
Denis,
I take a look into ignite cpp core.
Looks like it attaches to running jvm and calls java methods.
Please tell me that I’m wrong! )))
It will not work for golang.
Is there language-neutral protocol to communicate with Ignite server?
Thanks,
Aleksandr
From: Aleksandr Sokolovskii
Sent: 28
-Python-R-etc-td14006.html#a14028
—
Denis
> On Jun 27, 2017, at 2:29 PM, Aleksandr Sokolovskii wrote:
>
> Dear Ignite team,
>
> I see there is no native client for golang.
> I tried to fix this gap a little bit and developed golang SQL driver for
> ignite/gridgain: https://
Dear Ignite team,
I see there is no native client for golang.
I tried to fix this gap a little bit and developed golang SQL driver for
ignite/gridgain: https://github.com/amsokol/go-ignite-client.
Enjoy ))).
It's in beta phase now. I’m focusing on test coverage now.
Driver uses HTTP REST API whi
21 matches
Mail list logo