ignite.compute(ClusterGroup) is broken??

Hi, This is a continuation of this Thread, which has gone stale… http://apache-ignite-users.70518.x6.nabble.com/ComputeTask-is-including-Nodes-for-ComputeJobs-prematurely-td18185.html That Thread is concerned with Ignite sending ComputeJobs to Nodes prematurely. As suggested in that Thread, I

query operator in local node

Hi Igniters, Ignite 2.2, a couple of server nodes. I need to realize cache query operator only in local node or specific node, but I didn't found the related API in IgniteCache. I appreciate if you could give me a hint. -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: Web Console on Kubernetes Cluster

Hi, You may run agent on server node pods. Also you need pass user's security tokens: https://apacheignite-tools.readme.io/docs/getting-started#section-configuration -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Can the cache key and affinity key be different

Hi, I have two caches, A and B. They have their own pk as cache key. However, both of these caches are related to cache C by C's id. Is it possible to collocate them in same node by C's id? Please note, I will have to use their individual cache keys while doing get or put operation. C's id will be

Obtaining metadata about items in the cache

Hi, I’d like to be able to scan all the items in a cache where all I am interested in is the cache key and other metadata about the cached item (such as its size). I can do this now by running a cache query that simple reads out all the cache items, but this is a lot of IO when I don’t care

RE: Does the Ignite C# client support distributed queues?

Hi Pavel, Is there a document that captures all the current gaps? Thanks, Raymond. *From:* Pavel Tupitsyn [mailto:ptupit...@apache.org] *Sent:* Monday, December 4, 2017 6:27 AM *To:* user@ignite.apache.org *Cc:* d...@ignite.apache.org *Subject:* Re: Does the Ignite C# client support

Re: Does the Ignite C# client support distributed queues?

Hi Raymond, There is no exact schedule, but we always strive to keep .NET API up to speed with Java. Usually new features are added right in the same release (persistence in 2.1, for example). Pavel On Sat, Dec 2, 2017 at 9:51 AM, Raymond Wilson wrote: > Hi Alexey,