Re: Ignite Custom Java Code calling

2017-06-29 Thread ezhuravlev
an by Ignite native client? Client node? Evgenii -- View this message in context: http://apache-ignite-users.70518.x6.nabble.com/Ignite-Custom-Java-Code-calling-tp13986p14156.html Sent from the Apache Ignite Users mailing list archive at Nabble.com.

Re: Ignite Custom Java Code calling

2017-06-21 Thread ezhuravlev
Hi, It's not clear what you want to do. Why don't you just use simple sql queries? Why do you think that you need @QuerySQLFunction? Evgenii -- View this message in context: http://apache-ignite-users.70518.x6.nabble.com/Ignite-Custom-Java-Code-calling-tp13819p14032.html Sent from

Ignite Custom Java Code calling

2017-06-20 Thread abhishek dutta gupta
-ignite-users.70518.x6.nabble.com/Ignite-Custom-Java-Code-calling-tp13986.html Sent from the Apache Ignite Users mailing list archive at Nabble.com.

Re: Ignite Custom Java Code calling

2017-06-20 Thread abhishek dutta gupta
.nabble.com/Ignite-Custom-Java-Code-calling-tp13819p13984.html Sent from the Apache Ignite Users mailing list archive at Nabble.com.

Re: Ignite Custom Java Code calling

2017-06-19 Thread ezhuravlev
functions, then you should use @QuerySQLFunction. If you meant ForceServerMode for client nodes, then yes, your sql queries will be running only on server nodes, not on clients. Evgenii -- View this message in context: http://apache-ignite-users.70518.x6.nabble.com/Ignite-Custom-Java-Code-calling