Sounds interesting. If SWIG does its job really well than agree it worth
communities efforts to give it a try.
As a side note, I assume that somewhere in the future we will come to the point
when Ignite will have its own Machine Learning API. For every ML lib it’s
essential to support Python an
I think its worth trying. Recently on userlist someone requested Golang
integration. If we can achieve this with SWIG relatively easy, then why not.
Sergi
2017-01-18 10:55 GMT+03:00 Evgeniy Stanilovskiy
:
> Hi Denis,
>
> I don`t see any problem here, i have to speak with @vozerov about this
> i
Hi Denis,
I don`t see any problem here, i have to speak with @vozerov about this
issue and he recommends me to write it into dev list. All problems that i
have with swig is :
1. jni overhead (no miracle here ...)
2. light troubles with collections API wrapping, like std::map, std::list
and
Hi Evgeniy,
Presently we’re trying to fill this gap offering SQL Grid [1]. In a nutshell,
you can connect to an Ignite cluster from your favorite language or tool with
ODBC/JDBC drivers and work with the cluster using SQL SELECT, INSERT, UPDATE,
DELETE statements.
Here is how everything works
Hi all.
Not so long ago i had to know that ignite had reduced functionality
support in scripting languages.
So, idea was to take an existing C++ client and using SWIG
(http://www.swig.org) as automatic wrapper, generate clients for absence
scripting languages.
What do you think about this c
