Re: simple file based persistent store support TTL

Hi Val,do you mean that when cache is expired, I have to call cache.remove(key) manually in order to call delete in cachestore?I try to implement by remote listener like this:ignite.events().remoteListen(null, new IgnitePredicate(){ @IgniteInstanceResource private Ignite ignite;

Re: Ignite for fine-grained policy/quota control

I have considered using AtomicLong as well. But the main reason to introduce ignite lock is becuase the increaseAndGet() method should only be called after all the policies are allowed. Here is an example, when a message is allowed by Policy A(100 messages per user per day), but blocked by policy

Re: NOT IN in ignite

Hi Val, When two cache's require a join, collocation must be true in jdbc connection and then group by queries on individual caches will not return aggregated results. you mean this is not limitation ? if Yes, i am sorry, i may not agree on this :( in this case, to make sql queries work, two

Register CacheEvent Remote Listener

Hi,I want to only register listeners for cacheEvent, but I don't want to specify the particular cache.it is possible?like this code:ignite.events().remoteListen(null, new IgnitePredicate(){  } ThanksShawn

RE: Effective size limit for cache items in Ignite

I found this code snippet in the Ignite v1.8 source: This appears to be the core place where the value of CopyOnRead has an effect, though I don’t understand the context of the other logical conditions around it; it seems that CopyOnRead is dependent on other configuration state before it will

Re: restore Java Object from BinaryObject

My code error, BinaryObject deserialize twice. ThanksShawn On 02/11/2017 06:26，vkulichenko wrote： Shawn, What's the actual issue after you disabled compact footer? Exception?

Re: Ignite for fine-grained policy/quota control

Hi Evans, It sounds like you can simply use AtomicLong: https://apacheignite.readme.io/docs/atomic-types -Val -- View this message in context: http://apache-ignite-users.70518.x6.nabble.com/Ignite-for-fine-grained-policy-quota-control-tp10563p10584.html Sent from the Apache Ignite Users

Re: Unsubscribe the mailing list

Will do. Thanks. Sent from Bloomberg Professional for iPhone - Original Message - From: vkulichenko To: user@ignite.apache.org At: 12-Feb-2017 21:10:42 Tracy, You should write an email to user-unsubscr...@ignite.apache.org. It's a pity to see you going :)

Re: NOT IN in ignite

Anil, I don't see any limitations (except IGNITE-3860). Aggregation without collocation works properly and return correct result unless collected flag is set to true (doing so in this scenario is a misuse). As for performance, collocated execution will always be faster than non-collocated. That's

Re: Reduce Movement of data in cluster while data loading in PARTITIONED cache

That's correct. Partition aware data loading implies changing the database schema, but it's generally the fastest way to load the data. -Val -- View this message in context:

Re: Unsubscribe the mailing list

Tracy, You should write an email to user-unsubscr...@ignite.apache.org. It's a pity to see you going :) -Val -- View this message in context: http://apache-ignite-users.70518.x6.nabble.com/Unsubscribe-the-mailing-list-tp10574p10580.html Sent from the Apache Ignite Users mailing list archive

RE: Effective size limit for cache items in Ignite

Ah, I found the CopyOnRead flag in the cache configuration. Unfortunately, it seems to have the same behaviour regardless of the setting for this flag. If I create an example like the below, it seems that querying the same element from the cache many times takes about the same amount of time

Re: Reloading from Persistent Store after Losing a Node

Ah thank you. This is exactly what I was looking for! Thanks, Cody On Tue, Jan 31, 2017 at 8:07 AM, Vladimir Ozerov wrote: > Hi Cody, > > I think you can try using EventType.EVT_CACHE_REBALANCE_PART_DATA_LOST. It > is fired when data is lost. > > > > -- > View this

Grid Events and oldValue versus newValue

When updating entities in my cache, the oldValue=newValue in the event, unless I do a put with the original object instance. This is of course not always possible. Here is a simplified example. IgnitePredicate locLsnr = evt -> { // do something };

Effective size limit for cache items in Ignite

Hi, What is the practical size limit for items in an Ignite cache? I suspect the answer is something “As large as the memory you have to hold it”, but my question is more aimed at the practicality of large items in a cache due to the overhead of pulling copies of the items out of the cache

RE: Continuous reduce in Ignite

It turns out this annotation is also present in .Net and works the same way as the Java annotation. Eg: [Serializable] [ComputeTaskNoResultCache] class MyComputeTask : IComputeTask { } Sweet! :) -Original Message- From: vkulichenko

Unsubscribe the mailing list

Hey there, Could someone help me unsubscribe this sender email address from the Ignite mailing list. Thanks in advance! Tracy