Dmitriy, I'm researching a best way for this future.
At the moment I found only one way (querying and indexing compatible), this is per-objects-field compression. But there is a good proffit only for long strings or fields with large objects. Maybe it makes sense just to introduce compression for string fileds. I'm researching the new page-memory architecture as applied to by-page compression. 2017-05-11 11:30 GMT+03:00 Dmitriy Setrakyan <dsetrak...@apache.org>: > On Thu, May 11, 2017 at 12:44 AM, Vyacheslav Daradur <daradu...@gmail.com> > wrote: > > > Denis, > > > > The described roadmap looks great! > > > > Additional, I vote for introducing an ability (OOTB) to store objects in > a > > cache in a compressed form. > > This will allow to store more data at the cost of incriasing of CPU > > utilization. > > > > One of the problems with compression is indexing and querying. How do we > index the data if it is compressed? > > > > > > > > 2017-05-11 4:23 GMT+03:00 Denis Magda <dma...@apache.org>: > > > > > Igniters, > > > > > > Let me start a discussion around the scope for 2.1 release. > > > > > > In my vision the main direction of our ongoing efforts should be > > > implementing in life a use case of Ignite as a transactional > distributed > > > SQL database and HTAP platform. The current use cases (database cache, > > data > > > grid, micro services platform, etc.) will be supported as usual, no > > changes > > > on that frontier. > > > > > > Keeping this in mind, the roadmap needs to include essential SQL > related > > > features as well as disk based capabilities, MVCC support, advanced DDL > > > implementation and so on so forth. This is for Ignite as a SQL > database. > > > > > > Next, Machine Learning will be a great addition to Ignite as an HTAP > > > platform offering. This is why we should keep investing our time and > > > resources in that recently released component. > > > > > > Having this said, I see the scope for 2.1 release this way: > > > > > > 1. Distributed Persistent Store - if the donation is accepted by ASF. > The > > > decision is to be done in separate discussion. W/o the store > > > Ignite can only be used as In-Memory SQL database. > > > > > > 2. SQL Grid: > > > - CREATE & DROP table commands: https://issues.apache.org/ > > > jira/browse/IGNITE-4651 > > > - Renewed JDBC driver: https://issues.apache.org/ > > > jira/browse/IGNITE-4922 > > > - Collocation based routing of SQL queries: > > https://issues.apache.org/ > > > jira/browse/IGNITE-4510, > > > https://issues.apache.org/jira/browse/IGNITE-4509 > > > - > > > > > > 3. .NET: > > > - Peer-class loading: https://issues.apache.org/ > > > jira/browse/IGNITE-2492 > > > - SQLDependency: https://issues.apache.org/jira/browse/IGNITE-2657 > > > > > > 4. C++: > > > - Compute Grid: https://issues.apache.org/jira/browse/IGNITE-3574 > > > > > > 5. ML Grid: > > > - Linear regression algorithms: https://issues.apache.org/ > > > jira/browse/IGNITE-5012 > > > - K-means clustering: https://issues.apache.org/ > > > jira/browse/IGNITE-5113 > > > > > > > > > Please join the thread and share your thoughts, ideas and concerns. > > > > > > — > > > Denis > > > > > > > > > > > > > > > > > > > -- > > Best Regards, Vyacheslav > > > -- Best Regards, Vyacheslav
