The Apache Software Foundation
The Apache Software Foundation Incubator

Ignite Persistent Store Codebase Intellectual Property (IP) Clearance Status


The donated persistent store is a distributed and transactional disk storage that seamlessly integrates with Apache Ignite 2.0 page memory architecture. One of the main advantages of the store is that Apache Ignite becomes a fully operational from disk (SSD or Flash) without any need to preload the data in memory. Plus, with full SQL support already available in Apache Ignite, this feature will allow Apache Ignite serve as a distributed transactional database, both in memory and on disk, while continuing to support all the existing use cases.
Refer to these wiki pages for more details:

Project info

  • Apache Ignite PMC will be responsible for the code.
  • The persistent store will be added under "pds" and "core" modules.
  • Officer or member managing donation: Denis Magda (Apache Ignite PMC Chair)

Completed tasks are shown by the completion date (YYYY-MM-dd).

Identify the codebase

date item
2017-05-12 Branch:
MD5 or SHA1 sum for donated software: MD5 ( = 10c87c969cd836deb94172db384039f6 (md5 tool from Mac OS).
2017-05-22 The persistent store code base was committed to Apache Ignite repository's branch:
2017-06-16 The persistent store code base was moved to the different branch due to a variety of changes. The "pds" module is discontinued - all the codebase merged to "ignite-core" component:
date item
2017-05-13 Check and make sure that the papers that transfer rights to the ASF been received. It is only necessary to transfer rights for the package, the core code, and any new code produced by the project.
2017-05-16 Check and make sure that the files that have been donated have been updated to reflect the new ASF copyright.

Identify name recorded for software grant: Ignite Persistent Store

Verify distribution rights

Corporations and individuals holding existing distribution rights:

  • GridGain Systems, Inc.
date item
2017-05-12 Check that all active committers have a signed CLA on record.
2017-05-12 Remind active committers that they are responsible for ensuring that a Corporate CLA is recorded if such is required to authorize their contributions under their individual CLA.
2017-05-12 Check and make sure that for all items included with the distribution that is not under the Apache license, we have the right to combine with Apache-licensed code and redistribute.
2017-05-12 Check and make sure that all items depended upon by the project is covered by one or more of the following approved licenses: Apache, BSD, Artistic, MIT/X, MIT/W3C, MPL 1.1, or something with essentially the same terms.

Generally, the result of checking off these items will be a Software Grant, CLA, and Corporate CLA for ASF licensed code, which must have no dependencies upon items whose licenses that are incompatible with the Apache License.

Organizational acceptance of responsibility for the project