yet created) with some predefined expiration policy in order to be
able to>
> set the expiration timeout for key/value pair put into Ignite.>
>
> Looks like you are referring to>
> https://apacheignite.readme.io/docs/partition-loss-policies,>
> while I'm interes
Yes, it's my fault. I double check the list of existed options and looks like
there is no expire policy option there.
I see that exists PROP_EAGER_TTL property:
https://apacheignite.readme.io/docs/expiry-policies#section-eager-ttl
But there are no options for expiration policies.
Let me some t
Hi,
Are we talking about the same? I mean, my goal is to create a cache (if not
yet created) with some predefined expiration policy in order to be able to
set the expiration timeout for key/value pair put into Ignite.
Looks like you are referring to
https://apacheignite.readme.io/docs/partition
Hi,
Yes, it should be possible. Please read the documentation from binaries:
https://github.com/apache/ignite/blob/master/modules/platforms/python/docs/datatypes/cache_props.rst
PROP_PARTITION_LOSS_POLICY:
Partition loss policy: READ_ONLY_SAFE=0, READ_ONLY_ALL=1, READ_WRITE_SAFE=2,
READ_WRITE_A
Hello all,
I'm wondering whether it's possible to create a cache with expiration
policy <https://apacheignite.readme.io/docs/expiry-policies> defined from
Python client?
Documentation says nothing about this.
Thank you in advance.
--
Sent from: http://apache-ignit
Hi Anmol,
You statements are correct.
On Sep 3, 2016 05:02, "Anmol Rattan" wrote:
> Hi,
>
> Wanted to understand difference between expiration policy and eviction.
>
> 1. Expiration is a time base policy which will remove entry from cache
> older than configured tim
Hi,
Wanted to understand difference between expiration policy and eviction.
1. Expiration is a time base policy which will remove entry from cache
older than configured time duration. And will it only remove from cache and
would not invoke purge of cachestore (which may delete from backing
