ignite-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Denis Magda <dma...@apache.org>
Subject Re: Ignite2.0 memory policy
Date Sat, 13 May 2017 17:31:15 GMT
> 3)Is ignite supports any compression?

There is a ticket for that. Probably it will be added in the nearest time.
https://issues.apache.org/jira/browse/IGNITE-3592 <https://issues.apache.org/jira/browse/IGNITE-3592>

In the meanwhile, you can use EntryProcessor API [1] compressing whole objects or individual
fields when onBeforePut method is called and decompress on onGet call. However, once the whole
object or a field is compressed you will no be able to query them with SQL. This is something
you have to pay for.

[1] CacheInterceptor <https://ignite.apache.org/releases/latest/javadoc/org/apache/ignite/cache/CacheInterceptor.html>

—
Denis

> On May 13, 2017, at 8:13 AM, Ajay <ajay.babu@6dtech.co.in> wrote:
> 
> Hi,
> 
> Please explain points
> 
> 1)How to add custom memory policy?
> 2)Can disable default memory policy?
> 3)Is ignite supports any compression?
> 
> Thanks 
> 
> 
> 
> --
> View this message in context: http://apache-ignite-users.70518.x6.nabble.com/Ignite2-0-memory-policy-tp12756.html
> Sent from the Apache Ignite Users mailing list archive at Nabble.com.


Mime
View raw message