On Mon, Apr 17, 2017 at 7:37 PM, Denis Magda <dma...@apache.org> wrote: > Igniters, > > GridGain, as one of the most active Apache Ignite contributors, has been > developing a unique distributed persistent store specifically for Apache > Ignite for more than a year in-house. It’s a fully ACID and ANSI-99 SQL > compliant fault-tolerant solution. > > The store transparently integrates with Apache Ignite as an optional disk > layer (in addition to the existing RAM layer) via the new page memory > architecture that to be released in Apache Ignite 2.0. This allows storing > supersets of data on disk while having a subset in memory not worrying about > that you forgot to preload (warmup) your caches! > > Assuming that the storage goes to ASF as a part of Apache Ignite 2.1 release > the following will be supported by Ignite out-of-the-box: > > * SQL queries execution over the data that is both in RAM and on disk: no > need to preload the whole data set in memory. > > * Cluster instantaneous restarts: once your cluster ring is recovered after a > restart your applications are fully operational even if they highly utilize > SQL queries. > > As for the use cases, it means that Apache Ignite will be possible to use as > a distributed SQL database with memory-first concept. > > And we decided at GridGain that this tremendous feature should be open source > from the very beginning. > > Guys, could you advise how I can start official donation process?
First of all, it really isn't a good thing that a major functionality was developed behind the firewall without any feedback from Apache Ignite community. So the first question I'd like to ask is this: what was the reason for this to be developed in such a way (and a follow up -- how can this be avoided in the future)? In my experience the only excuse for something like that is either a work that was done before the project joined ASF or work that was done under the draconian initial license agreement that can now be re-licensed under ASF. Which brings me to my next point: any addition to the project that doesn't go through the normal channels of small reversible commits that are easy to scrutinize for IP issues needs to be vetted. Depending on the size of the donation a separate SGA for ASF may be required. Which brings me to my last point: where's the code? In order to have a factual conversation about the next steps in the process I'd like to be able to take a look at the code available to me under the Apache License. On top of which, I would like to either have a full access to the commit and authorship history of this code OR a statement from the current overall copyright owner. Please make it available and post the URL to this thread. Then we can discuss the next steps. Thanks, Roman (wearing his ASF member hat).
