Re: Issue IGNITE-3471

Hi, Yes, for complex transaction this workaround will not work. So you need either wait for fix or avoid using EntryProcessor for now. Thanks! -Dmitry -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: Effective Data through DataStream

Hi, Could you please provide your code example, configuration and used Ignite version? Thank you, Andrei -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: Roadmap, especially TensorFlow integration

Hi Dennis, Yes, we will have this integration. You clould check this issue for more details. We expect the first implementation of this integration after implementation of Python Thin Client

Re: Inconsistency reading cache from code and via REST?

Hi Andrei I simpler workaround for me for now is just to have keys a strings so REST A few toString() tweaks to the sample code to put/get as strings instead of integers shows this now works as expected both checking the cache in code and from a browser. thanks Michael -- Sent from:

Re: How to start Ignite with a jar built from the source code

Hi, In source code we have DEVNOTES.txt that contains the information how to build ignite. I believe that next steps could help you: 1)git clone https://git-wip-us.apache.org/repos/asf/ignite.git 2)Update your source code. 3)Build ignite as described from DEVNOTES.txt: 1.Compile and install:

connection pool in ignite

Hi,Is there connection pool concept in ignite client?I notice there are only one TCP connection between my ignite client and server.Currently I don't find any issues with it, but please explain.If a client communicate(put/get/query) with server heavily, does one connection is

Re: Which ports does ignite cluster need to run normally?

what about UDP ports? what they are used for in Ignite? On Thu, Apr 19, 2018 at 10:40 PM, vkulichenko wrote: > Most of these seem to ephemeral ports assigned to discovery and > communication > clients when they connect to well known configured ports on server

Re: Running heavy queries on Ignite cluster on backing store directly without impacting the cluster

HI Andrey The reason I was trying to explore this feature is, I will give you an example. I have a cache with 20M records and when I run this query SELECT * FROM "AssociatedPartiesCache".ASSOCIATED_PARTIES Query took more than 200 secs and ran out of memory, here is the error thrown This I

Missing shu is a cross-cache associated query.

My ignite configuration file looks something like this.