Vyacheslav, Did you read initial discussion [1] about compression? As far as I remember we agreed to add only some "top-level" API in order to provide a way for Ignite users to inject some sort of custom compression.
[1] http://apache-ignite-developers.2346864.n4.nabble.com/Data-compression-in-Ignite-2-0-td10099.html On Mon, Apr 10, 2017 at 2:19 PM, daradurvs <[email protected]> wrote: > Hi Igniters! > > I am interested in this task. > Provide some kind of pluggable compression SPI support > <https://issues.apache.org/jira/browse/IGNITE-3592> > > I developed a solution on BinaryMarshaller-level, but reviewer has rejected > it. > > Let's continue discussion of task goals and solution design. > As I understood that, the main goal of this task is to store data in > compressed form. > This is what I need from Ignite as its user. Compression provides economy > on > servers. > We can store more data on same servers at the cost of increasing CPU > utilization. > > I'm researching a possibility of implementation of compression at the > cache-level. > > Any thoughts? > > -- > Best regards, > Vyacheslav > > > > > -- > View this message in context: http://apache-ignite- > developers.2346864.n4.nabble.com/Data-compression-in- > Ignite-2-0-tp10099p16317.html > Sent from the Apache Ignite Developers mailing list archive at Nabble.com. > -- Alexey Kuznetsov
