Ignite for fine-grained policy/quota control

Hi Igniters, We recently are using Ignite building a real-time notification system. Ignite plays a crucial part on policy control for notifications. For example, we would like a user who has a quota of 100 notifications per day gets 100 messages per day precisely. Once quota exceeded, Further

Re: NOT IN in ignite

Hi Val, Do you guys accept this behavior as bug ? correct it so that group by with non affinity key returns same results with/without collocated true ? Thanks. On 9 February 2017 at 09:40, Anil wrote: > Hi Val, > > You are right. i collocated the data and set the

Ignite client connections hanged

IgniteCluster.jpg Hi, I have Ignite and Web applications deployment as shown in the attached image. I added couple of new functions to

Re: Continuous reduce in Ignite

Hi Val, This would be from .Net. Is there an option for extending the .Net client to support this? Thanks, Raymond. Sent from my iPhone > On 11/02/2017, at 11:19 AM, vkulichenko wrote: > > Hi Raymond, > > Are you implementing tasks in Java or .NET? For Java

Re: Help needed

Ranjit, I would recommend you to start a standalone Ignite cluster, separate from Spark. You may also need to specify clientMode=true in the configuration provided to IgniteContext, to make sure that nodes on executors are clients, not servers. -Val -- View this message in context:

Re: loadCache with ExpiryPolicy

Hi, When done right, expiry policy provided in CacheConfiguration must be applied to entries loaded from store. However there was an issue that was fixed recently (not released yet): https://issues.apache.org/jira/browse/IGNITE-3699 As for NPE, not sure why this happens. What is null there?

Re: restore Java Object from BinaryObject

Shawn, What's the actual issue after you disabled compact footer? Exception? Incorrect behavior? -Val -- View this message in context: http://apache-ignite-users.70518.x6.nabble.com/restore-Java-Object-from-BinaryObject-tp10525p10556.html Sent from the Apache Ignite Users mailing list

Re: Can continuousAsyncQuery guarantee event to be processed in order?

Yes, it does. -Val -- View this message in context: http://apache-ignite-users.70518.x6.nabble.com/Can-continuousAsyncQuery-guarantee-event-to-be-processed-in-order-tp10521p10555.html Sent from the Apache Ignite Users mailing list archive at Nabble.com.

Re: Bug with using Map as a cache key in Ignite

Responded on StackOverflow: http://stackoverflow.com/questions/42161278/bug-using-map-as-a-cache-key-in-ignite -Val -- View this message in context: http://apache-ignite-users.70518.x6.nabble.com/Bug-with-using-Map-as-a-cache-key-in-Ignite-tp10549p10554.html Sent from the Apache Ignite Users

Re: Continuous reduce in Ignite

Hi Raymond, Are you implementing tasks in Java or .NET? For Java there is a special @ComputeTaskNoResultCache annotation that prevents from caching all job results in a single collection. Not sure there is such an option for .NET though. -Val -- View this message in context:

Bug with using Map as a cache key in Ignite

Hi GridGain/Ignite guys, I've recently encountered a bug while using Ignite. The scenario is as follows:I have a class *A* that just has a *java.util.Map* field that I am using as an ignite cache key to map to some value. I have 2 instances of the same service: *S1* & *S2* , each running an

Re: EntryProcessor for cache

and Does compute task execute in parallel on number of partitions per node ? (like entry processor) thanks. On 10 February 2017 at 10:52, Anil wrote: > Hi Val, > > i have attached the code. please let me know if you see any issues with > approach. thanks. > > Thanks. > > On

Re: Can continuousAsyncQuery guarantee event to be processed in order?

Does what you said "notification guarantees" mean "exactly once delivery of an event"? Does it also mean "keep the order of the events"? -- View this message in context:

Re: Help needed

Hi Jorn, The use case what we are working on is something like this. We have three functions, one to extractEntity, one to resolve and to resolve we need an accesor. So first we build a RDD calling extract function in Step 1 below. Next we prepare the look up RDD and lets call it as Accesor.

Re: Help needed

Hi Jorn, The use case what we are working on is something like this. We have three functions, one to extractEntity, one to resolve and to resolve we need an accesor. So first we build a RDD calling extract function in Step 1 below. Next we prepare the look up RDD and lets call it as Accesor.