You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@ignite.apache.org by am...@apache.org on 2019/05/07 15:21:10 UTC
[ignite] 02/41: "README.md", "README.txt", "NOTICE_HADOOP",
"NOTICE_IGNITE", "LICENSE", "NOTICE", "LICENSE_HADOOP", "LICENSE_IGNITE"
This is an automated email from the ASF dual-hosted git repository.
amashenkov pushed a commit to branch gg-18540
in repository https://gitbox.apache.org/repos/asf/ignite.git
commit b33f3d2ba43ec1a636ddaa1a44ae232842cbfb8b
Author: mstepachev <ma...@gmail.com>
AuthorDate: Thu Apr 18 14:45:36 2019 +0300
"README.md", "README.txt", "NOTICE_HADOOP", "NOTICE_IGNITE", "LICENSE", "NOTICE", "LICENSE_HADOOP", "LICENSE_IGNITE"
---
LICENSE | 213 +-------------
NOTICE | 4 +-
README.md | 170 +++++------
README.txt | 22 +-
assembly/LICENSE_HADOOP | 264 +----------------
assembly/LICENSE_IGNITE | 311 +--------------------
assembly/NOTICE_HADOOP | 4 +-
assembly/NOTICE_IGNITE | 4 +-
assembly/libs/README.txt | 46 +--
docker/apache-ignite/README.txt | 12 +-
docker/web-agent/README.txt | 11 +-
docker/web-console/standalone/README.txt | 10 +-
examples/README.md | 14 +-
examples/README.txt | 21 +-
examples/config/filesystem/README.txt | 2 +-
examples/config/hibernate/README.txt | 2 +-
examples/config/servlet/README.txt | 2 +-
ipc/README.txt | 4 +-
ipc/shmem/README.txt | 8 +-
modules/aop/README.txt | 8 +-
modules/apache-license-gen/README.txt | 10 +-
modules/aws/README.txt | 8 +-
modules/camel/README.txt | 8 +-
modules/cassandra/README.txt | 8 +-
modules/cassandra/serializers/README.txt | 10 +-
modules/cassandra/store/README.txt | 8 +-
.../store/src/test/bootstrap/aws/README.txt | 4 +-
modules/clients/README.txt | 6 +-
modules/cloud/README.txt | 8 +-
modules/compatibility/README.txt | 4 +-
modules/core/src/main/java/META-INF/LICENSE | 245 +---------------
modules/core/src/main/java/META-INF/NOTICE | 4 +-
modules/dev-utils/README.txt | 4 +-
modules/direct-io/README.txt | 16 +-
modules/extdata/platform/README.txt | 2 +-
modules/flink/README.txt | 14 +-
modules/flume/README.txt | 10 +-
modules/gce/README.txt | 8 +-
modules/geospatial/README.txt | 16 +-
modules/hadoop/README.txt | 8 +-
modules/hibernate-4.2/README.txt | 16 +-
modules/hibernate-5.1/README.txt | 16 +-
modules/ignored-tests/README.txt | 2 +-
modules/indexing/README.txt | 8 +-
modules/jcl/README.txt | 8 +-
modules/jms11/README.txt | 12 +-
modules/jta/README.txt | 8 +-
modules/kafka/README.txt | 20 +-
modules/kubernetes/README.txt | 10 +-
modules/log4j/README.txt | 8 +-
modules/log4j2/README.txt | 8 +-
modules/mesos/README.txt | 10 +-
modules/ml/README.txt | 8 +-
modules/mqtt/README.txt | 12 +-
modules/osgi-karaf/README.txt | 12 +-
modules/osgi-paxlogging/README.txt | 2 +-
modules/osgi/README.txt | 14 +-
modules/platforms/README.txt | 6 +-
modules/platforms/cpp/README.md | 193 +++++++------
modules/platforms/cpp/README.txt | 36 +--
modules/platforms/cpp/examples/README.txt | 14 +-
modules/platforms/cpp/odbc/README.txt | 18 +-
modules/platforms/dotnet/README.md | 163 ++++-------
modules/platforms/dotnet/README.txt | 20 +-
modules/platforms/dotnet/docfx/README.txt | 2 +-
modules/platforms/dotnet/examples/README.txt | 2 +-
.../dotnet/examples/dotnetcore/README.txt | 2 +-
modules/platforms/nodejs/README.md | 4 +-
modules/platforms/php/README.md | 4 +-
modules/platforms/python/LICENSE | 209 +-------------
modules/rest-http/README.txt | 8 +-
modules/rocketmq/README.txt | 8 +-
modules/scalar-2.10/README.txt | 4 +-
modules/scalar/README.txt | 8 +-
modules/schedule/README.txt | 14 +-
modules/slf4j/README.txt | 8 +-
modules/spark/README.txt | 8 +-
modules/spring-data-2.0/README.txt | 8 +-
modules/spring-data/README.txt | 6 +-
modules/spring/README.txt | 8 +-
modules/ssh/README.txt | 8 +-
modules/storm/README.txt | 14 +-
modules/tensorflow/README.txt | 26 +-
modules/twitter/README.txt | 10 +-
modules/urideploy/README.txt | 8 +-
modules/visor-console-2.10/README.txt | 4 +-
modules/web-console/README.txt | 10 +-
modules/web-console/assembly/README.txt | 2 +-
modules/web-console/web-agent/README.txt | 16 +-
modules/web/README.txt | 12 +-
modules/yardstick/README.txt | 22 +-
modules/yarn/README.txt | 10 +-
modules/zeromq/README.txt | 14 +-
modules/zookeeper/README.txt | 12 +-
94 files changed, 700 insertions(+), 1928 deletions(-)
diff --git a/LICENSE b/LICENSE
index 6e77825..86ca9b6 100644
--- a/LICENSE
+++ b/LICENSE
@@ -1,212 +1,23 @@
+Copyright 2019 GridGain Systems, Inc. and Contributors.
- Apache License
- Version 2.0, January 2004
- http://www.apache.org/licenses/
+Licensed under the GridGain Community Edition License (the "License");
+you may not use this file except in compliance with the License.
+You may obtain a copy of the License at
- TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+ https://www.gridgain.com/products/software/community-edition/gridgain-community-edition-license
- 1. Definitions.
-
- "License" shall mean the terms and conditions for use, reproduction,
- and distribution as defined by Sections 1 through 9 of this document.
-
- "Licensor" shall mean the copyright owner or entity authorized by
- the copyright owner that is granting the License.
-
- "Legal Entity" shall mean the union of the acting entity and all
- other entities that control, are controlled by, or are under common
- control with that entity. For the purposes of this definition,
- "control" means (i) the power, direct or indirect, to cause the
- direction or management of such entity, whether by contract or
- otherwise, or (ii) ownership of fifty percent (50%) or more of the
- outstanding shares, or (iii) beneficial ownership of such entity.
-
- "You" (or "Your") shall mean an individual or Legal Entity
- exercising permissions granted by this License.
-
- "Source" form shall mean the preferred form for making modifications,
- including but not limited to software source code, documentation
- source, and configuration files.
-
- "Object" form shall mean any form resulting from mechanical
- transformation or translation of a Source form, including but
- not limited to compiled object code, generated documentation,
- and conversions to other media types.
-
- "Work" shall mean the work of authorship, whether in Source or
- Object form, made available under the License, as indicated by a
- copyright notice that is included in or attached to the work
- (an example is provided in the Appendix below).
-
- "Derivative Works" shall mean any work, whether in Source or Object
- form, that is based on (or derived from) the Work and for which the
- editorial revisions, annotations, elaborations, or other modifications
- represent, as a whole, an original work of authorship. For the purposes
- of this License, Derivative Works shall not include works that remain
- separable from, or merely link (or bind by name) to the interfaces of,
- the Work and Derivative Works thereof.
-
- "Contribution" shall mean any work of authorship, including
- the original version of the Work and any modifications or additions
- to that Work or Derivative Works thereof, that is intentionally
- submitted to Licensor for inclusion in the Work by the copyright owner
- or by an individual or Legal Entity authorized to submit on behalf of
- the copyright owner. For the purposes of this definition, "submitted"
- means any form of electronic, verbal, or written communication sent
- to the Licensor or its representatives, including but not limited to
- communication on electronic mailing lists, source code control systems,
- and issue tracking systems that are managed by, or on behalf of, the
- Licensor for the purpose of discussing and improving the Work, but
- excluding communication that is conspicuously marked or otherwise
- designated in writing by the copyright owner as "Not a Contribution."
-
- "Contributor" shall mean Licensor and any individual or Legal Entity
- on behalf of whom a Contribution has been received by Licensor and
- subsequently incorporated within the Work.
-
- 2. Grant of Copyright License. Subject to the terms and conditions of
- this License, each Contributor hereby grants to You a perpetual,
- worldwide, non-exclusive, no-charge, royalty-free, irrevocable
- copyright license to reproduce, prepare Derivative Works of,
- publicly display, publicly perform, sublicense, and distribute the
- Work and such Derivative Works in Source or Object form.
-
- 3. Grant of Patent License. Subject to the terms and conditions of
- this License, each Contributor hereby grants to You a perpetual,
- worldwide, non-exclusive, no-charge, royalty-free, irrevocable
- (except as stated in this section) patent license to make, have made,
- use, offer to sell, sell, import, and otherwise transfer the Work,
- where such license applies only to those patent claims licensable
- by such Contributor that are necessarily infringed by their
- Contribution(s) alone or by combination of their Contribution(s)
- with the Work to which such Contribution(s) was submitted. If You
- institute patent litigation against any entity (including a
- cross-claim or counterclaim in a lawsuit) alleging that the Work
- or a Contribution incorporated within the Work constitutes direct
- or contributory patent infringement, then any patent licenses
- granted to You under this License for that Work shall terminate
- as of the date such litigation is filed.
-
- 4. Redistribution. You may reproduce and distribute copies of the
- Work or Derivative Works thereof in any medium, with or without
- modifications, and in Source or Object form, provided that You
- meet the following conditions:
-
- (a) You must give any other recipients of the Work or
- Derivative Works a copy of this License; and
-
- (b) You must cause any modified files to carry prominent notices
- stating that You changed the files; and
-
- (c) You must retain, in the Source form of any Derivative Works
- that You distribute, all copyright, patent, trademark, and
- attribution notices from the Source form of the Work,
- excluding those notices that do not pertain to any part of
- the Derivative Works; and
-
- (d) If the Work includes a "NOTICE" text file as part of its
- distribution, then any Derivative Works that You distribute must
- include a readable copy of the attribution notices contained
- within such NOTICE file, excluding those notices that do not
- pertain to any part of the Derivative Works, in at least one
- of the following places: within a NOTICE text file distributed
- as part of the Derivative Works; within the Source form or
- documentation, if provided along with the Derivative Works; or,
- within a display generated by the Derivative Works, if and
- wherever such third-party notices normally appear. The contents
- of the NOTICE file are for informational purposes only and
- do not modify the License. You may add Your own attribution
- notices within Derivative Works that You distribute, alongside
- or as an addendum to the NOTICE text from the Work, provided
- that such additional attribution notices cannot be construed
- as modifying the License.
-
- You may add Your own copyright statement to Your modifications and
- may provide additional or different license terms and conditions
- for use, reproduction, or distribution of Your modifications, or
- for any such Derivative Works as a whole, provided Your use,
- reproduction, and distribution of the Work otherwise complies with
- the conditions stated in this License.
-
- 5. Submission of Contributions. Unless You explicitly state otherwise,
- any Contribution intentionally submitted for inclusion in the Work
- by You to the Licensor shall be under the terms and conditions of
- this License, without any additional terms or conditions.
- Notwithstanding the above, nothing herein shall supersede or modify
- the terms of any separate license agreement you may have executed
- with Licensor regarding such Contributions.
-
- 6. Trademarks. This License does not grant permission to use the trade
- names, trademarks, service marks, or product names of the Licensor,
- except as required for reasonable and customary use in describing the
- origin of the Work and reproducing the content of the NOTICE file.
-
- 7. Disclaimer of Warranty. Unless required by applicable law or
- agreed to in writing, Licensor provides the Work (and each
- Contributor provides its Contributions) on an "AS IS" BASIS,
- WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
- implied, including, without limitation, any warranties or conditions
- of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
- PARTICULAR PURPOSE. You are solely responsible for determining the
- appropriateness of using or redistributing the Work and assume any
- risks associated with Your exercise of permissions under this License.
-
- 8. Limitation of Liability. In no event and under no legal theory,
- whether in tort (including negligence), contract, or otherwise,
- unless required by applicable law (such as deliberate and grossly
- negligent acts) or agreed to in writing, shall any Contributor be
- liable to You for damages, including any direct, indirect, special,
- incidental, or consequential damages of any character arising as a
- result of this License or out of the use or inability to use the
- Work (including but not limited to damages for loss of goodwill,
- work stoppage, computer failure or malfunction, or any and all
- other commercial damages or losses), even if such Contributor
- has been advised of the possibility of such damages.
-
- 9. Accepting Warranty or Additional Liability. While redistributing
- the Work or Derivative Works thereof, You may choose to offer,
- and charge a fee for, acceptance of support, warranty, indemnity,
- or other liability obligations and/or rights consistent with this
- License. However, in accepting such obligations, You may act only
- on Your own behalf and on Your sole responsibility, not on behalf
- of any other Contributor, and only if You agree to indemnify,
- defend, and hold each Contributor harmless for any liability
- incurred by, or claims asserted against, such Contributor by reason
- of your accepting any such warranty or additional liability.
-
- END OF TERMS AND CONDITIONS
-
- APPENDIX: How to apply the Apache License to your work.
-
- To apply the Apache License to your work, attach the following
- boilerplate notice, with the fields enclosed by brackets "[]"
- replaced with your own identifying information. (Don't include
- the brackets!) The text should be enclosed in the appropriate
- comment syntax for the file format. We also recommend that a
- file or class name and description of purpose be included on the
- same "printed page" as the copyright notice for easier
- identification within third-party archives.
-
- Copyright [yyyy] [name of copyright owner]
-
- Licensed under the Apache License, Version 2.0 (the "License");
- you may not use this file except in compliance with the License.
- You may obtain a copy of the License at
-
- http://www.apache.org/licenses/LICENSE-2.0
-
- Unless required by applicable law or agreed to in writing, software
- distributed under the License is distributed on an "AS IS" BASIS,
- WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
- See the License for the specific language governing permissions and
- limitations under the License.
+Unless required by applicable law or agreed to in writing, software
+distributed under the License is distributed on an "AS IS" BASIS,
+WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+See the License for the specific language governing permissions and
+limitations under the License.
==============================================================================
-Apache Ignite Subcomponents:
+GridGain Subcomponents:
-The Apache Ignite project contains subcomponents with separate copyright
+The GridGain project contains subcomponents with separate copyright
notices and license terms. Your use of the source code for the these
subcomponents is subject to the terms and conditions of the following
licenses.
diff --git a/NOTICE b/NOTICE
index 0bae434..62c5414 100644
--- a/NOTICE
+++ b/NOTICE
@@ -1,5 +1,5 @@
-Apache Ignite
-Copyright 2019 The Apache Software Foundation
+GridGain
+Copyright 2019 GridGain Systems
This product includes software developed at
The Apache Software Foundation (http://www.apache.org/).
diff --git a/README.md b/README.md
index 89af2ca..ccedf78 100644
--- a/README.md
+++ b/README.md
@@ -1,54 +1,55 @@
-# Apache Ignite
+# GridGain Community Edition
-<a href="https://ignite.apache.org/"><img src="https://ignite.apache.org/images/logo3.png" hspace="20"/></a>
+<a href="https://www.gridgain.com/"><img src="https://www.gridgain.com/themes/gridgain1185/images/svg/gridgain-logo.svg?20180912" hspace="10" width="300px"/></a><br/><br/>
-<a href="https://ci.ignite.apache.org/viewType.html?buildTypeId=IgniteTests24Java8_RunAll&branch_IgniteTests24Java8=%3Cdefault%3E"><img src="https://ci.ignite.apache.org/app/rest/builds/buildType:(id:IgniteTests24Java8_RunAll)/statusIcon.svg"/></a>
+The [GridGain][GridGain-homepage] Community Edition (GCE) is a source-available in-memory computing platform built on Apache Ignite.
+GCE includes the [Apache Ignite][apache-ignite-homepage] code base plus improvements and additional functionality developed by GridGain Systems
+to enhance the performance and reliability of Apache Ignite. GCE is a hardened, high-performance version of Apache Ignite
+for mission-critical in-memory computing applications.
-## Getting Started
-For information on how to get started with Apache Ignite, please visit: [Getting Started][getting-started].
-## Full Documentation
+## Getting Started
-You can find the full Apache Ignite documentation here: [Full documentation][docs].
+For information on how to get started with GridGain CE, please visit: [Getting Started][getting-started].
-## What is Apache Ignite?
+## What is GridGain?
-[Apache Ignite][apache-ignite-homepage] is a memory-centric distributed <strong>database</strong>, <strong>caching</strong>,
- and <strong>processing</strong> platform for transactional, analytical, and streaming workloads delivering in-memory
+GridGain, built on top of Apache Ignite, is a memory-centric distributed **database**, **caching**,
+ and **processing** platform for transactional, analytical, and streaming workloads delivering in-memory
speeds at petabyte scale.
<p align="center">
- <a href="https://ignite.apache.org/whatisignite.html">
- <img src="https://ignite.apache.org/images/ignite_architecture.png" width="400px"/>
+ <a href="https://www.gridgain.com/">
+ <img src="https://files.readme.io/58b7901-gg_platform.png" width="600px"/>
</a>
</p>
## Memory-Centric Storage
-Apache Ignite is based on distributed memory-centric architecture that combines the performance and scale of in-memory
+GridGain is based on distributed memory-centric architecture that combines the performance and scale of in-memory
computing together with the disk durability and strong consistency in one system.
The main difference between the memory-centric approach and the traditional disk-centric approach is that the memory
is treated as a fully functional storage, not just as a caching layer, like most databases do.
-For example, Apache Ignite can function in a pure in-memory mode, in which case it can be treated as an
+For example, GridGain can function in a pure in-memory mode, in which case it can be treated as an
In-Memory Database (IMDB) and In-Memory Data Grid (IMDG) in one.
-On the other hand, when persistence is turned on, Ignite begins to function as a memory-centric system where most of
+On the other hand, when persistence is turned on, GidGain begins to function as a memory-centric system where most of
the processing happens in memory, but the data and indexes get persisted to disk. The main difference here
-from the traditional disk-centric RDBMS or NoSQL system is that Ignite is strongly consistent, horizontally
+from the traditional disk-centric RDBMS or NoSQL system is that GridGain is strongly consistent, horizontally
scalable, and supports both SQL and key-value processing APIs.
[Read More](https://ignite.apache.org/arch/memorycentric.html)
-## Ignite Persistence
+## Native Persistence
-Ignite Native Persistence is a distributed, ACID, and SQL-compliant **disk store** that transparently integrates with
-Ignite memory-centric storage as an optional disk layer storing data and indexes on SSD,
+Native Persistence is a distributed, ACID, and SQL-compliant **disk store** that transparently integrates with
+GridGain memory-centric storage as an optional disk layer storing data and indexes on SSD,
Flash, 3D XPoint, and other types of non-volatile storages.
-With the Ignite Persistence enabled, you no longer need to keep all the data and indexes in memory or warm it
+With the Native Persistence enabled, you no longer need to keep all the data and indexes in memory or warm it
up after a node or cluster restart because the Durable Memory is tightly coupled with persistence and treats
it as a secondary memory tier. This implies that if a subset of data or an index is missing in RAM,
the Durable Memory will take it from the disk.
@@ -62,33 +63,33 @@ the Durable Memory will take it from the disk.
[Read More](https://ignite.apache.org/arch/persistence.html)
## ACID Compliance
-Data stored in Ignite is ACID-compliant both in memory and on disk, making Ignite a **strongly consistent** system. Ignite transactions work across the network and can span multiple servers.
+Data stored in GridGain is ACID-compliant both in memory and on disk, making GridGain a **strongly consistent** system. GridGain transactions work across the network and can span multiple servers.
[Read More](https://apacheignite.readme.io/docs/transactions)
## Complete SQL Support
-Ignite provides full support for SQL, DDL and DML, allowing users to interact with Ignite using pure SQL without writing any code. This means that users can create tables and indexes as well as insert, update, and query data using only SQL. Having such complete SQL support makes Ignite a one-of-a-kind **distributed SQL database**.
+GridGain provides full support for SQL, DDL and DML, allowing users to interact with the cluster using pure SQL without writing any code. This means that users can create tables and indexes as well as insert, update, and query data using only SQL. Having such complete SQL support makes GridGain a one-of-a-kind **distributed SQL database**.
[Read More](https://apacheignite.readme.io/docs/distributed-sql)
## Key-Value
-The in-memory data grid component in Ignite is a fully transactional **distributed key-value store** that can scale horizontally across 100s of servers in the cluster. When persistence is enabled, Ignite can also store more data than fits in memory and survive full cluster restarts.
+The in-memory data grid component in GridGain is a fully transactional **distributed key-value store** that can scale horizontally across 100s of servers in the cluster. When persistence is enabled, GridGain can also store more data than fits in memory and survive full cluster restarts.
[Read More](https://apacheignite.readme.io/docs/data-grid)
## Collocated Processing
-Most traditional databases work in a client-server fashion, meaning that data must be brought to the client side for processing. This approach requires lots of data movement from servers to clients and generally does not scale. Ignite, on the other hand, allows for sending light-weight computations to the data, i.e. **collocating** computations with data. As a result, Ignite scales better and minimizes data movement.
+Most traditional databases work in a client-server fashion, meaning that data must be brought to the client side for processing. This approach requires lots of data movement from servers to clients and generally does not scale. GridGain, on the other hand, allows for sending light-weight computations to the data, i.e. **collocating** computations with data. As a result, GridGain scales better and minimizes data movement.
[Read More](https://apacheignite.readme.io/docs/collocate-compute-and-data)
## Scalability and Durability
-Ignite is an elastic, horizontally scalable distributed system that supports adding and removing cluster nodes on demand. Ignite also allows for storing multiple copies of the data, making it resilient to partial cluster failures. If the persistence is enabled, then data stored in Ignite will also survive full cluster failures. Cluster restarts in Ignite can be very fast, as the data becomes operational instantaneously directly from disk. As a result, the data does not need to be preload [...]
+GridGain is an elastic, horizontally scalable distributed system that supports adding and removing cluster nodes on demand. GridGain also allows for storing multiple copies of the data, making it resilient to partial cluster failures. If the persistence is enabled, then data stored in GridGain will also survive full cluster failures. Cluster restarts in GridGain can be very fast, as the data becomes operational instantaneously directly from disk. As a result, the data does not need to be [...]
[Read More](https://apacheignite.readme.io/docs/clustering)
-## Ignite Components
+## GridGain Components
-You can view Apache Ignite as a collection of independent, well-integrated components geared to improve performance and
+You can view Apache GridGain as a collection of independent, well-integrated components geared to improve performance and
scalability of your application.
Some of these components include:
@@ -97,7 +98,6 @@ Some of these components include:
* [SQL Database](#sql-database)
* [Compute Grid](#compute-grid)
* [Service Grid](#service-grid)
-* [Hadoop Accelerator](#hadoop-accelerator)
* [Spark Shared RDDs and SQL indexes](#spark-shared-rdds)
Below you’ll find a brief explanation for each of them.
@@ -105,7 +105,7 @@ Below you’ll find a brief explanation for each of them.
### Advanced Clustering
-Ignite nodes can [automatically discover](https://apacheignite.readme.io/docs/cluster) each other. This helps to scale the cluster when needed, without having to restart the whole cluster. Developers can also leverage from Ignite’s hybrid cloud support that allows establishing connection between private cloud and public clouds such as Amazon Web Services, providing them with best of both worlds.
+GridGain nodes can [automatically discover](https://apacheignite.readme.io/docs/cluster) each other. This helps to scale the cluster when needed, without having to restart the whole cluster. Developers can also leverage from GridGain’s hybrid cloud support that allows establishing connection between private cloud and public clouds such as Amazon Web Services, providing them with best of both worlds.
<p align="center">
<a href="https://apacheignite.readme.io/docs/cluster">
@@ -113,7 +113,7 @@ Ignite nodes can [automatically discover](https://apacheignite.readme.io/docs/cl
</a>
</p>
-Apache Ignite can be deployed on:
+GridGain can be deployed on:
* [AWS](https://apacheignite.readme.io/docs/aws-deployment)
* [Docker](https://apacheignite.readme.io/docs/docker-deployment)
* [Google Compute](https://apacheignite.readme.io/docs/google-compute-deployment)
@@ -124,16 +124,16 @@ Apache Ignite can be deployed on:
### Data Grid (JCache)
-[Ignite data grid](https://apacheignite.readme.io/docs/data-grid) is an in-memory distributed key-value store which can be viewed as a distributed partitioned hash map,
+GridGain data grid is an in-memory distributed key-value store which can be viewed as a distributed partitioned hash map,
with every cluster node owning a portion of the overall data. This way the more cluster nodes we add, the more data we
can cache.
-Unlike other key-value stores, Ignite determines data locality using a pluggable hashing algorithm. Every client can
+Unlike other key-value stores, GridGain determines data locality using a pluggable hashing algorithm. Every client can
determine which node a key belongs to by plugging it into a hashing function, without a need for any special mapping
servers or name nodes.
-Ignite data grid supports local, replicated, and partitioned data sets and allows to freely cross query between these
-data sets using standard SQL syntax. Ignite supports standard SQL for querying in-memory data including support for distributed SQL joins.
+GridGain data grid supports local, replicated, and partitioned data sets and allows to freely cross query between these
+data sets using standard SQL syntax. GridGain supports standard SQL for querying in-memory data including support for distributed SQL joins.
<p align="center">
<a href="https://apacheignite.readme.io/docs/data-grid">
@@ -143,16 +143,16 @@ data sets using standard SQL syntax. Ignite supports standard SQL for querying i
### SQL Database
-Apache Ignite incorporates [distributed SQL database](https://apacheignite.readme.io/docs/distributed-sql) capabilities as a part of its platform. The database is horizontally
+GridGain incorporates [distributed SQL database](https://apacheignite.readme.io/docs/distributed-sql) capabilities as a part of its platform. The database is horizontally
scalable, fault tolerant and SQL ANSI-99 compliant. It supports all SQL, DDL, and DML commands including SELECT, UPDATE,
INSERT, MERGE, and DELETE queries. It also provides support for a subset of DDL commands relevant for distributed
databases.
-With Ignite Durable Memory architecture, data as well as indexes can be stored both in memory and, optionally, on disk.
+With GridGain Durable Memory architecture, data as well as indexes can be stored both in memory and, optionally, on disk.
This allows executing distributed SQL operations across different memory layers achieving in-memory performance with the durability of disk.
-You can interact with Apache Ignite using the SQL language via natively developed APIs for Java, .NET and C++, or via
-the Ignite JDBC or ODBC drivers. This provides a true cross-platform connectivity from languages such as PHP, Ruby and more.
+You can interact with GridGain using the SQL language via natively developed APIs for Java, .NET and C++, or via
+the GridGain JDBC or ODBC drivers. This provides a true cross-platform connectivity from languages such as PHP, Ruby and more.
<p align="center">
@@ -165,7 +165,7 @@ the Ignite JDBC or ODBC drivers. This provides a true cross-platform connectivit
### Compute Grid
[Distributed computations](https://apacheignite.readme.io/docs/compute-grid) are performed in parallel fashion to gain high performance, low latency, and linear scalability.
- Ignite compute grid provides a set of simple APIs that allow users distribute computations and data processing across
+ GridGain compute grid provides a set of simple APIs that allow users distribute computations and data processing across
multiple computers in the cluster. Distributed parallel processing is based on the ability to take any computation and
execute it on any set of cluster nodes and return the results back.
@@ -193,7 +193,7 @@ We support these features, amongst others:
[Service Grid](https://apacheignite.readme.io/docs/service-grid) allows for deployments of arbitrary user-defined services on the cluster. You can implement and deploy any
service, such as custom counters, ID generators, hierarchical maps, etc.
-Ignite allows you to control how many instances of your service should be deployed on each cluster node and will
+GridGain allows you to control how many instances of your service should be deployed on each cluster node and will
automatically ensure proper deployment and fault tolerance of all the services.
<p align="center">
@@ -202,17 +202,9 @@ automatically ensure proper deployment and fault tolerance of all the services.
</a>
</p>
-### Ignite File System
-
-[Ignite File System](https://apacheignite-fs.readme.io/docs/in-memory-file-system) (IGFS) is an in-memory file system allowing work with files and directories over existing cache
-infrastructure. IGFS can either work as purely in-memory file system, or delegate to another file system (e.g. various
-Hadoop file system implementations) acting as a caching layer.
-
-In addition, IGFS provides API to execute map-reduce tasks over file system data.
-
### Distributed Data Structures
-Ignite supports complex [data structures](https://apacheignite.readme.io/docs/data-structures) in a distributed fashion:
+GridGain supports complex [data structures](https://apacheignite.readme.io/docs/data-structures) in a distributed fashion:
* [Queues and sets](https://apacheignite.readme.io/docs/queue-and-set): ordinary, bounded, collocated, non-collocated
* [Atomic types](https://apacheignite.readme.io/docs/atomic-types): `AtomicLong` and `AtomicReference`
@@ -225,16 +217,13 @@ Ignite supports complex [data structures](https://apacheignite.readme.io/docs/da
[Distributed messaging](https://apacheignite.readme.io/docs/messaging) allows for topic based cluster-wide communication between all nodes. Messages with a specified
message topic can be distributed to all or sub-group of nodes that have subscribed to that topic.
-Ignite messaging is based on publish-subscribe paradigm where publishers and subscribers are connected together by a
+GridGain messaging is based on publish-subscribe paradigm where publishers and subscribers are connected together by a
common topic. When one of the nodes sends a message A for topic T, it is published on all nodes that have subscribed to T.
### Distributed Events
[Distributed events](https://apacheignite.readme.io/docs/events) allow applications to receive notifications when a variety of events occur in the distributed grid environment. You can automatically get notified for task executions, read, write or query operations occurring on local or remote nodes within the cluster.
-### Hadoop Accelerator
-
-Our [Hadoop Accelerator](https://apacheignite-fs.readme.io/docs/hadoop-accelerator) provides a set of components allowing for in-memory Hadoop job execution and file system operations.
#### MapReduce
@@ -247,34 +236,12 @@ boost your Hadoop MapReduce job execution performance.
</a>
</p>
-#### IGFS - In-Memory File System
-
-A Hadoop-compliant [IGFS](https://apacheignite-fs.readme.io/docs/file-system) File System implementation over which Hadoop can run over in plug-n-play fashion and significantly reduce I/O and improve both, latency and throughput.
-
-<p align="center">
- <a href="https://apacheignite-fs.readme.io/docs/in-memory-file-system">
- <img src="https://ignite.apache.org/images/ignite_filesystem.png" height="300" vspace="15"/>
- </a>
-</p>
-
-#### Secondary File System
-
-An implementation of [`SecondaryFileSystem`](https://apacheignite-fs.readme.io/docs/secondary-file-system). This implementation can be injected into existing IGFS allowing for
-read-through and write-through behavior over any other Hadoop FileSystem implementation (e.g. HDFS). Use it if you
-want your IGFS to become an in-memory caching layer over disk-based HDFS or any other Hadoop-compliant file system.
-
-#### Supported Hadoop distributions
-
-* [Apache Hadoop](https://apacheignite-fs.readme.io/docs/installing-on-apache-hadoop)
-* [Cloudera CDH](https://apacheignite-fs.readme.io/docs/installing-on-cloudera-cdh)
-* [Hortonworks HDP](https://apacheignite-fs.readme.io/docs/installing-on-hortonworks-hdp)
-* [Apache Hive](https://apacheignite-fs.readme.io/docs/running-apache-hive-over-ignited-hadoop)
### Spark Shared RDDs
-Apache Ignite provides an implementation of Spark RDD abstraction which allows to easily share state in memory across Spark jobs.
+GridGain provides an implementation of Spark RDD abstraction which allows to easily share state in memory across Spark jobs.
-The main difference between native Spark `RDD` and `IgniteRDD` is that Ignite RDD provides a [shared in-memory](https://apacheignite-fs.readme.io/docs/ignite-for-spark) view on data across different Spark jobs, workers, or applications, while native Spark RDD cannot be seen by other Spark jobs or applications.
+The main difference between native Spark `RDD` and `GridGainRDD` is that GridGain RDD provides a [shared in-memory](https://apacheignite-fs.readme.io/docs/ignite-for-spark) view on data across different Spark jobs, workers, or applications, while native Spark RDD cannot be seen by other Spark jobs or applications.
<p align="center">
<a href="https://apacheignite-fs.readme.io/docs/ignite-for-spark">
@@ -282,64 +249,65 @@ The main difference between native Spark `RDD` and `IgniteRDD` is that Ignite RD
</a>
</p>
-## Ignite Facts
+## GridGain Facts
-#### Is Ignite a persistent or pure in-memory storage?
-**Both**. Native persistence in Ignite can be turned on and off. This allows Ignite to store data sets bigger than can fit in the available memory. Essentially, the smaller operational data sets can be stored in-memory only, and larger data sets that do not fit in memory can be stored on disk, using memory as a caching layer for better performance.
+#### Is GridGain a persistent or pure in-memory storage?
+**Both**. Native persistence in GridGain can be turned on and off. This allows GridGain to store data sets bigger than can fit in the available memory. Essentially, the smaller operational data sets can be stored in-memory only, and larger data sets that do not fit in memory can be stored on disk, using memory as a caching layer for better performance.
[Read More](https://apacheignite.readme.io/docs/distributed-persistent-store)
-#### Is Ignite a distributed database?
-**Yes**. Data in Ignite is either *partitioned* or *replicated* across a cluster of multiple nodes. This provides scalability and adds resilience to the system. Ignite automatically controls how data is partitioned, however, users can plug in their own distribution (affinity) functions and collocate various pieces of data together for efficiency.
+#### Is GridGain a distributed database?
+**Yes**. Data in GridGain is either *partitioned* or *replicated* across a cluster of multiple nodes. This provides scalability and adds resilience to the system. GridGain automatically controls how data is partitioned, however, users can plug in their own distribution (affinity) functions and collocate various pieces of data together for efficiency.
[Read More](https://apacheignite.readme.io/docs/distributed-sql)
-#### Is Ignite a relational SQL database?
-**Not fully**. Although Ignite aims to behave like any other relational SQL database, there are differences in how Ignite handles constraints and indexes. Ignite supports *primary* and *secondary* indexes, however, the *uniqueness* can only be enforced for the *primary* indexes. Ignite also does not support *foreign key* constraints.
+#### Is GridGain a relational SQL database?
+**Not fully**. Although GridGain aims to behave like any other relational SQL database, there are differences in how GridGain handles constraints and indexes. GridGain supports *primary* and *secondary* indexes, however, the *uniqueness* can only be enforced for the *primary* indexes. GridGain also does not support *foreign key* constraints.
-Essentially, Ignite purposely does not support any constraints that would entail a cluster broadcast message for each update and significantly hurt performance and scalability of the system.
+Essentially, GridGain purposely does not support any constraints that would entail a cluster broadcast message for each update and significantly hurt performance and scalability of the system.
[Read More](https://apacheignite.readme.io/docs/indexes)
-#### Is Ignite an in-memory database?
-**Yes**. Even though Ignite *durable memory* works well in-memory and on-disk, the disk persistence can be disabled and Ignite can act as a pure *in-memory database*.
+#### Is GridGain an in-memory database?
+**Yes**. Even though GridGain *durable memory* works well in-memory and on-disk, the disk persistence can be disabled and GridGain can act as a pure *in-memory database*.
[Read More](https://apacheignite.readme.io/docs/distributed-sql)
-#### Is Ignite a transactional database?
-**Not fully**. ACID Transactions are supported, but only at *key-value* API level. Ignite also supports *cross-partition* transactions, which means that transactions can span keys residing in different partitions on different servers.
+#### Is GridGain a transactional database?
+**Not fully**. ACID Transactions are supported, but only at *key-value* API level. GridGain also supports *cross-partition* transactions, which means that transactions can span keys residing in different partitions on different servers.
-At *SQL* level Ignite supports *atomic*, but not yet *transactional* consistency. Ignite community plans to implement SQL transactions in version 2.2.
+At *SQL* level GridGain supports *atomic*, but not yet *transactional* consistency. GridGain community plans to implement SQL transactions in version 2.2.
[Read More](https://apacheignite.readme.io/docs/sql-queries#known-limitations)
-#### Is Ignite a key-value store?
-**Yes**. Ignite provides a feature rich key-value API, that is JCache (JSR-107) compliant and supports Java, C++, and .NET.
+#### Is GridGain a key-value store?
+**Yes**. GridGain provides a feature rich key-value API, that is JCache (JSR-107) compliant and supports Java, C++, and .NET.
[Read More](https://apacheignite.readme.io/docs/data-grid)
-#### Is Ignite an in-memory data grid?
-**Yes**. Ignite is a full-featured data grid, which can be used either in pure in-memory mode or with Ignite native persistence. It can also integrate with any 3rd party database, including any RDBMS or NoSQL store.
+#### Is GridGain an in-memory data grid?
+**Yes**. GridGain is a full-featured data grid, which can be used either in pure in-memory mode or with native persistence. It can also integrate with any 3rd party database, including any RDBMS or NoSQL store.
[Read More](https://apacheignite.readme.io/docs/data-grid)
#### What is durable memory?
-Ignite *durable memory* architecture allows Ignite to extend in-memory computing to disk. It is based on a paged-based off-heap memory allocator which becomes durable by persisting to the *write-ahead-log (WAL)* and, then, to main Ignite persistent storage. When persistence is disabled, durable memory acts like a pure in-memory storage.
+GridGain *durable memory* architecture allows GridGain to extend in-memory computing to disk. It is based on a paged-based off-heap memory allocator which becomes durable by persisting to the *write-ahead-log (WAL)* and, then, to main GridGain persistent storage. When persistence is disabled, durable memory acts like a pure in-memory storage.
[Read More](https://apacheignite.readme.io/docs/durable-memory)
#### What is collocated processing?
-Ignite is a distributed system and, therefore, it is important to be able to collocate data with data and compute with data to avoid distributed data noise. Data collocation becomes especially important when performing distributed SQL joins. Ignite also supports sending user logic (functions, lambdas, etc.) directly to the nodes where the data resides and computing on the data locally.
+GridGain is a distributed system and, therefore, it is important to be able to collocate data with data and compute with data to avoid distributed data noise. Data collocation becomes especially important when performing distributed SQL joins. GridGain also supports sending user logic (functions, lambdas, etc.) directly to the nodes where the data resides and computing on the data locally.
[Read More](https://apacheignite.readme.io/docs/collocate-compute-and-data)
-## Ignite On Other Platforms
+## GridGain On Other Platforms
-<a href="modules/platforms/dotnet">Ignite.NET</a>
+<a href="modules/platforms/dotnet">GridGain.NET</a>
-<a href="modules/platforms/cpp">Ignite C++</a>
+<a href="modules/platforms/cpp">GridGain C++</a>
[apache-ignite-homepage]: https://ignite.apache.org/
-[getting-started]: https://apacheignite.readme.io/docs/getting-started
-[docs]: https://apacheignite.readme.io/docs
\ No newline at end of file
+[GridGain-homepage]: https://www.gridgain.com/
+[getting-started]: https://docs.gridgain.com/docs
+[docs]: https://docs.gridgain.com/docs
\ No newline at end of file
diff --git a/README.txt b/README.txt
index 2e6add5..0db0d3c 100644
--- a/README.txt
+++ b/README.txt
@@ -1,10 +1,13 @@
-Apache Ignite In-Memory Database and Caching Platform
-=====================================================
+GridGain Community Edition
+===========================
-Ignite is a memory-centric distributed database, caching, and processing platform for transactional, analytical,
-and streaming workloads delivering in-memory speeds at petabyte scale.
+The GridGain Community Edition (GCE) is a source-available in-memory computing platform built on Apache Ignite.
+GCE includes the Apache Ignite code base plus improvements and additional functionality developed by GridGain Systems
+to enhance the performance and reliability of Apache Ignite. GCE is a hardened, high-performance version of Apache Ignite
+for mission-critical in-memory computing applications.
-The main feature set of Ignite includes:
+
+The main feature set of GridGain Community Edition includes:
* Memory-Centric Storage
* Advanced Clustering
* Distributed Key-Value
@@ -16,11 +19,6 @@ The main feature set of Ignite includes:
* Distributed Events
* Streaming & CEP
-For information on how to get started with Apache Ignite please visit:
-
- http://apacheignite.readme.io/docs/getting-started
-
-
-You can find Apache Ignite documentation here:
+For information on how to get started with GridGain please visit:
- http://apacheignite.readme.io/docs
+ https://docs.gridgain.com/docs
\ No newline at end of file
diff --git a/assembly/LICENSE_HADOOP b/assembly/LICENSE_HADOOP
index 3db2360..4f2f7db 100644
--- a/assembly/LICENSE_HADOOP
+++ b/assembly/LICENSE_HADOOP
@@ -1,257 +1,13 @@
- Apache License
- Version 2.0, January 2004
- http://www.apache.org/licenses/
+Copyright 2019 GridGain Systems, Inc. and Contributors.
- TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
-
- 1. Definitions.
-
- "License" shall mean the terms and conditions for use, reproduction,
- and distribution as defined by Sections 1 through 9 of this document.
-
- "Licensor" shall mean the copyright owner or entity authorized by
- the copyright owner that is granting the License.
-
- "Legal Entity" shall mean the union of the acting entity and all
- other entities that control, are controlled by, or are under common
- control with that entity. For the purposes of this definition,
- "control" means (i) the power, direct or indirect, to cause the
- direction or management of such entity, whether by contract or
- otherwise, or (ii) ownership of fifty percent (50%) or more of the
- outstanding shares, or (iii) beneficial ownership of such entity.
-
- "You" (or "Your") shall mean an individual or Legal Entity
- exercising permissions granted by this License.
-
- "Source" form shall mean the preferred form for making modifications,
- including but not limited to software source code, documentation
- source, and configuration files.
-
- "Object" form shall mean any form resulting from mechanical
- transformation or translation of a Source form, including but
- not limited to compiled object code, generated documentation,
- and conversions to other media types.
-
- "Work" shall mean the work of authorship, whether in Source or
- Object form, made available under the License, as indicated by a
- copyright notice that is included in or attached to the work
- (an example is provided in the Appendix below).
-
- "Derivative Works" shall mean any work, whether in Source or Object
- form, that is based on (or derived from) the Work and for which the
- editorial revisions, annotations, elaborations, or other modifications
- represent, as a whole, an original work of authorship. For the purposes
- of this License, Derivative Works shall not include works that remain
- separable from, or merely link (or bind by name) to the interfaces of,
- the Work and Derivative Works thereof.
-
- "Contribution" shall mean any work of authorship, including
- the original version of the Work and any modifications or additions
- to that Work or Derivative Works thereof, that is intentionally
- submitted to Licensor for inclusion in the Work by the copyright owner
- or by an individual or Legal Entity authorized to submit on behalf of
- the copyright owner. For the purposes of this definition, "submitted"
- means any form of electronic, verbal, or written communication sent
- to the Licensor or its representatives, including but not limited to
- communication on electronic mailing lists, source code control systems,
- and issue tracking systems that are managed by, or on behalf of, the
- Licensor for the purpose of discussing and improving the Work, but
- excluding communication that is conspicuously marked or otherwise
- designated in writing by the copyright owner as "Not a Contribution."
-
- "Contributor" shall mean Licensor and any individual or Legal Entity
- on behalf of whom a Contribution has been received by Licensor and
- subsequently incorporated within the Work.
-
- 2. Grant of Copyright License. Subject to the terms and conditions of
- this License, each Contributor hereby grants to You a perpetual,
- worldwide, non-exclusive, no-charge, royalty-free, irrevocable
- copyright license to reproduce, prepare Derivative Works of,
- publicly display, publicly perform, sublicense, and distribute the
- Work and such Derivative Works in Source or Object form.
-
- 3. Grant of Patent License. Subject to the terms and conditions of
- this License, each Contributor hereby grants to You a perpetual,
- worldwide, non-exclusive, no-charge, royalty-free, irrevocable
- (except as stated in this section) patent license to make, have made,
- use, offer to sell, sell, import, and otherwise transfer the Work,
- where such license applies only to those patent claims licensable
- by such Contributor that are necessarily infringed by their
- Contribution(s) alone or by combination of their Contribution(s)
- with the Work to which such Contribution(s) was submitted. If You
- institute patent litigation against any entity (including a
- cross-claim or counterclaim in a lawsuit) alleging that the Work
- or a Contribution incorporated within the Work constitutes direct
- or contributory patent infringement, then any patent licenses
- granted to You under this License for that Work shall terminate
- as of the date such litigation is filed.
-
- 4. Redistribution. You may reproduce and distribute copies of the
- Work or Derivative Works thereof in any medium, with or without
- modifications, and in Source or Object form, provided that You
- meet the following conditions:
-
- (a) You must give any other recipients of the Work or
- Derivative Works a copy of this License; and
-
- (b) You must cause any modified files to carry prominent notices
- stating that You changed the files; and
-
- (c) You must retain, in the Source form of any Derivative Works
- that You distribute, all copyright, patent, trademark, and
- attribution notices from the Source form of the Work,
- excluding those notices that do not pertain to any part of
- the Derivative Works; and
-
- (d) If the Work includes a "NOTICE" text file as part of its
- distribution, then any Derivative Works that You distribute must
- include a readable copy of the attribution notices contained
- within such NOTICE file, excluding those notices that do not
- pertain to any part of the Derivative Works, in at least one
- of the following places: within a NOTICE text file distributed
- as part of the Derivative Works; within the Source form or
- documentation, if provided along with the Derivative Works; or,
- within a display generated by the Derivative Works, if and
- wherever such third-party notices normally appear. The contents
- of the NOTICE file are for informational purposes only and
- do not modify the License. You may add Your own attribution
- notices within Derivative Works that You distribute, alongside
- or as an addendum to the NOTICE text from the Work, provided
- that such additional attribution notices cannot be construed
- as modifying the License.
-
- You may add Your own copyright statement to Your modifications and
- may provide additional or different license terms and conditions
- for use, reproduction, or distribution of Your modifications, or
- for any such Derivative Works as a whole, provided Your use,
- reproduction, and distribution of the Work otherwise complies with
- the conditions stated in this License.
-
- 5. Submission of Contributions. Unless You explicitly state otherwise,
- any Contribution intentionally submitted for inclusion in the Work
- by You to the Licensor shall be under the terms and conditions of
- this License, without any additional terms or conditions.
- Notwithstanding the above, nothing herein shall supersede or modify
- the terms of any separate license agreement you may have executed
- with Licensor regarding such Contributions.
-
- 6. Trademarks. This License does not grant permission to use the trade
- names, trademarks, service marks, or product names of the Licensor,
- except as required for reasonable and customary use in describing the
- origin of the Work and reproducing the content of the NOTICE file.
-
- 7. Disclaimer of Warranty. Unless required by applicable law or
- agreed to in writing, Licensor provides the Work (and each
- Contributor provides its Contributions) on an "AS IS" BASIS,
- WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
- implied, including, without limitation, any warranties or conditions
- of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
- PARTICULAR PURPOSE. You are solely responsible for determining the
- appropriateness of using or redistributing the Work and assume any
- risks associated with Your exercise of permissions under this License.
-
- 8. Limitation of Liability. In no event and under no legal theory,
- whether in tort (including negligence), contract, or otherwise,
- unless required by applicable law (such as deliberate and grossly
- negligent acts) or agreed to in writing, shall any Contributor be
- liable to You for damages, including any direct, indirect, special,
- incidental, or consequential damages of any character arising as a
- result of this License or out of the use or inability to use the
- Work (including but not limited to damages for loss of goodwill,
- work stoppage, computer failure or malfunction, or any and all
- other commercial damages or losses), even if such Contributor
- has been advised of the possibility of such damages.
-
- 9. Accepting Warranty or Additional Liability. While redistributing
- the Work or Derivative Works thereof, You may choose to offer,
- and charge a fee for, acceptance of support, warranty, indemnity,
- or other liability obligations and/or rights consistent with this
- License. However, in accepting such obligations, You may act only
- on Your own behalf and on Your sole responsibility, not on behalf
- of any other Contributor, and only if You agree to indemnify,
- defend, and hold each Contributor harmless for any liability
- incurred by, or claims asserted against, such Contributor by reason
- of your accepting any such warranty or additional liability.
-
- END OF TERMS AND CONDITIONS
-
- APPENDIX: How to apply the Apache License to your work.
-
- To apply the Apache License to your work, attach the following
- boilerplate notice, with the fields enclosed by brackets "[]"
- replaced with your own identifying information. (Don't include
- the brackets!) The text should be enclosed in the appropriate
- comment syntax for the file format. We also recommend that a
- file or class name and description of purpose be included on the
- same "printed page" as the copyright notice for easier
- identification within third-party archives.
-
- Copyright [yyyy] [name of copyright owner]
-
- Licensed under the Apache License, Version 2.0 (the "License");
- you may not use this file except in compliance with the License.
- You may obtain a copy of the License at
-
- http://www.apache.org/licenses/LICENSE-2.0
-
- Unless required by applicable law or agreed to in writing, software
- distributed under the License is distributed on an "AS IS" BASIS,
- WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
- See the License for the specific language governing permissions and
- limitations under the License.
-
-
-
-==============================================================================
-Apache Ignite Subcomponents:
-
-The Apache Ignite project contains subcomponents with separate copyright
-notices and license terms. Your use of the source code for the these
-subcomponents is subject to the terms and conditions of the following
-licenses.
-
-
-==============================================================================
-For SnapTree:
-==============================================================================
-This product bundles SnapTree, which is available under the following:
-"3-clause BSD" license. For details, see https://github.com/nbronson/snaptree/blob/master/LICENSE.
-
-==============================================================================
-For JSR 166 classes in "org.jsr166" package
-==============================================================================
-This product bundles JSR-166 classes which are donated to public domain.
-For details, see CC0 1.0 Universal (1.0), Public Domain Dedication,
-http://creativecommons.org/publicdomain/zero/1.0/
-
-==============================================================================
-For JSR107 API and SPI (https://github.com/jsr107/jsr107spec) javax.cache:cache-api:jar:1.0.0
-==============================================================================
-This product bundles JSR107 API and SPI which is available under the following:
-JSR-000107 JCACHE 2.9 Public Review - Updated Specification License. https://raw.github.com/jsr107/jsr107spec/master/LICENSE.txt
-
-==============================================================================
-For JSch (http://www.jcraft.com/jsch/) com.jcraft:jsch:jar:0.1.50
-==============================================================================
-This product bundles JSch which is available under the following:
-Revised BSD. For details, see http://www.jcraft.com/jsch/LICENSE.txt.
-
-==============================================================================
-For JLine (http://nexus.sonatype.org/oss-repository-hosting.html/jline) jline:jline:jar:2.12.1
-==============================================================================
-This product bundles JLine which is available under the following:
-The BSD License. For details, see http://www.opensource.org/licenses/bsd-license.php.
-
-==============================================================================
-For Scala Library (http://www.scala-lang.org/) org.scala-lang:scala-library:jar:2.11.2
-==============================================================================
-This product bundles Scala Library which is available under the following:
-BSD 3-Clause. For details, see http://www.scala-lang.org/license.html.
-
-==============================================================================
-For ASM All (http://asm.objectweb.org/asm-all/) org.ow2.asm:asm-all:jar:5.0.3
-==============================================================================
-This product bundles ASM All which is available under the following:
-BSD. For details, see http://asm.objectweb.org/license.html.
+Licensed under the GridGain Community Edition License (the "License");
+you may not use this file except in compliance with the License.
+You may obtain a copy of the License at
+ https://www.gridgain.com/products/software/community-edition/gridgain-community-edition-license
+Unless required by applicable law or agreed to in writing, software
+distributed under the License is distributed on an "AS IS" BASIS,
+WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+See the License for the specific language governing permissions and
+limitations under the License.
\ No newline at end of file
diff --git a/assembly/LICENSE_IGNITE b/assembly/LICENSE_IGNITE
index ce44bea..4f2f7db 100644
--- a/assembly/LICENSE_IGNITE
+++ b/assembly/LICENSE_IGNITE
@@ -1,304 +1,13 @@
- Apache License
- Version 2.0, January 2004
- http://www.apache.org/licenses/
+Copyright 2019 GridGain Systems, Inc. and Contributors.
- TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+Licensed under the GridGain Community Edition License (the "License");
+you may not use this file except in compliance with the License.
+You may obtain a copy of the License at
- 1. Definitions.
+ https://www.gridgain.com/products/software/community-edition/gridgain-community-edition-license
- "License" shall mean the terms and conditions for use, reproduction,
- and distribution as defined by Sections 1 through 9 of this document.
-
- "Licensor" shall mean the copyright owner or entity authorized by
- the copyright owner that is granting the License.
-
- "Legal Entity" shall mean the union of the acting entity and all
- other entities that control, are controlled by, or are under common
- control with that entity. For the purposes of this definition,
- "control" means (i) the power, direct or indirect, to cause the
- direction or management of such entity, whether by contract or
- otherwise, or (ii) ownership of fifty percent (50%) or more of the
- outstanding shares, or (iii) beneficial ownership of such entity.
-
- "You" (or "Your") shall mean an individual or Legal Entity
- exercising permissions granted by this License.
-
- "Source" form shall mean the preferred form for making modifications,
- including but not limited to software source code, documentation
- source, and configuration files.
-
- "Object" form shall mean any form resulting from mechanical
- transformation or translation of a Source form, including but
- not limited to compiled object code, generated documentation,
- and conversions to other media types.
-
- "Work" shall mean the work of authorship, whether in Source or
- Object form, made available under the License, as indicated by a
- copyright notice that is included in or attached to the work
- (an example is provided in the Appendix below).
-
- "Derivative Works" shall mean any work, whether in Source or Object
- form, that is based on (or derived from) the Work and for which the
- editorial revisions, annotations, elaborations, or other modifications
- represent, as a whole, an original work of authorship. For the purposes
- of this License, Derivative Works shall not include works that remain
- separable from, or merely link (or bind by name) to the interfaces of,
- the Work and Derivative Works thereof.
-
- "Contribution" shall mean any work of authorship, including
- the original version of the Work and any modifications or additions
- to that Work or Derivative Works thereof, that is intentionally
- submitted to Licensor for inclusion in the Work by the copyright owner
- or by an individual or Legal Entity authorized to submit on behalf of
- the copyright owner. For the purposes of this definition, "submitted"
- means any form of electronic, verbal, or written communication sent
- to the Licensor or its representatives, including but not limited to
- communication on electronic mailing lists, source code control systems,
- and issue tracking systems that are managed by, or on behalf of, the
- Licensor for the purpose of discussing and improving the Work, but
- excluding communication that is conspicuously marked or otherwise
- designated in writing by the copyright owner as "Not a Contribution."
-
- "Contributor" shall mean Licensor and any individual or Legal Entity
- on behalf of whom a Contribution has been received by Licensor and
- subsequently incorporated within the Work.
-
- 2. Grant of Copyright License. Subject to the terms and conditions of
- this License, each Contributor hereby grants to You a perpetual,
- worldwide, non-exclusive, no-charge, royalty-free, irrevocable
- copyright license to reproduce, prepare Derivative Works of,
- publicly display, publicly perform, sublicense, and distribute the
- Work and such Derivative Works in Source or Object form.
-
- 3. Grant of Patent License. Subject to the terms and conditions of
- this License, each Contributor hereby grants to You a perpetual,
- worldwide, non-exclusive, no-charge, royalty-free, irrevocable
- (except as stated in this section) patent license to make, have made,
- use, offer to sell, sell, import, and otherwise transfer the Work,
- where such license applies only to those patent claims licensable
- by such Contributor that are necessarily infringed by their
- Contribution(s) alone or by combination of their Contribution(s)
- with the Work to which such Contribution(s) was submitted. If You
- institute patent litigation against any entity (including a
- cross-claim or counterclaim in a lawsuit) alleging that the Work
- or a Contribution incorporated within the Work constitutes direct
- or contributory patent infringement, then any patent licenses
- granted to You under this License for that Work shall terminate
- as of the date such litigation is filed.
-
- 4. Redistribution. You may reproduce and distribute copies of the
- Work or Derivative Works thereof in any medium, with or without
- modifications, and in Source or Object form, provided that You
- meet the following conditions:
-
- (a) You must give any other recipients of the Work or
- Derivative Works a copy of this License; and
-
- (b) You must cause any modified files to carry prominent notices
- stating that You changed the files; and
-
- (c) You must retain, in the Source form of any Derivative Works
- that You distribute, all copyright, patent, trademark, and
- attribution notices from the Source form of the Work,
- excluding those notices that do not pertain to any part of
- the Derivative Works; and
-
- (d) If the Work includes a "NOTICE" text file as part of its
- distribution, then any Derivative Works that You distribute must
- include a readable copy of the attribution notices contained
- within such NOTICE file, excluding those notices that do not
- pertain to any part of the Derivative Works, in at least one
- of the following places: within a NOTICE text file distributed
- as part of the Derivative Works; within the Source form or
- documentation, if provided along with the Derivative Works; or,
- within a display generated by the Derivative Works, if and
- wherever such third-party notices normally appear. The contents
- of the NOTICE file are for informational purposes only and
- do not modify the License. You may add Your own attribution
- notices within Derivative Works that You distribute, alongside
- or as an addendum to the NOTICE text from the Work, provided
- that such additional attribution notices cannot be construed
- as modifying the License.
-
- You may add Your own copyright statement to Your modifications and
- may provide additional or different license terms and conditions
- for use, reproduction, or distribution of Your modifications, or
- for any such Derivative Works as a whole, provided Your use,
- reproduction, and distribution of the Work otherwise complies with
- the conditions stated in this License.
-
- 5. Submission of Contributions. Unless You explicitly state otherwise,
- any Contribution intentionally submitted for inclusion in the Work
- by You to the Licensor shall be under the terms and conditions of
- this License, without any additional terms or conditions.
- Notwithstanding the above, nothing herein shall supersede or modify
- the terms of any separate license agreement you may have executed
- with Licensor regarding such Contributions.
-
- 6. Trademarks. This License does not grant permission to use the trade
- names, trademarks, service marks, or product names of the Licensor,
- except as required for reasonable and customary use in describing the
- origin of the Work and reproducing the content of the NOTICE file.
-
- 7. Disclaimer of Warranty. Unless required by applicable law or
- agreed to in writing, Licensor provides the Work (and each
- Contributor provides its Contributions) on an "AS IS" BASIS,
- WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
- implied, including, without limitation, any warranties or conditions
- of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
- PARTICULAR PURPOSE. You are solely responsible for determining the
- appropriateness of using or redistributing the Work and assume any
- risks associated with Your exercise of permissions under this License.
-
- 8. Limitation of Liability. In no event and under no legal theory,
- whether in tort (including negligence), contract, or otherwise,
- unless required by applicable law (such as deliberate and grossly
- negligent acts) or agreed to in writing, shall any Contributor be
- liable to You for damages, including any direct, indirect, special,
- incidental, or consequential damages of any character arising as a
- result of this License or out of the use or inability to use the
- Work (including but not limited to damages for loss of goodwill,
- work stoppage, computer failure or malfunction, or any and all
- other commercial damages or losses), even if such Contributor
- has been advised of the possibility of such damages.
-
- 9. Accepting Warranty or Additional Liability. While redistributing
- the Work or Derivative Works thereof, You may choose to offer,
- and charge a fee for, acceptance of support, warranty, indemnity,
- or other liability obligations and/or rights consistent with this
- License. However, in accepting such obligations, You may act only
- on Your own behalf and on Your sole responsibility, not on behalf
- of any other Contributor, and only if You agree to indemnify,
- defend, and hold each Contributor harmless for any liability
- incurred by, or claims asserted against, such Contributor by reason
- of your accepting any such warranty or additional liability.
-
- END OF TERMS AND CONDITIONS
-
- APPENDIX: How to apply the Apache License to your work.
-
- To apply the Apache License to your work, attach the following
- boilerplate notice, with the fields enclosed by brackets "[]"
- replaced with your own identifying information. (Don't include
- the brackets!) The text should be enclosed in the appropriate
- comment syntax for the file format. We also recommend that a
- file or class name and description of purpose be included on the
- same "printed page" as the copyright notice for easier
- identification within third-party archives.
-
- Copyright [yyyy] [name of copyright owner]
-
- Licensed under the Apache License, Version 2.0 (the "License");
- you may not use this file except in compliance with the License.
- You may obtain a copy of the License at
-
- http://www.apache.org/licenses/LICENSE-2.0
-
- Unless required by applicable law or agreed to in writing, software
- distributed under the License is distributed on an "AS IS" BASIS,
- WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
- See the License for the specific language governing permissions and
- limitations under the License.
-
-
-
-==============================================================================
-Apache Ignite Subcomponents:
-
-The Apache Ignite project contains subcomponents with separate copyright
-notices and license terms. Your use of the source code for the these
-subcomponents is subject to the terms and conditions of the following
-licenses.
-
-
-==============================================================================
-For SnapTree:
-==============================================================================
-This product bundles SnapTree, which is available under the following:
-"3-clause BSD" license. For details, see https://github.com/nbronson/snaptree/blob/master/LICENSE.
-
-==============================================================================
-For JSR 166 classes in "org.jsr166" package
-==============================================================================
-This product bundles JSR-166 classes which are donated to public domain.
-For details, see CC0 1.0 Universal (1.0), Public Domain Dedication,
-http://creativecommons.org/publicdomain/zero/1.0/
-
-==============================================================================
-For JSR107 API and SPI (https://github.com/jsr107/jsr107spec) javax.cache:cache-api:jar:1.0.0
-==============================================================================
-This product bundles JSR107 API and SPI which is available under the following:
-JSR-000107 JCACHE 2.9 Public Review - Updated Specification License. https://raw.github.com/jsr107/jsr107spec/master/LICENSE.txt
-
-==============================================================================
-For JSch (http://www.jcraft.com/jsch/) com.jcraft:jsch:jar:0.1.50
-==============================================================================
-This product bundles JSch which is available under the following:
-Revised BSD. For details, see http://www.jcraft.com/jsch/LICENSE.txt.
-
-==============================================================================
-For JLine (http://nexus.sonatype.org/oss-repository-hosting.html/jline) jline:jline:jar:2.12.1
-==============================================================================
-This product bundles JLine which is available under the following:
-The BSD License. For details, see http://www.opensource.org/licenses/bsd-license.php.
-
-==============================================================================
-For Scala Library (http://www.scala-lang.org/) org.scala-lang:scala-library:jar:2.*
-==============================================================================
-This product bundles Scala Library which is available under the following:
-BSD 3-Clause. For details, see http://www.scala-lang.org/license.html.
-
-==============================================================================
-For H2 Database Engine (http://www.h2database.com) com.h2database:h2:jar:1.4.191
-==============================================================================
-This product bundles H2 Database Engine which is available under the following:
-MPL 2.0, and EPL 1.0. For details, see http://h2database.com/html/license.html.
-
-==============================================================================
-For JTidy (http://jtidy.sourceforge.net) net.sf.jtidy:jtidy:jar:r938
-==============================================================================
-This product bundles JTidy which is available under the following:
-Java HTML Tidy License. For details, see http://jtidy.svn.sourceforge.net/viewvc/jtidy/trunk/jtidy/LICENSE.txt?revision=95.
-
-==============================================================================
-For tomcat-servlet-api (http://tomcat.apache.org/) org.apache.tomcat:tomcat-servlet-api:jar:9.0.10
-==============================================================================
-This product bundles tomcat-servlet-api which is available under the following:
-Apache License, Version 2.0 and Common Development And Distribution License (CDDL) Version 1.0. For details, see http://www.apache.org/licenses/LICENSE-2.0.txt and http://www.opensource.org/licenses/cddl1.txt.
-
-==============================================================================
-For AOP alliance (http://aopalliance.sourceforge.net) aopalliance:aopalliance:jar:1.0
-==============================================================================
-This product bundles AOP alliance which is available under the following:
-Public Domain.
-
-==============================================================================
-For AspectJ (http://www.aspectj.org) org.aspectj:*:jar:1.7.2
-==============================================================================
-This product bundles AspectJ which is available under the following:
-Eclipse Public License - v 1.0. For details, see http://www.eclipse.org/legal/epl-v10.html.
-
-==============================================================================
-For Java Transaction API (http://java.sun.com/products/jta) javax.transaction:jta:jar:1.1
-==============================================================================
-This product bundles Java Transaction API which is available under it's own license.
-See http://download.oracle.com/otndocs/jcp/jta-1.1-classes-oth-JSpec/jta-1.1-classes-oth-JSpec-license.html for details.
-
-==============================================================================
-For ASM All (http://asm.objectweb.org/asm-all/) org.ow2.asm:asm-all:jar:5.0.3
-==============================================================================
-This product bundles ASM All which is available under the following:
-BSD. For details, see http://asm.objectweb.org/license.html.
-
-==============================================================================
-For Jetty (http://www.eclipse.org/jetty) org.eclipse.jetty:*:jar:9.2.11.v20150529
-==============================================================================
-This product bundles Jetty which is available under the following:
-Apache Software License - Version 2.0. For details, see http://www.apache.org/licenses/LICENSE-2.0.
-Eclipse Public License - Version 1.0. For details, see http://www.eclipse.org/org/documents/epl-v10.php.
-
-==============================================================================
-For SLF4J API Module (http://www.slf4j.org) org.slf4j:slf4j-api:jar:1.6.4
-==============================================================================
-This product bundles SLF4J API Module which is available under the following:
-MIT License. For details, see http://www.opensource.org/licenses/mit-license.php.
+Unless required by applicable law or agreed to in writing, software
+distributed under the License is distributed on an "AS IS" BASIS,
+WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+See the License for the specific language governing permissions and
+limitations under the License.
\ No newline at end of file
diff --git a/assembly/NOTICE_HADOOP b/assembly/NOTICE_HADOOP
index 0bae434..62c5414 100644
--- a/assembly/NOTICE_HADOOP
+++ b/assembly/NOTICE_HADOOP
@@ -1,5 +1,5 @@
-Apache Ignite
-Copyright 2019 The Apache Software Foundation
+GridGain
+Copyright 2019 GridGain Systems
This product includes software developed at
The Apache Software Foundation (http://www.apache.org/).
diff --git a/assembly/NOTICE_IGNITE b/assembly/NOTICE_IGNITE
index fffcc7c..df10333 100644
--- a/assembly/NOTICE_IGNITE
+++ b/assembly/NOTICE_IGNITE
@@ -1,5 +1,5 @@
-Apache Ignite
-Copyright 2019 The Apache Software Foundation
+GridGain
+Copyright 2019 GridGain Systems
This product includes software developed at
The Apache Software Foundation (http://www.apache.org/).
diff --git a/assembly/libs/README.txt b/assembly/libs/README.txt
index 1365cc1..c6233ba 100644
--- a/assembly/libs/README.txt
+++ b/assembly/libs/README.txt
@@ -1,14 +1,14 @@
-Apache Ignite Dependencies
+GridGain Dependencies
--------------------------
-Current folder contains JAR files for all Apache Ignite modules along with their dependencies.
+Current folder contains JAR files for all GridGain modules along with their dependencies.
When node is started using 'ignite.{sh|bat}' script, all JARs and classes located in
'libs' folder and all its sub-folders except 'optional' are added to classpath of the node.
-By default, only Apache Ignite core JAR and a minimum set of modules is enabled, while other
+By default, only GridGain core JAR and a minimum set of modules is enabled, while other
modules are located in 'optional' folder and therefore disabled.
-To enable any of optional Ignite modules when starting a standalone node,
+To enable any of optional GridGain modules when starting a standalone node,
move corresponding module folder from 'libs/optional' to 'libs' before running
'ignite.{sh|bat}' script. The content of the module folder will be added to
classpath in this case.
@@ -17,7 +17,7 @@ If you need to add your own classes to classpath of the node (e.g., task classes
to 'libs' folder. You can create a subfolder for convenience as well.
-Importing Ignite Dependencies In Maven Project
+Importing GridGain Dependencies In Maven Project
------------------------------------------------
If you are using Maven to manage dependencies of your project, there are two options:
@@ -26,7 +26,7 @@ If you are using Maven to manage dependencies of your project, there are two opt
- apache-ignite (all inclusive)
Here is how 'apache-ignite' can be added to your POM file (replace '${ignite.version}'
-with actual Ignite version you are interested in):
+with actual GridGain version you are interested in):
<project xmlns="http://maven.apache.org/POM/4.0.0"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
@@ -36,7 +36,7 @@ with actual Ignite version you are interested in):
<dependencies>
...
<dependency>
- <groupId>org.apache.ignite</groupId>
+ <groupId>org.gridgain</groupId>
<artifactId>apache-ignite</artifactId>
<version>${ignite.version}</version>
</dependency>
@@ -45,9 +45,9 @@ with actual Ignite version you are interested in):
...
</project>
-2. Or import individual Apache Ignite modules a la carte.
+2. Or import individual GridGain modules a la carte.
-Alternatively you can import Ignite modules a la carte, one by one.
+Alternatively you can import GridGain modules a la carte, one by one.
The only required module is 'ignite-core', all others are optional.
Here is how it can be imported into your POM file:
@@ -59,7 +59,7 @@ Here is how it can be imported into your POM file:
<dependencies>
...
<dependency>
- <groupId>org.apache.ignite</groupId>
+ <groupId>org.gridgain</groupId>
<artifactId>ignite-core</artifactId>
<version>${ignite.version}</version>
</dependency>
@@ -76,41 +76,41 @@ The following modules are available:
- ignite-camel (for Apache Camel integration)
- ignite-cassandra (for Apache Cassandra integration)
- ignite-cloud (for Apache JClouds integration)
-- ignite-flink (for streaming from Apache Flink into Ignite)
-- ignite-flume (for streaming events from Apache Flume into Ignite)
+- ignite-flink (for streaming from Apache Flink into GridGain)
+- ignite-flume (for streaming events from Apache Flume into GridGain)
- ignite-gce (for automatic cluster discovery on Google Compute Engine)
- ignite-hadoop (for Apache Hadoop Accelerator)
- ignite-hibernate (for Hibernate integration)
- ignite-hibernate5 (for Hibernate5 integration)
- ignite-indexing (for SQL querying and indexing)
- ignite-jcl (for Apache Commons logging)
-- ignite-jms11 (for streaming messaging from JMS queue or topic into Ignite)
+- ignite-jms11 (for streaming messaging from JMS queue or topic into GridGain)
- ignite-jta (for XA integration)
-- ignite-kafka (for streaming messages from Apache Kafka into Ignite)
+- ignite-kafka (for streaming messages from Apache Kafka into GridGain)
- ignite-logj4 (for Log4j logging)
- ignite-log4j2 (for Log4j 2 logging)
- ignite-mesos (for integration with Apache Mesos cluster resource manager)
-- ignite-mqtt (for streaming MQTT topic messages into Ignite)
-- ignite-osgi (to allow Ignite run seemlessly in OSGI containers)
+- ignite-mqtt (for streaming MQTT topic messages into GridGain)
+- ignite-osgi (to allow GridGain run seemlessly in OSGI containers)
- ignite-osgi-karaf (to seemlessly intall ignite into Apache Karaf container)
- ignite-osgi-paxlogging (to expose PAX Logging API to Log4j if needed)
- ignite-rest-http (for HTTP REST messages)
-- ignite-rocketmq (for streaming messages from Apache RocketMQ into Ignite)
+- ignite-rocketmq (for streaming messages from Apache RocketMQ into GridGain)
- ignite-scalar (for ignite Scala API)
-- ignite-scalar_2.10 (for Ignite Scala 2.10 API)
+- ignite-scalar_2.10 (for GridGain Scala 2.10 API)
- ignite-schedule (for Cron-based task scheduling)
- ignite-sl4j (for SL4J logging)
- ignite-spark (for shared in-memory RDDs and faster SQL for Apache Spark)
- ignite-spring (for Spring-based configuration support)
- ignite-ssh (for starting grid nodes on remote machines)
-- ignite-storm (for streaming events from Apache Storm into Ignite)
-- ignite-twitter (for streaming tweets from Twitter into Ignite)
+- ignite-storm (for streaming events from Apache Storm into GridGain)
+- ignite-twitter (for streaming tweets from Twitter into GridGain)
- ignite-urideploy (for URI-based deployment)
- ignite-web (for Web Sessions Clustering)
- ignite-yarn (for integration with Apache Hadoop Yarn)
- ignite-zookeeper (for cluster discovery based on Apache Zookeeper)
-For example, if you want to use Apache Ignite Spring-based configuration,
+For example, if you want to use GridGain Spring-based configuration,
you should add 'ignite-spring' module like this:
<project xmlns="http://maven.apache.org/POM/4.0.0"
@@ -122,14 +122,14 @@ you should add 'ignite-spring' module like this:
...
<!-- Core module. -->
<dependency>
- <groupId>org.apache.ignite</groupId>
+ <groupId>org.gridgain</groupId>
<artifactId>ignite-core</artifactId>
<version>${ignite.version}</version>
</dependency>
<!-- Optional. -->
<dependency>
- <groupId>org.apache.ignite</groupId>
+ <groupId>org.gridgain</groupId>
<artifactId>ignite-spring</artifactId>
<version>${ignite.version}</version>
</dependency>
diff --git a/docker/apache-ignite/README.txt b/docker/apache-ignite/README.txt
index 98d67b2..e8d4d14 100644
--- a/docker/apache-ignite/README.txt
+++ b/docker/apache-ignite/README.txt
@@ -1,21 +1,21 @@
-Apache Ignite Docker module
+GridGain Docker module
===========================
-Apache Ignite Docker module provides Dockerfile and accompanying files for building docker image.
+GridGain Docker module provides Dockerfile and accompanying files for building docker image.
Build image
===========
-1) Build Apache Ignite binary archive as described in DEVNOTES.txt.
+1) Build GridGain binary archive as described in DEVNOTES.txt.
-2) Goto Apache Ignite's Docker module directory
+2) Goto GridGain's Docker module directory
cd modules/docker
-3) Copy Apache Ignite's binary archive to Docker module directory
+3) Copy GridGain's binary archive to Docker module directory
cp -rfv ../../target/bin/apache-ignite-*.zip
-4) Unpack Apache Ignite's binary archive
+4) Unpack GridGain's binary archive
unzip apache-ignite-*.zip
diff --git a/docker/web-agent/README.txt b/docker/web-agent/README.txt
index 376e333..9f020ce 100644
--- a/docker/web-agent/README.txt
+++ b/docker/web-agent/README.txt
@@ -1,25 +1,24 @@
-Apache Ignite Web Agent Docker module
+GridGain Web Agent Docker module
=====================================
-Apache Ignite Web Agent Docker module provides Dockerfile and accompanying files
+GridGain Web Agent Docker module provides Dockerfile and accompanying files
for building docker image of Web Agent.
Build image
===========
-1) Build Apache Ignite Web Console module
+1) Build GridGain Web Console module
mvn clean install -T 2C \
-Pall-java,all-scala,licenses,web-console \
-pl :ignite-web-console -am \
-DskipTests
-2) Go to Apache Ignite Web Console Docker module directory and copy Apache
- Ignite Web Agent's binary archive
+2) Go to GridGain Web Console Docker module directory and copy GridGain Web Agent's binary archive
cd docker/web-agent
cp -rfv ../../modules/web-console/web-agent/target/ignite-web-agent-*.zip ./
-3) Unpack and remove Apache Ignite Web Agent's binary archive
+3) Unpack and remove GridGain Web Agent's binary archive
unzip ignite-web-agent-*.zip
rm -rf ignite-web-agent-*.zip
diff --git a/docker/web-console/standalone/README.txt b/docker/web-console/standalone/README.txt
index c97e792..bccc935 100644
--- a/docker/web-console/standalone/README.txt
+++ b/docker/web-console/standalone/README.txt
@@ -1,10 +1,10 @@
-Apache Ignite Web Console Standalone Docker module
+GridGain Web Console Standalone Docker module
==================================================
-Apache Ignite Web Console Standalone Docker module provides Dockerfile and accompanying files
+GridGain Web Console Standalone Docker module provides Dockerfile and accompanying files
for building docker image of Web Console.
-Ignite Web Console Standalone Docker Image Build Instructions
+GridGain Web Console Standalone Docker Image Build Instructions
=============================================================
1) Build ignite-web-console module
@@ -15,8 +15,8 @@ Ignite Web Console Standalone Docker Image Build Instructions
cp -rf modules/web-console/web-agent/target/ignite-web-agent-*.zip docker/web-console/standalone
-3) Go to Apache Ignite Web Console Docker module directory and copy Apache
- Ignite Web Console's frontend and backend directory
+3) Go to GridGain Web Console Docker module directory and copy GridGain
+ Web Console's frontend and backend directory
cd docker/web-console/standalone
cp -rf ../../../modules/web-console/backend ./
diff --git a/examples/README.md b/examples/README.md
index 1855953..dcdc641 100644
--- a/examples/README.md
+++ b/examples/README.md
@@ -1,13 +1,13 @@
-# Apache Ignite Examples
+# GridGain Examples
-This module contains examples of how to run [Apache Ignite](ignite.apache.org) and [Apache Ignite](ignite.apache.org) with 3rd party components.
+This module contains examples of how to run GridGain.
Instructions on how to start examples can be found in [README.txt](README.txt).
How to start examples in the developer's environment, please see [DEVNOTES.txt](DEVNOTES.txt).
## Running examples on JDK 9/10/11
-Ignite uses proprietary SDK APIs that are not available by default. See also [How to run Ignite on JDK 9,10 and 11](https://apacheignite.readme.io/docs/getting-started#section-running-ignite-with-java-9-10-11)
+GridGain uses proprietary SDK APIs that are not available by default. See also [How to run GridGain on JDK 9,10 and 11](https://docs.gridgain.com/docs/getting-started#section-running-gridgain-with-java-9-10-11)
To set up local IDE to easier access to examples, it is possible to add following options as default for all applications
@@ -16,8 +16,7 @@ To set up local IDE to easier access to examples, it is possible to add followin
--add-exports=java.management/com.sun.jmx.mbeanserver=ALL-UNNAMED
--add-exports=jdk.internal.jvmstat/sun.jvmstat.monitor=ALL-UNNAMED
--add-exports=java.base/sun.reflect.generics.reflectiveObjects=ALL-UNNAMED
- --illegal-access=permit
- -Djdk.tls.client.protocols=TLSv1.2``
+ --illegal-access=permit``
For example, for IntelliJ IDEA it is possible to use Application Templates.
@@ -28,7 +27,4 @@ Use 'Run' -> 'Edit Configuration' menu.
## Contributing to Examples
*Notice* When updating classpath of examples and in case any modifications required in [pom.xml](pom.xml)
please make sure that corresponding changes were applied to
- * [pom-standalone.xml](pom-standalone.xml),
- * [pom-standalone-lgpl.xml](pom-standalone-lgpl.xml).
-
- These pom files are finalized during release and placed to examples folder with these examples code.
\ No newline at end of file
+ [pom-standalone.xml](pom-standalone.xml). This pom file is finalized during release and placed to examples folder with these examples code.
\ No newline at end of file
diff --git a/examples/README.txt b/examples/README.txt
index abb5d23..64146a8 100644
--- a/examples/README.txt
+++ b/examples/README.txt
@@ -1,20 +1,20 @@
-Apache Ignite Examples
+GridGain Examples
======================
-This folder contains code examples for various Apache Ignite functionality.
+This folder contains code examples for various GridGain functionality.
Examples are shipped as a separate Maven project, so to start running you simply need
to import provided `pom.xml` file into your favourite IDE.
The examples folder contains he following subfolders:
-- `config` - contains Ignite configuration files needed for examples.
-- `memcached` - contains PHP script demonstrating how Ignite Cache can be accessed using Memcached client.
-- `rest` - contains PHP script demonstrating how Ignite Cache can be accessed via HTTP API.
+- `config` - contains GridGain configuration files needed for examples.
+- `memcached` - contains PHP script demonstrating how GridGain Cache can be accessed using Memcached client.
+- `rest` - contains PHP script demonstrating how GridGain Cache can be accessed via HTTP API.
- `sql` - contains sample SQL scripts and data sets.
-- `src/main/java` - contains Java examples for different Ignite modules and features.
+- `src/main/java` - contains Java examples for different GridGain modules and features.
- `src/main/scala` - contains examples demonstrating usage of API provided by Scalar.
-- `src/main/java-lgpl` - contains lgpl-based examples for different Ignite modules and features.
+- `src/main/java-lgpl` - contains lgpl-based examples for different GridGain modules and features.
Starting Remote Nodes
=====================
@@ -28,14 +28,13 @@ LGPL
LGPL examples can be activated by turning lgpl profile on.
lgpl profile required some lgpl-based libs, for example: ignite-hibernate & ignite-schedule.
-In case these libs can not be found by this maven project please download Apache Ignite sources
-at https://ignite.apache.org/download.cgi#sources.
+In case these libs can not be found by this maven project please download GridGain sources.
There are some ways to gain required libs from sources:
-1) Run "mvn clean install -DskipTests -P lgpl" at Apache Ignite sources.
+1) Run "mvn clean install -DskipTests -P lgpl" at GridGain sources.
This case will install lgpl-based libs to local maven repository.
-2) Run "mvn clean package -DskipTests -Prelease,lgpl -Dignite.edition=apache-ignite-lgpl" at Apache Ignite sources.
+2) Run "mvn clean package -DskipTests -Prelease,lgpl -Dignite.edition=apache-ignite-lgpl" at GridGain sources.
Required libs will appear at /target/release-package/libs/optional subfolders.
Found libs should be copied to global or project's classpath.
diff --git a/examples/config/filesystem/README.txt b/examples/config/filesystem/README.txt
index 4f6ae88..c06d1b8 100644
--- a/examples/config/filesystem/README.txt
+++ b/examples/config/filesystem/README.txt
@@ -4,5 +4,5 @@ FileSystem Configuration Example
This folder contains configuration files for IgniteFs examples located in
org.apache.ignite.examples.igfs package.
-- example-igfs.xml file is used to start Apache Ignite nodes with IgniteFS configured
+- example-igfs.xml file is used to start GridGain nodes with IgniteFS configured
- core-site.xml file is used to run Hadoop FS driver over IgniteFs
diff --git a/examples/config/hibernate/README.txt b/examples/config/hibernate/README.txt
index 5b7ab29..5cbf9b5 100644
--- a/examples/config/hibernate/README.txt
+++ b/examples/config/hibernate/README.txt
@@ -2,7 +2,7 @@ Hibernate L2 Cache Configuration Example
----------------------------------------
This folder contains example-hibernate-L2-cache.xml file that demonstrates
-how to configure Hibernate to use Apache Ignite cache as an L2 cache provider.
+how to configure Hibernate to use GridGain cache as an L2 cache provider.
This file is also used in Hibernate example located in org.apache.ignite.examples.datagrid.hibernate
package.
diff --git a/examples/config/servlet/README.txt b/examples/config/servlet/README.txt
index 20d4b90..46ea854 100644
--- a/examples/config/servlet/README.txt
+++ b/examples/config/servlet/README.txt
@@ -2,7 +2,7 @@ Servlet Configuration Example
-----------------------------
This folder contains web.xml file that demonstrates how to configure any servlet container
-to start a Apache Ignite node inside a Web application.
+to start a GridGain node inside a Web application.
For more information on available configuration properties, etc. refer to our documentation:
http://apacheignite.readme.io/docs/web-session-clustering
diff --git a/ipc/README.txt b/ipc/README.txt
index 3adc0dc..dadece2 100644
--- a/ipc/README.txt
+++ b/ipc/README.txt
@@ -1,4 +1,4 @@
-Apache Ignite IPC
+GridGain IPC
-------------------
-Contains different Inter-process communication (IPC) implementations for Apache Ignite.
+Contains different Inter-process communication (IPC) implementations for GridGain.
diff --git a/ipc/shmem/README.txt b/ipc/shmem/README.txt
index e11360b..7526897 100644
--- a/ipc/shmem/README.txt
+++ b/ipc/shmem/README.txt
@@ -1,7 +1,7 @@
-Apache Ignite Shared memory IPC library
+GridGain Shared memory IPC library
---------------------------------------
-Apache Ignite shared memory IPC library implement exchange via shared memory for Apache Ignite.
+GridGain shared memory IPC library implement exchange via shared memory for GridGain.
Building on Linux and Mac OS X
-------------------
@@ -22,12 +22,12 @@ to see all available command line options. Once the configure script finishes, y
This will build and install the shared memory library and the headers into the default location on your
system (which is usually '/usr/local').
-Usage with Apache Ignite
+Usage with GridGain
-------------------
Copy compiled library to folder that already listed in 'java.library.path'
with name in form: 'libigniteshmem-<ignite-version>.<extension>'.
-Note: Ignite should be restarted.
+Note: GridGain should be restarted.
**************************************************************************************
*** Additional notes:
diff --git a/modules/aop/README.txt b/modules/aop/README.txt
index 4d04630..a824d60 100644
--- a/modules/aop/README.txt
+++ b/modules/aop/README.txt
@@ -1,7 +1,7 @@
-Apache Ignite AOP Module
+GridGain AOP Module
------------------------
-Apache Ignite AOP module provides capability to turn any Java method to a distributed closure by
+GridGain AOP module provides capability to turn any Java method to a distributed closure by
adding @Gridify annotation to it.
To enable AOP module when starting a standalone node, move 'optional/ignite-aop' folder to
@@ -12,7 +12,7 @@ Importing AOP Module In Maven Project
-------------------------------------
If you are using Maven to manage dependencies of your project, you can add AOP module
-dependency like this (replace '${ignite.version}' with actual Ignite version you are
+dependency like this (replace '${ignite.version}' with actual GridGain version you are
interested in):
<project xmlns="http://maven.apache.org/POM/4.0.0"
@@ -23,7 +23,7 @@ interested in):
<dependencies>
...
<dependency>
- <groupId>org.apache.ignite</groupId>
+ <groupId>org.gridgain</groupId>
<artifactId>ignite-aop</artifactId>
<version>${ignite.version}</version>
</dependency>
diff --git a/modules/apache-license-gen/README.txt b/modules/apache-license-gen/README.txt
index 46f0be9..3b88115 100644
--- a/modules/apache-license-gen/README.txt
+++ b/modules/apache-license-gen/README.txt
@@ -1,16 +1,16 @@
-Apache Ignite License Generator Module
+GridGain License Generator Module
------------------------------
-Apache Ignite License Generator module is a custom maven resource plugin.
+GridGain License Generator module is a custom maven resource plugin.
It generates /license/{module name}-licenses.txt file contains list of module's non transitive dependencies.
-Apache Ignite binary distribution contains all non transitive dependencies of it's modules.
+GridGain binary distribution contains all non transitive dependencies of it's modules.
Set of modules included to binary distribution may vary as well as their dependencies list, versions and licenses.
Automatic generation of /license/{module name}-licenses.txt file guarantee that binary distribution gives user
-actual information about licenses used by Apache Ignite's modules.
+actual information about licenses used by GridGain's modules.
Note that in case dependency provided under Apache License 2.0 only in will not appear inside generated file.
-To use Apache Ignite License Generator Module in your project please add following to pom.xml:
+To use GridGain License Generator Module in your project please add following to pom.xml:
<plugin><!-- generates dependencies licenses -->
<groupId>org.apache.maven.plugins</groupId>
diff --git a/modules/aws/README.txt b/modules/aws/README.txt
index 1819915..d49b699 100644
--- a/modules/aws/README.txt
+++ b/modules/aws/README.txt
@@ -1,7 +1,7 @@
-Apache Ignite AWS Module
+GridGain AWS Module
------------------------
-Apache Ignite AWS module provides S3-based implementations of checkpoint SPI and IP finder for TCP discovery.
+GridGain AWS module provides S3-based implementations of checkpoint SPI and IP finder for TCP discovery.
To enable AWS module when starting a standalone node, move 'optional/ignite-aws' folder to
'libs' folder before running 'ignite.{sh|bat}' script. The content of the module folder will
@@ -11,7 +11,7 @@ Importing AWS Module In Maven Project
-------------------------------------
If you are using Maven to manage dependencies of your project, you can add AWS module
-dependency like this (replace '${ignite.version}' with actual Ignite version you are
+dependency like this (replace '${ignite.version}' with actual GridGain version you are
interested in):
<project xmlns="http://maven.apache.org/POM/4.0.0"
@@ -22,7 +22,7 @@ interested in):
<dependencies>
...
<dependency>
- <groupId>org.apache.ignite</groupId>
+ <groupId>org.gridgain</groupId>
<artifactId>ignite-aws</artifactId>
<version>${ignite.version}</version>
</dependency>
diff --git a/modules/camel/README.txt b/modules/camel/README.txt
index ca119ae..b6c7109 100644
--- a/modules/camel/README.txt
+++ b/modules/camel/README.txt
@@ -1,7 +1,7 @@
-Apache Ignite Camel Module
+GridGain Camel Module
--------------------------
-Apache Ignite Camel provides a streamer to consume cache tuples from a Camel endpoint such as
+GridGain Camel provides a streamer to consume cache tuples from a Camel endpoint such as
HTTP, TCP, File, FTP, AMQP, SNMP, databases, etc. For more information on available components,
refer to http://camel.apache.org/components.html.
@@ -13,7 +13,7 @@ Importing the Camel module in a Maven project
---------------------------------------------
If you are using Maven to manage dependencies of your project, you can add the Camel module
-dependency like this (replace '${ignite.version}' with actual Ignite version you are
+dependency like this (replace '${ignite.version}' with actual GridGain version you are
interested in):
<project xmlns="http://maven.apache.org/POM/4.0.0"
@@ -24,7 +24,7 @@ interested in):
<dependencies>
...
<dependency>
- <groupId>org.apache.ignite</groupId>
+ <groupId>org.gridgain</groupId>
<artifactId>ignite-camel</artifactId>
<version>${ignite.version}</version>
</dependency>
diff --git a/modules/cassandra/README.txt b/modules/cassandra/README.txt
index 146e5d4..a82007c 100644
--- a/modules/cassandra/README.txt
+++ b/modules/cassandra/README.txt
@@ -1,13 +1,13 @@
-Apache Ignite Cassandra Module
+GridGain Cassandra Module
------------------------
-Apache Ignite Cassandra module, used just as a parent container for other Cassandra related modules.
+GridGain Cassandra module, used just as a parent container for other Cassandra related modules.
Importing Cassandra Module In Maven Project
-------------------------------------
If you are using Maven to manage dependencies of your project, you can add Cassandra Store module
-dependency like this (replace '${ignite.version}' with actual Ignite version you are
+dependency like this (replace '${ignite.version}' with actual GridGain version you are
interested in):
<project xmlns="http://maven.apache.org/POM/4.0.0"
@@ -18,7 +18,7 @@ interested in):
<dependencies>
...
<dependency>
- <groupId>org.apache.ignite</groupId>
+ <groupId>org.gridgain</groupId>
<artifactId>ignite-cassandra</artifactId>
<version>${ignite.version}</version>
</dependency>
diff --git a/modules/cassandra/serializers/README.txt b/modules/cassandra/serializers/README.txt
index aaa309f..cedaf23 100644
--- a/modules/cassandra/serializers/README.txt
+++ b/modules/cassandra/serializers/README.txt
@@ -1,8 +1,8 @@
-Apache Ignite Cassandra Serializers Module
+GridGain Cassandra Serializers Module
------------------------
-Apache Ignite Cassandra Serializers module provides additional serializers to store objects as BLOBs in Cassandra. The
-module could be used as an addition to Ignite Cassandra Store module.
+GridGain Cassandra Serializers module provides additional serializers to store objects as BLOBs in Cassandra. The
+module could be used as an addition to GridGain Cassandra Store module.
To enable Cassandra Serializers module when starting a standalone node, move 'optional/ignite-cassandra-serializers'
folder to 'libs' folder before running 'ignite.{sh|bat}' script. The content of the module folder will be added to
@@ -13,7 +13,7 @@ Importing Cassandra Serializers Module In Maven Project
-------------------------------------
If you are using Maven to manage dependencies of your project, you can add Cassandra Store module
-dependency like this (replace '${ignite.version}' with actual Ignite version you are
+dependency like this (replace '${ignite.version}' with actual GridGain version you are
interested in):
<project xmlns="http://maven.apache.org/POM/4.0.0"
@@ -24,7 +24,7 @@ interested in):
<dependencies>
...
<dependency>
- <groupId>org.apache.ignite</groupId>
+ <groupId>org.gridgain</groupId>
<artifactId>ignite-cassandra-serializers</artifactId>
<version>${ignite.version}</version>
</dependency>
diff --git a/modules/cassandra/store/README.txt b/modules/cassandra/store/README.txt
index fd72dea..972912b 100644
--- a/modules/cassandra/store/README.txt
+++ b/modules/cassandra/store/README.txt
@@ -1,7 +1,7 @@
-Apache Ignite Cassandra Store Module
+GridGain Cassandra Store Module
------------------------
-Apache Ignite Cassandra Store module provides CacheStore implementation backed by Cassandra database.
+GridGain Cassandra Store module provides CacheStore implementation backed by Cassandra database.
To enable Cassandra Store module when starting a standalone node, move 'optional/ignite-cassandra-store' folder to
'libs' folder before running 'ignite.{sh|bat}' script. The content of the module folder will
@@ -11,7 +11,7 @@ Importing Cassandra Store Module In Maven Project
-------------------------------------
If you are using Maven to manage dependencies of your project, you can add Cassandra Store module
-dependency like this (replace '${ignite.version}' with actual Ignite version you are
+dependency like this (replace '${ignite.version}' with actual GridGain version you are
interested in):
<project xmlns="http://maven.apache.org/POM/4.0.0"
@@ -22,7 +22,7 @@ interested in):
<dependencies>
...
<dependency>
- <groupId>org.apache.ignite</groupId>
+ <groupId>org.gridgain</groupId>
<artifactId>ignite-cassandra-store</artifactId>
<version>${ignite.version}</version>
</dependency>
diff --git a/modules/cassandra/store/src/test/bootstrap/aws/README.txt b/modules/cassandra/store/src/test/bootstrap/aws/README.txt
index a61b235..548cbec 100644
--- a/modules/cassandra/store/src/test/bootstrap/aws/README.txt
+++ b/modules/cassandra/store/src/test/bootstrap/aws/README.txt
@@ -1,8 +1,8 @@
-Shell scripts to spin up Ignite, Cassandra and Load tests clusters in AWS.
+Shell scripts to spin up GridGain, Cassandra and Load tests clusters in AWS.
1) cassandra - bootstrap scripts for Cassandra cluster nodes
2) ganglia - bootstrap scripts for Ganglia master and agents
-3) ignite - bootstrap scripts for Ignite cluster nodes
+3) ignite - bootstrap scripts for GridGain cluster nodes
4) tests - bootstrap scripts for Load Tests cluster nodes
5) common.sh - definitions for common functions
6) env.sh - definitions for common variables
diff --git a/modules/clients/README.txt b/modules/clients/README.txt
index 8299c33..f63cdb4 100644
--- a/modules/clients/README.txt
+++ b/modules/clients/README.txt
@@ -1,9 +1,9 @@
Java Client README
==================
-Java Client is a lightweight gateway to Ignite nodes.
+Java Client is a lightweight gateway to GridGain nodes.
-Client communicates with grid nodes via REST interface and provides reduced but powerful subset of Ignite API.
-Java Client allows to use Ignite features from devices and environments where fully-functional Ignite node
+Client communicates with grid nodes via REST interface and provides reduced but powerful subset of GridGain API.
+Java Client allows to use GridGain features from devices and environments where fully-functional GridGain node
could not (or should not) be started.
Client vs Grid Node
diff --git a/modules/cloud/README.txt b/modules/cloud/README.txt
index c57a5da..dd92a12 100644
--- a/modules/cloud/README.txt
+++ b/modules/cloud/README.txt
@@ -1,7 +1,7 @@
-Apache Ignite Cloud Module
+GridGain Cloud Module
------------------------
-Apache Ignite Cloud module provides Apache jclouds implementations of IP finder for TCP discovery.
+GridGain Cloud module provides Apache jclouds implementations of IP finder for TCP discovery.
To enable Cloud module when starting a standalone node, move 'optional/ignite-cloud' folder to
'libs' folder before running 'ignite.{sh|bat}' script. The content of the module folder will
@@ -11,7 +11,7 @@ Importing Cloud Module In Maven Project
-------------------------------------
If you are using Maven to manage dependencies of your project, you can add Cloud module
-dependency like this (replace '${ignite.version}' with actual Ignite version you are
+dependency like this (replace '${ignite.version}' with actual GridGain version you are
interested in):
<project xmlns="http://maven.apache.org/POM/4.0.0"
@@ -22,7 +22,7 @@ interested in):
<dependencies>
...
<dependency>
- <groupId>org.apache.ignite</groupId>
+ <groupId>org.gridgain</groupId>
<artifactId>ignite-cloud</artifactId>
<version>${ignite.version}</version>
</dependency>
diff --git a/modules/compatibility/README.txt b/modules/compatibility/README.txt
index f2743ec..6c8b466 100644
--- a/modules/compatibility/README.txt
+++ b/modules/compatibility/README.txt
@@ -1,5 +1,5 @@
-Apache Ignite Compatibility Tests
+GridGain Compatibility Tests
------------------------
Special module contains testing framework which provides methods for testing backward compatibility.
-It allows to start Ignite-cluster in multiversion mode. It means that nodes with different build version is allowed to join topology.
\ No newline at end of file
+It allows to start GridGain-cluster in multiversion mode. It means that nodes with different build version is allowed to join topology.
\ No newline at end of file
diff --git a/modules/core/src/main/java/META-INF/LICENSE b/modules/core/src/main/java/META-INF/LICENSE
index c971434..4f2f7db 100644
--- a/modules/core/src/main/java/META-INF/LICENSE
+++ b/modules/core/src/main/java/META-INF/LICENSE
@@ -1,238 +1,13 @@
+Copyright 2019 GridGain Systems, Inc. and Contributors.
- Apache License
- Version 2.0, January 2004
- http://www.apache.org/licenses/
+Licensed under the GridGain Community Edition License (the "License");
+you may not use this file except in compliance with the License.
+You may obtain a copy of the License at
- TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+ https://www.gridgain.com/products/software/community-edition/gridgain-community-edition-license
- 1. Definitions.
-
- "License" shall mean the terms and conditions for use, reproduction,
- and distribution as defined by Sections 1 through 9 of this document.
-
- "Licensor" shall mean the copyright owner or entity authorized by
- the copyright owner that is granting the License.
-
- "Legal Entity" shall mean the union of the acting entity and all
- other entities that control, are controlled by, or are under common
- control with that entity. For the purposes of this definition,
- "control" means (i) the power, direct or indirect, to cause the
- direction or management of such entity, whether by contract or
- otherwise, or (ii) ownership of fifty percent (50%) or more of the
- outstanding shares, or (iii) beneficial ownership of such entity.
-
- "You" (or "Your") shall mean an individual or Legal Entity
- exercising permissions granted by this License.
-
- "Source" form shall mean the preferred form for making modifications,
- including but not limited to software source code, documentation
- source, and configuration files.
-
- "Object" form shall mean any form resulting from mechanical
- transformation or translation of a Source form, including but
- not limited to compiled object code, generated documentation,
- and conversions to other media types.
-
- "Work" shall mean the work of authorship, whether in Source or
- Object form, made available under the License, as indicated by a
- copyright notice that is included in or attached to the work
- (an example is provided in the Appendix below).
-
- "Derivative Works" shall mean any work, whether in Source or Object
- form, that is based on (or derived from) the Work and for which the
- editorial revisions, annotations, elaborations, or other modifications
- represent, as a whole, an original work of authorship. For the purposes
- of this License, Derivative Works shall not include works that remain
- separable from, or merely link (or bind by name) to the interfaces of,
- the Work and Derivative Works thereof.
-
- "Contribution" shall mean any work of authorship, including
- the original version of the Work and any modifications or additions
- to that Work or Derivative Works thereof, that is intentionally
- submitted to Licensor for inclusion in the Work by the copyright owner
- or by an individual or Legal Entity authorized to submit on behalf of
- the copyright owner. For the purposes of this definition, "submitted"
- means any form of electronic, verbal, or written communication sent
- to the Licensor or its representatives, including but not limited to
- communication on electronic mailing lists, source code control systems,
- and issue tracking systems that are managed by, or on behalf of, the
- Licensor for the purpose of discussing and improving the Work, but
- excluding communication that is conspicuously marked or otherwise
- designated in writing by the copyright owner as "Not a Contribution."
-
- "Contributor" shall mean Licensor and any individual or Legal Entity
- on behalf of whom a Contribution has been received by Licensor and
- subsequently incorporated within the Work.
-
- 2. Grant of Copyright License. Subject to the terms and conditions of
- this License, each Contributor hereby grants to You a perpetual,
- worldwide, non-exclusive, no-charge, royalty-free, irrevocable
- copyright license to reproduce, prepare Derivative Works of,
- publicly display, publicly perform, sublicense, and distribute the
- Work and such Derivative Works in Source or Object form.
-
- 3. Grant of Patent License. Subject to the terms and conditions of
- this License, each Contributor hereby grants to You a perpetual,
- worldwide, non-exclusive, no-charge, royalty-free, irrevocable
- (except as stated in this section) patent license to make, have made,
- use, offer to sell, sell, import, and otherwise transfer the Work,
- where such license applies only to those patent claims licensable
- by such Contributor that are necessarily infringed by their
- Contribution(s) alone or by combination of their Contribution(s)
- with the Work to which such Contribution(s) was submitted. If You
- institute patent litigation against any entity (including a
- cross-claim or counterclaim in a lawsuit) alleging that the Work
- or a Contribution incorporated within the Work constitutes direct
- or contributory patent infringement, then any patent licenses
- granted to You under this License for that Work shall terminate
- as of the date such litigation is filed.
-
- 4. Redistribution. You may reproduce and distribute copies of the
- Work or Derivative Works thereof in any medium, with or without
- modifications, and in Source or Object form, provided that You
- meet the following conditions:
-
- (a) You must give any other recipients of the Work or
- Derivative Works a copy of this License; and
-
- (b) You must cause any modified files to carry prominent notices
- stating that You changed the files; and
-
- (c) You must retain, in the Source form of any Derivative Works
- that You distribute, all copyright, patent, trademark, and
- attribution notices from the Source form of the Work,
- excluding those notices that do not pertain to any part of
- the Derivative Works; and
-
- (d) If the Work includes a "NOTICE" text file as part of its
- distribution, then any Derivative Works that You distribute must
- include a readable copy of the attribution notices contained
- within such NOTICE file, excluding those notices that do not
- pertain to any part of the Derivative Works, in at least one
- of the following places: within a NOTICE text file distributed
- as part of the Derivative Works; within the Source form or
- documentation, if provided along with the Derivative Works; or,
- within a display generated by the Derivative Works, if and
- wherever such third-party notices normally appear. The contents
- of the NOTICE file are for informational purposes only and
- do not modify the License. You may add Your own attribution
- notices within Derivative Works that You distribute, alongside
- or as an addendum to the NOTICE text from the Work, provided
- that such additional attribution notices cannot be construed
- as modifying the License.
-
- You may add Your own copyright statement to Your modifications and
- may provide additional or different license terms and conditions
- for use, reproduction, or distribution of Your modifications, or
- for any such Derivative Works as a whole, provided Your use,
- reproduction, and distribution of the Work otherwise complies with
- the conditions stated in this License.
-
- 5. Submission of Contributions. Unless You explicitly state otherwise,
- any Contribution intentionally submitted for inclusion in the Work
- by You to the Licensor shall be under the terms and conditions of
- this License, without any additional terms or conditions.
- Notwithstanding the above, nothing herein shall supersede or modify
- the terms of any separate license agreement you may have executed
- with Licensor regarding such Contributions.
-
- 6. Trademarks. This License does not grant permission to use the trade
- names, trademarks, service marks, or product names of the Licensor,
- except as required for reasonable and customary use in describing the
- origin of the Work and reproducing the content of the NOTICE file.
-
- 7. Disclaimer of Warranty. Unless required by applicable law or
- agreed to in writing, Licensor provides the Work (and each
- Contributor provides its Contributions) on an "AS IS" BASIS,
- WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
- implied, including, without limitation, any warranties or conditions
- of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
- PARTICULAR PURPOSE. You are solely responsible for determining the
- appropriateness of using or redistributing the Work and assume any
- risks associated with Your exercise of permissions under this License.
-
- 8. Limitation of Liability. In no event and under no legal theory,
- whether in tort (including negligence), contract, or otherwise,
- unless required by applicable law (such as deliberate and grossly
- negligent acts) or agreed to in writing, shall any Contributor be
- liable to You for damages, including any direct, indirect, special,
- incidental, or consequential damages of any character arising as a
- result of this License or out of the use or inability to use the
- Work (including but not limited to damages for loss of goodwill,
- work stoppage, computer failure or malfunction, or any and all
- other commercial damages or losses), even if such Contributor
- has been advised of the possibility of such damages.
-
- 9. Accepting Warranty or Additional Liability. While redistributing
- the Work or Derivative Works thereof, You may choose to offer,
- and charge a fee for, acceptance of support, warranty, indemnity,
- or other liability obligations and/or rights consistent with this
- License. However, in accepting such obligations, You may act only
- on Your own behalf and on Your sole responsibility, not on behalf
- of any other Contributor, and only if You agree to indemnify,
- defend, and hold each Contributor harmless for any liability
- incurred by, or claims asserted against, such Contributor by reason
- of your accepting any such warranty or additional liability.
-
- END OF TERMS AND CONDITIONS
-
- APPENDIX: How to apply the Apache License to your work.
-
- To apply the Apache License to your work, attach the following
- boilerplate notice, with the fields enclosed by brackets "[]"
- replaced with your own identifying information. (Don't include
- the brackets!) The text should be enclosed in the appropriate
- comment syntax for the file format. We also recommend that a
- file or class name and description of purpose be included on the
- same "printed page" as the copyright notice for easier
- identification within third-party archives.
-
- Copyright [yyyy] [name of copyright owner]
-
- Licensed under the Apache License, Version 2.0 (the "License");
- you may not use this file except in compliance with the License.
- You may obtain a copy of the License at
-
- http://www.apache.org/licenses/LICENSE-2.0
-
- Unless required by applicable law or agreed to in writing, software
- distributed under the License is distributed on an "AS IS" BASIS,
- WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
- See the License for the specific language governing permissions and
- limitations under the License.
-
-
-
-==============================================================================
-Apache Ignite Subcomponents:
-
-The Apache Ignite project contains subcomponents with separate copyright
-notices and license terms. Your use of the source code for the these
-subcomponents is subject to the terms and conditions of the following
-licenses.
-
-
-==============================================================================
-For SnapTree:
-==============================================================================
-This product bundles SnapTree, which is available under a
-"3-clause BSD" license. For details, see
-https://github.com/nbronson/snaptree/blob/master/LICENSE.
-
-==============================================================================
-For JSR 166 classes in "org.jsr166" package
-==============================================================================
-This product bundles JSR-166 classes which are donated to public domain.
-For details, see CC0 1.0 Universal (1.0), Public Domain Dedication,
-http://creativecommons.org/publicdomain/zero/1.0/
-
-==============================================================================
-For books used for tests in "org.apache.ignite.internal.processors.hadoop.books"
-==============================================================================
-This code bundles book text files used for testing purposes which contain
-the following header:
-
-This eBook is for the use of anyone anywhere at no cost and with
-almost no restrictions whatsoever. You may copy it, give it away or
-re-use it under the terms of the Project Gutenberg License included
-with this eBook or online at www.gutenberg.org
+Unless required by applicable law or agreed to in writing, software
+distributed under the License is distributed on an "AS IS" BASIS,
+WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+See the License for the specific language governing permissions and
+limitations under the License.
\ No newline at end of file
diff --git a/modules/core/src/main/java/META-INF/NOTICE b/modules/core/src/main/java/META-INF/NOTICE
index 0bae434..62c5414 100644
--- a/modules/core/src/main/java/META-INF/NOTICE
+++ b/modules/core/src/main/java/META-INF/NOTICE
@@ -1,5 +1,5 @@
-Apache Ignite
-Copyright 2019 The Apache Software Foundation
+GridGain
+Copyright 2019 GridGain Systems
This product includes software developed at
The Apache Software Foundation (http://www.apache.org/).
diff --git a/modules/dev-utils/README.txt b/modules/dev-utils/README.txt
index f839c4f..e10baad 100644
--- a/modules/dev-utils/README.txt
+++ b/modules/dev-utils/README.txt
@@ -1,5 +1,5 @@
-Apache Ignite Development Utils
+GridGain Development Utils
------------------------
-Special module contains Ignite development utilities. These utilities may be useful when analyzing PDS artifacts,
+Special module contains GridGain development utilities. These utilities may be useful when analyzing PDS artifacts,
such as WAL or page storage, in field deployments.
diff --git a/modules/direct-io/README.txt b/modules/direct-io/README.txt
index 95d4401..f7d2582 100644
--- a/modules/direct-io/README.txt
+++ b/modules/direct-io/README.txt
@@ -1,20 +1,20 @@
-Apache Ignite Direct IO Module
+GridGain Direct IO Module
-------------------------------------
-Apache Ignite Direct IO is plugin, which provides page store with ability to write and read cache partitions
+GridGain Direct IO is plugin, which provides page store with ability to write and read cache partitions
in O_DIRECT mode.
OS gets the data and stores it in a file buffer cache. Similarly, for every write operation,
the OS first writes the data in a cache and then transfers to the disk. To eliminate this process you can enable
Direct I/O in which case the data is read and written directly from/to the disk bypassing the file buffer cache.
-Direct I/O plugin in Ignite is used for the checkpointing process where the dirty pages in RAM are written to the disk.
+Direct I/O plugin in GridGain is used for the checkpointing process where the dirty pages in RAM are written to the disk.
Importing Direct I/O Pluging In Maven Project
-------------------------------------
If you are using Maven to manage dependencies of your project, you can add Direct IO Module
-dependency like this (replace '${ignite.version}' with actual Ignite version you are
+dependency like this (replace '${ignite.version}' with actual GridGain version you are
interested in):
<project xmlns="http://maven.apache.org/POM/4.0.0"
@@ -25,7 +25,7 @@ interested in):
<dependencies>
...
<dependency>
- <groupId>org.apache.ignite</groupId>
+ <groupId>org.gridgain</groupId>
<artifactId>ignite-direct-io</artifactId>
<version>${ignite.version}</version>
</dependency>
@@ -36,14 +36,14 @@ interested in):
Importing Direct I/O Pluging In Gradle Project
-------------------------------------
-For gradle you can add compile dependency, where igniteVersion is actual Ignite version:
+For gradle you can add compile dependency, where igniteVersion is actual GridGain version:
-compile group: 'org.apache.ignite', name: 'ignite-direct-io', version: igniteVersion
+compile group: 'org.gridgain', name: 'ignite-direct-io', version: igniteVersion
Additional setup is not required. Once plugin is available in classpath, it will be used for Durable Memory IO.
-------------------------------------
-See more information in Apache Ignite documentation:
+See more information in GridGain documentation:
https://apacheignite.readme.io/docs/durable-memory-tuning#section-enabling-direct-i-o
and description of internal desing can be found in Wiki:
diff --git a/modules/extdata/platform/README.txt b/modules/extdata/platform/README.txt
index cb583ca..d39d9e7 100644
--- a/modules/extdata/platform/README.txt
+++ b/modules/extdata/platform/README.txt
@@ -1,4 +1,4 @@
-Apache Ignite Platform Tests
+GridGain Platform Tests
------------------------
Special module for platform tests.
diff --git a/modules/flink/README.txt b/modules/flink/README.txt
index a198b1b..449e2db 100644
--- a/modules/flink/README.txt
+++ b/modules/flink/README.txt
@@ -1,14 +1,14 @@
-Apache Ignite Flink Sink Module
+GridGain Flink Sink Module
-----------------------------------
-Apache Ignite Flink Sink module is a streaming connector to inject Flink data into Ignite cache.
+GridGain Flink Sink module is a streaming connector to inject Flink data into GridGain cache.
-Starting data transfer to Ignite can be done with the following steps.
+Starting data transfer to GridGain can be done with the following steps.
-1. Import Ignite Flink Sink Module in Maven Project
+1. Import GridGain Flink Sink Module in Maven Project
If you are using Maven to manage dependencies of your project, you can add Flink module
-dependency like this (replace '${ignite.version}' with actual Ignite version you are
+dependency like this (replace '${ignite.version}' with actual GridGain version you are
interested in):
<project xmlns="http://maven.apache.org/POM/4.0.0"
@@ -19,7 +19,7 @@ interested in):
<dependencies>
...
<dependency>
- <groupId>org.apache.ignite</groupId>
+ <groupId>org.gridgain</groupId>
<artifactId>ignite-flink</artifactId>
<version>${ignite.version}</version>
</dependency>
@@ -28,6 +28,6 @@ interested in):
...
</project>
-2. Create an Ignite configuration file (see example-ignite.xml) and make sure it is accessible from the sink.
+2. Create an GridGain configuration file (see example-ignite.xml) and make sure it is accessible from the sink.
3. Make sure your data input to the sink is specified. For example `input.addSink(igniteSinkObject)`
diff --git a/modules/flume/README.txt b/modules/flume/README.txt
index adcd021..ff34d68 100644
--- a/modules/flume/README.txt
+++ b/modules/flume/README.txt
@@ -1,7 +1,7 @@
-Apache Ignite Flume Sink Module
+GridGain Flume Sink Module
-------------------------------
-IgniteSink is a Flume sink that extracts Events from an associated Flume channel and injects into an Ignite cache.
+IgniteSink is a Flume sink that extracts Events from an associated Flume channel and injects into an GridGain cache.
Flume 1.7.0 is supported.
IgniteSink, which can be found in 'optional/ignite-flume', and its dependencies have to be included in the agent's classpath,
@@ -12,7 +12,7 @@ as described in the following subsection, before starting the Flume agent.
1. Create a transformer by implementing EventTransformer interface.
2. Create 'ignite' directory inside plugins.d directory which is located in ${FLUME_HOME}. If the plugins.d directory is not there, create it.
3. Build it and copy to ${FLUME_HOME}/plugins.d/ignite-sink/lib.
-4. Copy other Ignite-related jar files from Apache Ignite distribution to ${FLUME_HOME}/plugins.d/ignite-sink/libext to have them as shown below.
+4. Copy other GridGain-related jar files from GridGain distribution to ${FLUME_HOME}/plugins.d/ignite-sink/libext to have them as shown below.
```
plugins.d/
@@ -31,9 +31,9 @@ plugins.d/
`-- spring-expression-4.1.0.RELEASE.jar
```
-4. In Flume configuration file, specify Ignite configuration XML file's location with cache properties
+4. In Flume configuration file, specify GridGain configuration XML file's location with cache properties
(see [Apache Ignite](https://apacheignite.readme.io/) with cache name specified for cache creation,
-cache name (same as in Ignite configuration file), your EventTransformer's implementation class,
+cache name (same as in GridGain configuration file), your EventTransformer's implementation class,
and, optionally, batch size (default -- 100).
```
diff --git a/modules/gce/README.txt b/modules/gce/README.txt
index 22c0cb9..860603d 100644
--- a/modules/gce/README.txt
+++ b/modules/gce/README.txt
@@ -1,7 +1,7 @@
-Apache Ignite GCE Module
+GridGain GCE Module
------------------------
-Apache Ignite GCE module provides Google Cloud Storage based implementations of IP finder for TCP discovery.
+GridGain GCE module provides Google Cloud Storage based implementations of IP finder for TCP discovery.
To enable GCE module when starting a standalone node, move 'optional/ignite-gce' folder to
'libs' folder before running 'ignite.{sh|bat}' script. The content of the module folder will
@@ -11,7 +11,7 @@ Importing GCE Module In Maven Project
-------------------------------------
If you are using Maven to manage dependencies of your project, you can add GCE module
-dependency like this (replace '${ignite.version}' with actual Ignite version you are
+dependency like this (replace '${ignite.version}' with actual GridGain version you are
interested in):
<project xmlns="http://maven.apache.org/POM/4.0.0"
@@ -22,7 +22,7 @@ interested in):
<dependencies>
...
<dependency>
- <groupId>org.apache.ignite</groupId>
+ <groupId>org.gridgain</groupId>
<artifactId>ignite-gce</artifactId>
<version>${ignite.version}</version>
</dependency>
diff --git a/modules/geospatial/README.txt b/modules/geospatial/README.txt
index 59143a0..fcfbf74 100644
--- a/modules/geospatial/README.txt
+++ b/modules/geospatial/README.txt
@@ -1,18 +1,18 @@
-Apache Ignite Geospatial Module
+GridGain Geospatial Module
-----------------------------
-Apache Ignite geospatial module provides capabilities to geospatial index cache type.
+GridGain geospatial module provides capabilities to geospatial index cache type.
To enable geospatial module when starting a standalone node, move 'optional/ignite-geospatial' folder to
'libs' folder before running 'ggstart.{sh|bat}' script. The content of the module folder will
be added to classpath in this case.
-Note! This module can be used only when Ignite indexing module is enabled.
+Note! This module can be used only when GridGain indexing module is enabled.
Importing geospatial Module In Maven Project
------------------------------------------
If you are using Maven to manage dependencies of your project, you can add geospatial module
-dependency like this (replace '${ignite.version}' with actual Ignite version you are
+dependency like this (replace '${ignite.version}' with actual GridGain version you are
interested in):
<project xmlns="http://maven.apache.org/POM/4.0.0"
@@ -23,7 +23,7 @@ interested in):
<dependencies>
...
<dependency>
- <groupId>org.apache.ignite</groupId>
+ <groupId>org.gridgain</groupId>
<artifactId>ignite-geospatial</artifactId>
<version>${ignite.version}</version>
</dependency>
@@ -36,13 +36,13 @@ interested in):
LGPL dependencies
-----------------
-Ignite includes the following optional LGPL dependencies:
+GridGain includes the following optional LGPL dependencies:
- Hibernate L2 Cache Integration, http://hibernate.org/orm/
- JTS Topology Suite for Geospatial indexing, http://tsusiatsoftware.net/jts/main.html
- cron4j for cron-based task scheduling, http://www.sauronsoftware.it/projects/cron4j
-Apache binary releases cannot include LGPL dependencies. If you would like include
+GridGain binary releases cannot include LGPL dependencies. If you would like include
optional LGPL dependencies into your release, you should download the source release
-from Ignite website and do the build with the following maven command:
+from GridGain website and do the build with the following maven command:
mvn clean package -DskipTests -Prelease,lgpl
diff --git a/modules/hadoop/README.txt b/modules/hadoop/README.txt
index ecd47e0..1d4860c 100644
--- a/modules/hadoop/README.txt
+++ b/modules/hadoop/README.txt
@@ -1,7 +1,7 @@
-Apache Ignite Hadoop Module
+GridGain Hadoop Module
---------------------------
-Apache Ignite Hadoop module provides In-Memory MapReduce engine and driver to use IGFS as Hadoop file system
+GridGain Hadoop module provides In-Memory MapReduce engine and driver to use IGFS as Hadoop file system
which are 100% compatible with HDFS and YARN.
To enable Hadoop module when starting a standalone node, move 'optional/ignite-hadoop' folder to
@@ -12,7 +12,7 @@ Importing Hadoop Module In Maven Project
----------------------------------------
If you are using Maven to manage dependencies of your project, you can add Hadoop module
-dependency like this (replace '${ignite.version}' with actual Ignite version you are
+dependency like this (replace '${ignite.version}' with actual GridGain version you are
interested in):
<project xmlns="http://maven.apache.org/POM/4.0.0"
@@ -23,7 +23,7 @@ interested in):
<dependencies>
...
<dependency>
- <groupId>org.apache.ignite</groupId>
+ <groupId>org.gridgain</groupId>
<artifactId>ignite-hadoop</artifactId>
<version>${ignite.version}</version>
</dependency>
diff --git a/modules/hibernate-4.2/README.txt b/modules/hibernate-4.2/README.txt
index 096b9d7..85bc95b 100644
--- a/modules/hibernate-4.2/README.txt
+++ b/modules/hibernate-4.2/README.txt
@@ -1,8 +1,8 @@
-Apache Ignite Hibernate Module
+GridGain Hibernate Module
------------------------------
-Apache Ignite Hibernate module provides Hibernate second-level cache (L2 cache) implementation based
-on Apache Ignite In-Memory Data Grid.
+GridGain Hibernate module provides Hibernate second-level cache (L2 cache) implementation based
+on GridGain In-Memory Data Grid.
To enable Hibernate module when starting a standalone node, move 'optional/ignite-hibernate' folder to
'libs' folder before running 'ignite.{sh|bat}' script. The content of the module folder will
@@ -12,7 +12,7 @@ Importing Hibernate Module In Maven Project
-------------------------------------------
If you are using Maven to manage dependencies of your project, you can add Hibernate module
-dependency like this (replace '${ignite.version}' with actual Ignite version you are
+dependency like this (replace '${ignite.version}' with actual GridGain version you are
interested in):
<project xmlns="http://maven.apache.org/POM/4.0.0"
@@ -23,7 +23,7 @@ interested in):
<dependencies>
...
<dependency>
- <groupId>org.apache.ignite</groupId>
+ <groupId>org.gridgain</groupId>
<artifactId>ignite-hibernate_4.2</artifactId>
<version>${ignite.version}</version>
</dependency>
@@ -36,13 +36,13 @@ interested in):
LGPL dependencies
-----------------
-Ignite includes the following optional LGPL dependencies:
+GridGain includes the following optional LGPL dependencies:
- Hibernate L2 Cache Integration, http://hibernate.org/orm/
- JTS Topology Suite for Geospatial indexing, http://tsusiatsoftware.net/jts/main.html
- cron4j for cron-based task scheduling, http://www.sauronsoftware.it/projects/cron4j
-Apache binary releases cannot include LGPL dependencies. If you would like include
+GridGain binary releases cannot include LGPL dependencies. If you would like include
optional LGPL dependencies into your release, you should download the source release
-from Ignite website and do the build with the following maven command:
+from GridGain website and do the build with the following maven command:
mvn clean package -DskipTests -Prelease,lgpl
diff --git a/modules/hibernate-5.1/README.txt b/modules/hibernate-5.1/README.txt
index 53c5d18..e9d3ae0 100644
--- a/modules/hibernate-5.1/README.txt
+++ b/modules/hibernate-5.1/README.txt
@@ -1,8 +1,8 @@
-Apache Ignite Hibernate Module
+GridGain Hibernate Module
------------------------------
-Apache Ignite Hibernate module provides Hibernate second-level cache (L2 cache) implementation based
-on Apache Ignite In-Memory Data Grid.
+GridGain Hibernate module provides Hibernate second-level cache (L2 cache) implementation based
+on GridGain In-Memory Data Grid.
To enable Hibernate module when starting a standalone node, move 'optional/ignite-hibernate5' folder to
'libs' folder before running 'ignite.{sh|bat}' script. The content of the module folder will
@@ -12,7 +12,7 @@ Importing Hibernate Module In Maven Project
-------------------------------------------
If you are using Maven to manage dependencies of your project, you can add Hibernate module
-dependency like this (replace '${ignite.version}' with actual Ignite version you are
+dependency like this (replace '${ignite.version}' with actual GridGain version you are
interested in):
<project xmlns="http://maven.apache.org/POM/4.0.0"
@@ -23,7 +23,7 @@ interested in):
<dependencies>
...
<dependency>
- <groupId>org.apache.ignite</groupId>
+ <groupId>org.gridgain</groupId>
<artifactId>ignite-hibernate_5.1</artifactId>
<version>${ignite.version}</version>
</dependency>
@@ -36,13 +36,13 @@ interested in):
LGPL dependencies
-----------------
-Ignite includes the following optional LGPL dependencies:
+GridGain includes the following optional LGPL dependencies:
- Hibernate L2 Cache Integration, http://hibernate.org/orm/
- JTS Topology Suite for Geospatial indexing, http://tsusiatsoftware.net/jts/main.html
- cron4j for cron-based task scheduling, http://www.sauronsoftware.it/projects/cron4j
-Apache binary releases cannot include LGPL dependencies. If you would like include
+GridGain binary releases cannot include LGPL dependencies. If you would like include
optional LGPL dependencies into your release, you should download the source release
-from Ignite website and do the build with the following maven command:
+from GridGain website and do the build with the following maven command:
mvn clean package -DskipTests -Prelease,lgpl
diff --git a/modules/ignored-tests/README.txt b/modules/ignored-tests/README.txt
index 70f728d..f8feea0 100644
--- a/modules/ignored-tests/README.txt
+++ b/modules/ignored-tests/README.txt
@@ -1,4 +1,4 @@
-Apache Ignite Ignored Tests
+GridGain Ignored Tests
------------------------
Special module containing ignored and flaky tests grouped in a single test suite.
\ No newline at end of file
diff --git a/modules/indexing/README.txt b/modules/indexing/README.txt
index f0ea6ba..fa5aff5 100644
--- a/modules/indexing/README.txt
+++ b/modules/indexing/README.txt
@@ -1,7 +1,7 @@
-Apache Ignite Indexing Module
+GridGain Indexing Module
-----------------------------
-Apache Ignite indexing module provides capabilities to index cache context and run SQL, full text or
+GridGain indexing module provides capabilities to index cache context and run SQL, full text or
individual field queries against these indexes.
To enable indexing module when starting a standalone node, move 'optional/ignite-indexing' folder to
@@ -12,7 +12,7 @@ Importing indexing Module In Maven Project
------------------------------------------
If you are using Maven to manage dependencies of your project, you can add indexing module
-dependency like this (replace '${ignite.version}' with actual Ignite version you are
+dependency like this (replace '${ignite.version}' with actual GridGain version you are
interested in):
<project xmlns="http://maven.apache.org/POM/4.0.0"
@@ -23,7 +23,7 @@ interested in):
<dependencies>
...
<dependency>
- <groupId>org.apache.ignite</groupId>
+ <groupId>org.gridgain</groupId>
<artifactId>ignite-indexing</artifactId>
<version>${ignite.version}</version>
</dependency>
diff --git a/modules/jcl/README.txt b/modules/jcl/README.txt
index ac37421..ece38bf 100644
--- a/modules/jcl/README.txt
+++ b/modules/jcl/README.txt
@@ -1,7 +1,7 @@
-Apache Ignite JCL Module
+GridGain JCL Module
------------------------
-Apache Ignite JCL module provides GridLogger implementation that can delegate to any logger based
+GridGain JCL module provides GridLogger implementation that can delegate to any logger based
on Jakarta Commons Logging (JCL).
To enable JCL module when starting a standalone node, move 'optional/ignite-jcl' folder to
@@ -12,7 +12,7 @@ Importing JCL Module In Maven Project
-------------------------------------
If you are using Maven to manage dependencies of your project, you can add JCL module
-dependency like this (replace '${ignite.version}' with actual Ignite version you are
+dependency like this (replace '${ignite.version}' with actual GridGain version you are
interested in):
<project xmlns="http://maven.apache.org/POM/4.0.0"
@@ -23,7 +23,7 @@ interested in):
<dependencies>
...
<dependency>
- <groupId>org.apache.ignite</groupId>
+ <groupId>org.gridgain</groupId>
<artifactId>ignite-jcl</artifactId>
<version>${ignite.version}</version>
</dependency>
diff --git a/modules/jms11/README.txt b/modules/jms11/README.txt
index 3f0d213..55654b6 100644
--- a/modules/jms11/README.txt
+++ b/modules/jms11/README.txt
@@ -1,14 +1,14 @@
-Apache Ignite JMS 1.1 Module
+GridGain JMS 1.1 Module
----------------------------
-Apache Ignite JMS 1.1 module provides a streamer to consume JMS queue and topic messages into
-Apache Ignite caches.
+GridGain JMS 1.1 module provides a streamer to consume JMS queue and topic messages into
+GridGain caches.
-Importing Apache Ignite JMS 1.1 Module In Maven Project
+Importing GridGain JMS 1.1 Module In Maven Project
--------------------------------------------------------
If you are using Maven to manage dependencies of your project, you can add the JMS 1.1 module
-dependency like this (replace '${ignite.version}' with actual Ignite version you are
+dependency like this (replace '${ignite.version}' with actual GridGain version you are
interested in):
<project xmlns="http://maven.apache.org/POM/4.0.0"
@@ -19,7 +19,7 @@ interested in):
<dependencies>
...
<dependency>
- <groupId>org.apache.ignite</groupId>
+ <groupId>org.gridgain</groupId>
<artifactId>ignite-jms11</artifactId>
<version>${ignite.version}</version>
</dependency>
diff --git a/modules/jta/README.txt b/modules/jta/README.txt
index c6c08b2a..6a8913f 100644
--- a/modules/jta/README.txt
+++ b/modules/jta/README.txt
@@ -1,7 +1,7 @@
-Apache Ignite JTA Module
+GridGain JTA Module
------------------------
-Apache Ignite JTA module provides capabilities to integrate Apache Ignite cache transactions with JTA.
+GridGain JTA module provides capabilities to integrate GridGain cache transactions with JTA.
To enable JTA module when starting a standalone node, move 'optional/ignite-jta' folder to
'libs' folder before running 'ignite.{sh|bat}' script. The content of the module folder will
@@ -11,7 +11,7 @@ Importing JTA Module In Maven Project
-------------------------------------
If you are using Maven to manage dependencies of your project, you can add JTA module
-dependency like this (replace '${ignite.version}' with actual Ignite version you are
+dependency like this (replace '${ignite.version}' with actual GridGain version you are
interested in):
<project xmlns="http://maven.apache.org/POM/4.0.0"
@@ -22,7 +22,7 @@ interested in):
<dependencies>
...
<dependency>
- <groupId>org.apache.ignite</groupId>
+ <groupId>org.gridgain</groupId>
<artifactId>ignite-jta</artifactId>
<version>${ignite.version}</version>
</dependency>
diff --git a/modules/kafka/README.txt b/modules/kafka/README.txt
index 686c7ce..d04f338 100644
--- a/modules/kafka/README.txt
+++ b/modules/kafka/README.txt
@@ -1,7 +1,7 @@
-Apache Ignite Kafka Streamer Module
+GridGain Kafka Streamer Module
-----------------------------------
-Apache Ignite Kafka Streamer module provides streaming from Kafka to Ignite cache.
+GridGain Kafka Streamer module provides streaming from Kafka to GridGain cache.
There are two ways this can be achieved:
- importing Kafka Streamer module in your Maven project and instantiate KafkaStreamer for data streaming;
@@ -9,10 +9,10 @@ There are two ways this can be achieved:
Below are the details.
-## Importing Ignite Kafka Streamer Module In Maven Project
+## Importing GridGain Kafka Streamer Module In Maven Project
If you are using Maven to manage dependencies of your project, you can add Kafka module
-dependency like this (replace '${ignite.version}' with actual Ignite version you are
+dependency like this (replace '${ignite.version}' with actual GridGain version you are
interested in):
<project xmlns="http://maven.apache.org/POM/4.0.0"
@@ -23,7 +23,7 @@ interested in):
<dependencies>
...
<dependency>
- <groupId>org.apache.ignite</groupId>
+ <groupId>org.gridgain</groupId>
<artifactId>ignite-kafka</artifactId>
<version>${ignite.version}</version>
</dependency>
@@ -33,9 +33,9 @@ interested in):
</project>
-## Streaming Data to Ignite via Kafka Connect
+## Streaming Data to GridGain via Kafka Connect
-Sink Connector will help you export data from Kafka to Ignite cache. It polls data from Kafka topics and writes it to the user-specified cache.
+Sink Connector will help you export data from Kafka to GridGain cache. It polls data from Kafka topics and writes it to the user-specified cache.
For more information on Kafka Connect, see [Kafka Documentation](http://kafka.apache.org/documentation.html#connect).
Connector can be found in 'optional/ignite-kafka.' It and its dependencies have to be on the classpath of a Kafka running instance,
@@ -93,7 +93,7 @@ where 'cacheName' is the name of the cache you specify in '/some-path/ignite.xml
will be pulled and stored. 'cacheAllowOverwrite' is set to true if you want to enable overwriting existing values in cache.
You can also set 'cachePerNodeDataSize' and 'cachePerNodeParOps' to adjust per-node buffer and the maximum number
of parallel stream operations for a single node.
-If you need to create an Ignite key from a Kafka value, implement StreamSingleTupleExtractor and specify it as 'singleTupleExtractorCls'.
+If you need to create an GridGain key from a Kafka value, implement StreamSingleTupleExtractor and specify it as 'singleTupleExtractorCls'.
See example-ignite.xml in tests for a simple cache configuration file example.
@@ -134,7 +134,7 @@ http://node1:8080/ignite?cmd=size&cacheName=cache1
## Streaming Cache Event Data to Kafka via Kafka Connect
-Source connector enables listening to Ignite cache events and, upon filtering, stream them to Kafka.
+Source connector enables listening to GridGain cache events and, upon filtering, stream them to Kafka.
Connector can be found in 'optional/ignite-kafka.' It and its dependencies have to be on the classpath of a Kafka running instance,
as described in the following subsection.
@@ -191,7 +191,7 @@ igniteCfg=/some-path/ignite.xml
```
where 'cacheName' is the name of the cache you specify in '/some-path/ignite.xml' and the data from 'testTopic1,testTopic2'
will be pulled and stored. Also consider using 'evtBufferSize' and 'evtBatchSize' for tuning the internal queue
-used to safely transfer data from Ignite cache to Kafka.
+used to safely transfer data from GridGain cache to Kafka.
The following cache events can be specified in the connector configurations:
- CREATED
diff --git a/modules/kubernetes/README.txt b/modules/kubernetes/README.txt
index a9a5a09..e8b3f8f 100644
--- a/modules/kubernetes/README.txt
+++ b/modules/kubernetes/README.txt
@@ -1,8 +1,8 @@
-Apache Ignite Kubernetes Module
+GridGain Kubernetes Module
------------------------
-Apache Ignite Kubernetes module provides a TCP Discovery IP Finder that uses a dedicated Kubernetes service
-for IP addresses lookup of Apache Ignite pods containerized by Kubernetes.
+GridGain Kubernetes module provides a TCP Discovery IP Finder that uses a dedicated Kubernetes service
+for IP addresses lookup of GridGain pods containerized by Kubernetes.
To enable Kubernetes module when starting a standalone node, move 'optional/ignite-kubernetes' folder to
'libs' folder before running 'ignite.{sh|bat}' script. The content of the module folder will
@@ -12,7 +12,7 @@ Importing Kubernetes Module In Maven Project
-------------------------------------
If you are using Maven to manage dependencies of your project, you can add Kubernetes module
-dependency like this (replace '${ignite.version}' with actual Ignite version you are
+dependency like this (replace '${ignite.version}' with actual GridGain version you are
interested in):
<project xmlns="http://maven.apache.org/POM/4.0.0"
@@ -23,7 +23,7 @@ interested in):
<dependencies>
...
<dependency>
- <groupId>org.apache.ignite</groupId>
+ <groupId>org.gridgain</groupId>
<artifactId>ignite-kubernetes</artifactId>
<version>${ignite.version}</version>
</dependency>
diff --git a/modules/log4j/README.txt b/modules/log4j/README.txt
index 4bd1b4b..b78db7e 100644
--- a/modules/log4j/README.txt
+++ b/modules/log4j/README.txt
@@ -1,7 +1,7 @@
-Apache Ignite Log4J Module
+GridGain Log4J Module
--------------------------
-Apache Ignite Log4J module provides IgniteLogger implementation based on Apache Log4J.
+GridGain Log4J module provides IgniteLogger implementation based on Apache Log4J.
To enable Log4J module when starting a standalone node, move 'optional/ignite-log4j' folder to
'libs' folder before running 'ignite.{sh|bat}' script. The content of the module folder will
@@ -11,7 +11,7 @@ Importing Log4J Module In Maven Project
---------------------------------------
If you are using Maven to manage dependencies of your project, you can add Log4J module
-dependency like this (replace '${ignite.version}' with actual Ignite version you are
+dependency like this (replace '${ignite.version}' with actual GridGain version you are
interested in):
<project xmlns="http://maven.apache.org/POM/4.0.0"
@@ -22,7 +22,7 @@ interested in):
<dependencies>
...
<dependency>
- <groupId>org.apache.ignite</groupId>
+ <groupId>org.gridgain</groupId>
<artifactId>ignite-log4j</artifactId>
<version>${ignite.version}</version>
</dependency>
diff --git a/modules/log4j2/README.txt b/modules/log4j2/README.txt
index 6e21b7a..9e0e4c0 100644
--- a/modules/log4j2/README.txt
+++ b/modules/log4j2/README.txt
@@ -1,7 +1,7 @@
-Apache Ignite Log4J2 Module
+GridGain Log4J2 Module
--------------------------
-Apache Ignite Log4J2 module provides IgniteLogger implementation based on Apache Log4J2.
+GridGain Log4J2 module provides IgniteLogger implementation based on Apache Log4J2.
To enable Log4J2 module when starting a standalone node, move 'optional/ignite-log4j2' folder to
'libs' folder before running 'ignite.{sh|bat}' script. The content of the module folder will
@@ -24,7 +24,7 @@ Importing Log4J2 Module In Maven Project
---------------------------------------
If you are using Maven to manage dependencies of your project, you can add Log4J2 module
-dependency like this (replace '${ignite.version}' with actual Ignite version you are
+dependency like this (replace '${ignite.version}' with actual GridGain version you are
interested in):
<project xmlns="http://maven.apache.org/POM/4.0.0"
@@ -35,7 +35,7 @@ interested in):
<dependencies>
...
<dependency>
- <groupId>org.apache.ignite</groupId>
+ <groupId>org.gridgain</groupId>
<artifactId>ignite-log4j2</artifactId>
<version>${ignite.version}</version>
</dependency>
diff --git a/modules/mesos/README.txt b/modules/mesos/README.txt
index e5e4bbb..1cb62ee 100644
--- a/modules/mesos/README.txt
+++ b/modules/mesos/README.txt
@@ -1,13 +1,13 @@
-Apache Ignite Mesos Module
+GridGain Mesos Module
------------------------
-Apache Ignite Mesos module provides integration Apache Ignite with Apache Mesos.
+GridGain Mesos module provides integration GridGain with Apache Mesos.
-Importing Apache Ignite Mesos Module In Maven Project
+Importing GridGain Mesos Module In Maven Project
-------------------------------------
If you are using Maven to manage dependencies of your project, you can add Mesos module
-dependency like this (replace '${ignite.version}' with actual Ignite version you are
+dependency like this (replace '${ignite.version}' with actual GridGain version you are
interested in):
<project xmlns="http://maven.apache.org/POM/4.0.0"
@@ -18,7 +18,7 @@ interested in):
<dependencies>
...
<dependency>
- <groupId>org.apache.ignite</groupId>
+ <groupId>org.gridgain</groupId>
<artifactId>ignite-mesos</artifactId>
<version>${ignite.version}</version>
</dependency>
diff --git a/modules/ml/README.txt b/modules/ml/README.txt
index d7e2fb9..8f4a556 100644
--- a/modules/ml/README.txt
+++ b/modules/ml/README.txt
@@ -1,16 +1,16 @@
-Apache Ignite ML Grid Module
+GridGain ML Grid Module
----------------------------
-Apache Ignite ML Grid module provides machine learning features, along with involved methods of linear algebra and relevant data structures, including on heap and off heap, dense and sparse, local and distributed implementations.
+GridGain ML Grid module provides machine learning features, along with involved methods of linear algebra and relevant data structures, including on heap and off heap, dense and sparse, local and distributed implementations.
# Local build with javadoc
Run from project root:
mvn clean package -DskipTests -pl modules/ml -am
-Apache binary releases cannot include LGPL dependencies. If you would like to activate native BLAS optimizations
+GridGain binary releases cannot include LGPL dependencies. If you would like to activate native BLAS optimizations
into your build, you should download the source release
-from Ignite website and do the build with the following maven command:
+from GridGain website and do the build with the following maven command:
mvn clean package -Plgpl -DskipTests -pl modules/ml -am
diff --git a/modules/mqtt/README.txt b/modules/mqtt/README.txt
index 62a1589..b37a9d7 100644
--- a/modules/mqtt/README.txt
+++ b/modules/mqtt/README.txt
@@ -1,14 +1,14 @@
-Apache Ignite MQTT Module
+GridGain MQTT Module
-------------------------
-Apache Ignite MQTT module provides a streamer to consume MQTT topic messages into
-Apache Ignite caches.
+GridGain MQTT module provides a streamer to consume MQTT topic messages into
+GridGain caches.
-Importing Apache Ignite MQTT Module In Maven Project
+Importing GridGain MQTT Module In Maven Project
----------------------------------------------------
If you are using Maven to manage dependencies of your project, you can add the MQTT module
-dependency like this (replace '${ignite.version}' with actual Ignite version you are
+dependency like this (replace '${ignite.version}' with actual GridGain version you are
interested in):
<project xmlns="http://maven.apache.org/POM/4.0.0"
@@ -19,7 +19,7 @@ interested in):
<dependencies>
...
<dependency>
- <groupId>org.apache.ignite</groupId>
+ <groupId>org.gridgain</groupId>
<artifactId>ignite-mqtt</artifactId>
<version>${ignite.version}</version>
</dependency>
diff --git a/modules/osgi-karaf/README.txt b/modules/osgi-karaf/README.txt
index 6bd1555..42e977f 100644
--- a/modules/osgi-karaf/README.txt
+++ b/modules/osgi-karaf/README.txt
@@ -1,18 +1,18 @@
-Apache Ignite OSGi Karaf Integration Module
+GridGain OSGi Karaf Integration Module
-------------------------------------------
-This module contains a feature repository to facilitate installing Apache Ignite into an Apache Karaf container.
+This module contains a feature repository to facilitate installing GridGain into an Apache Karaf container.
Use the following Karaf command:
- karaf@root()> feature:repo-add mvn:org.apache.ignite/ignite-osgi-karaf/${ignite.version}/xml/features
+ karaf@root()> feature:repo-add mvn:org.gridgain/ignite-osgi-karaf/${ignite.version}/xml/features
-Replacing ${ignite.version} with the Apache Ignite version you woudl like to install.
+Replacing ${ignite.version} with the GridGain version you would like to install.
-You may now list the Ignite features that are available for installation:
+You may now list the GridGain features that are available for installation:
karaf@root()> feature:list | grep ignite
Each feature installs the corresponding ignite module + its dependencies.
-We include an global feature with name 'ignite-all' that collectively installs all Ignite features at once.
+We include an global feature with name 'ignite-all' that collectively installs all GridGain features at once.
diff --git a/modules/osgi-paxlogging/README.txt b/modules/osgi-paxlogging/README.txt
index f6346f1..08342f3 100644
--- a/modules/osgi-paxlogging/README.txt
+++ b/modules/osgi-paxlogging/README.txt
@@ -1,4 +1,4 @@
-Apache Ignite OSGi Pax Logging Fragment Module
+GridGain OSGi Pax Logging Fragment Module
----------------------------------------------
This module is an OSGi fragment that exposes the following packages from the Pax Logging API bundle:
diff --git a/modules/osgi/README.txt b/modules/osgi/README.txt
index 439c450..00df4ae 100644
--- a/modules/osgi/README.txt
+++ b/modules/osgi/README.txt
@@ -1,13 +1,13 @@
-Apache Ignite OSGi Integration Module
+GridGain OSGi Integration Module
-------------------------------------
-This module provides the bridging components to make Apache Ignite run seamlessly inside an OSGi container
-like Apache Karaf. It provides a Bundle Activator to initialize Ignite, along with different classloaders
+This module provides the bridging components to make GridGain run seamlessly inside an OSGi container
+like Apache Karaf. It provides a Bundle Activator to initialize GridGain, along with different classloaders
facilitate class resolution within an OSGi environment.
-If using Ignite within Apache Karaf, please refer to the osgi-karaf and osgi-paxlogging modules too:
+If using GridGain within Apache Karaf, please refer to the osgi-karaf and osgi-paxlogging modules too:
- - osgi-karaf contains a feature repository to facilitate installing Ignite into a Karaf container.
+ - osgi-karaf contains a feature repository to facilitate installing GridGain into a Karaf container.
- osgi-paxlogging contains an OSGi fragment required to make pax-logging-api expose certain log4j packages
required by ignite-log4j
@@ -15,7 +15,7 @@ Importing the ignite-osgi module in a Maven project
---------------------------------------------------
If you are using Maven to manage dependencies of your project, you can add the ignite-osgi module
-dependency like this (replace '${ignite.version}' with actual Ignite version you are interested in):
+dependency like this (replace '${ignite.version}' with actual GridGain version you are interested in):
<project xmlns="http://maven.apache.org/POM/4.0.0"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
@@ -25,7 +25,7 @@ dependency like this (replace '${ignite.version}' with actual Ignite version you
<dependencies>
...
<dependency>
- <groupId>org.apache.ignite</groupId>
+ <groupId>org.gridgain</groupId>
<artifactId>ignite-osgi</artifactId>
<version>${ignite.version}</version>
</dependency>
diff --git a/modules/platforms/README.txt b/modules/platforms/README.txt
index 6268a88..aaeaf9e 100644
--- a/modules/platforms/README.txt
+++ b/modules/platforms/README.txt
@@ -1,6 +1,6 @@
-Apache Ignite Platforms
+GridGain Platforms
==================================
Contains integrations with other platforms, most notably:
- * Apache Ignite.NET
- * Apache Ignite C++
\ No newline at end of file
+ * GridGain.NET
+ * GridGain C++
\ No newline at end of file
diff --git a/modules/platforms/cpp/README.md b/modules/platforms/cpp/README.md
index 8d0f6d2..8be405c 100644
--- a/modules/platforms/cpp/README.md
+++ b/modules/platforms/cpp/README.md
@@ -1,99 +1,118 @@
-# Apache Ignite C++ SDK
+# Apache Ignite.NET SDK
-<a href="https://ignite.apache.org/"><img src="https://ignite.apache.org/images/logo3.png" hspace="20"/></a>
+<a href="https://www.gridgain.com/"><img src="https://www.gridgain.com/themes/gridgain1185/images/svg/gridgain-logo.svg?20180912" hspace="10" width="300px"/></a><br/><br/>
+<a href="https://www.nuget.org/packages?q=Apache.Ignite"><img src="https://img.shields.io/nuget/v/Apache.Ignite.svg" /></a>
-## Getting Started
+<a href="https://www.myget.org/gallery/apache-ignite-net-nightly"><img src="https://img.shields.io/myget/apache-ignite-net-nightly/vpre/Apache.Ignite.svg" /></a>
+
+<a href="https://ci.ignite.apache.org/viewType.html?buildTypeId=IgniteTests24Java8_IgnitePlatformNet&branch_IgniteTests24Java8=<default>"><img src="http://ci.ignite.apache.org/app/rest/builds/buildType:(id:IgniteTests24Java8_IgnitePlatformNet)/statusIcon" /></a>
-For information on how to get started with Apache Ignite, please visit: [Getting Started][getting-started].
+## Getting Started
-## Full Documentation
+For information on how to get started with GridGain, please visit: [Getting Started][getting-started].
-You can find the full Apache Ignite documentation here: [Full documentation][docs].
-## What is Apache Ignite?
+## What is GridGain?
-[Apache Ignite][apache-ignite-homepage] is a memory-centric multi-model distributed
- <strong>database</strong>, <strong>caching</strong>, and <strong>processing</strong> platform for
- transactional, analytical, and streaming workloads, delivering in-memory speeds at petabyte scale.
+GridGain, built on top of Apache Ignite, is a memory-centric distributed **database**, **caching**,
+ and **processing** platform for transactional, analytical, and streaming workloads delivering in-memory
+ speeds at petabyte scale.
<p align="center">
- <a href="https://apacheignite-cpp.readme.io/docs/">
- <img src="https://ignite.apache.org/images/durable-memory.png" width="900px"/>
+ <a href="https://www.gridgain.com/">
+ <img src="https://files.readme.io/58b7901-gg_platform.png" width="600px"/>
</a>
</p>
-## Durable Memory
-Ignite's durable memory component treats RAM not just as a caching layer but as a complete fully functional storage layer. This means that users can turn the persistence on and off as needed. If the persistence is off, then Ignite can act as a distributed **in-memory database** or **in-memory data grid**, depending on whether you prefer to use SQL or key-value APIs. If the persistence is turned on, then Ignite becomes a distributed, **horizontally scalable database** that guarantees full [...]
+## Memory-Centric Storage
+GridGain is based on distributed memory-centric architecture that combines the performance and scale of in-memory
+computing together with the disk durability and strong consistency in one system.
-[Read More](https://apacheignite-cpp.readme.io/docs/durable-memory)
+The main difference between the memory-centric approach and the traditional disk-centric approach is that the memory
+is treated as a fully functional storage, not just as a caching layer, like most databases do.
+For example, GridGain can function in a pure in-memory mode, in which case it can be treated as an
+In-Memory Database (IMDB) and In-Memory Data Grid (IMDG) in one.
-## Ignite Persistence
+On the other hand, when persistence is turned on, GidGain begins to function as a memory-centric system where most of
+the processing happens in memory, but the data and indexes get persisted to disk. The main difference here
+from the traditional disk-centric RDBMS or NoSQL system is that GridGain is strongly consistent, horizontally
+[Read More](https://apacheignite-net.readme.io/docs/durable-memory)
-Ignite Native Persistence is a distributed, ACID, and SQL-compliant **disk store** that transparently integrates with Ignite's Durable Memory as an optional disk layer storing data and indexes on SSD, Flash, 3D XPoint, and other types of non-volatile storages.
+## Native Persistence
-With the Ignite Persistence enabled, you no longer need to keep all the data and indexes in memory or warm it up after a node or cluster restart because the Durable Memory is tightly coupled with persistence and treats it as a secondary memory tier. This implies that if a subset of data or an index is missing in RAM, the Durable Memory will take it from the disk.
+Native Persistence is a distributed, ACID, and SQL-compliant **disk store** that transparently integrates with
+GridGain memory-centric storage as an optional disk layer storing data and indexes on SSD,
+ Flash, 3D XPoint, and other types of non-volatile storages.
+With the Native Persistence enabled, you no longer need to keep all the data and indexes in memory or warm it
+up after a node or cluster restart because the Durable Memory is tightly coupled with persistence and treats
+it as a secondary memory tier. This implies that if a subset of data or an index is missing in RAM,
+the Durable Memory will take it from the disk.
<p align="center">
<a href="https://apacheignite.readme.io/docs/distributed-persistent-store">
<img src="https://ignite.apache.org/images/native_persistence.png?renew" width="400px"/>
</a>
</p>
-[Read More](https://apacheignite-cpp.readme.io/docs/ignite-persistence)
+[Read More](https://apacheignite-net.readme.io/docs/ignite-persistent-store)
## ACID Compliance
-Data stored in Ignite is ACID-compliant both in memory and on disk, making Ignite a **strongly consistent** system. Ignite transactions work across the network and can span multiple servers.
+Data stored in GridGain is ACID-compliant both in memory and on disk, making GridGain a **strongly consistent** system. GridGain transactions work across the network and can span multiple servers.
-[Read More](https://apacheignite-cpp.readme.io/docs/transactions)
+[Read More](https://apacheignite-net.readme.io/docs/transactions)
## Complete SQL Support
-Ignite provides full support for SQL, DDL and DML, allowing users to interact with Ignite using pure SQL without writing any code. This means that users can create tables and indexes as well as insert, update, and query data using only SQL. Having such complete SQL support makes Ignite a one-of-a-kind **distributed SQL database**.
+GridGain provides full support for SQL, DDL and DML, allowing users to interact with GridGain using pure SQL without writing any code. This means that users can create tables and indexes as well as insert, update, and query data using only SQL. Having such complete SQL support makes GridGain a one-of-a-kind **distributed SQL database**.
-[Read More](https://apacheignite-cpp.readme.io/docs/sql-database)
+[Read More](https://apacheignite-net.readme.io/docs/sql-database)
## Key-Value
-The in-memory data grid component in Ignite is a fully transactional **distributed key-value store** that can scale horizontally across 100s of servers in the cluster. When persistence is enabled, Ignite can also store more data than fits in memory and survive full cluster restarts.
+The in-memory data grid component in GridGain is a fully transactional **distributed key-value store** that can scale horizontally across 100s of servers in the cluster. When persistence is enabled, GridGain can also store more data than fits in memory and survive full cluster restarts.
-[Read More](https://apacheignite-cpp.readme.io/docs/data-grid)
+[Read More](https://apacheignite-net.readme.io/docs/data-grid)
## Collocated Processing
-Most traditional databases work in a client-server fashion, meaning that data must be brought to the client side for processing. This approach requires lots of data movement from servers to clients and generally does not scale. Ignite, on the other hand, allows for sending light-weight computations to the data, i.e. **collocating** computations with data. As a result, Ignite scales better and minimizes data movement.
+Most traditional databases work in a client-server fashion, meaning that data must be brought to the client side for processing. This approach requires lots of data movement from servers to clients and generally does not scale. GridGain, on the other hand, allows for sending light-weight computations to the data, i.e. **collocating** computations with data. As a result, GridGain scales better and minimizes data movement.
-[Read More](https://apacheignite.readme.io/docs/collocate-compute-and-data)
+[Read More](https://apacheignite-net.readme.io/docs/colocate-compute-and-data)
## Scalability and Durability
-Ignite is an elastic, horizontally scalable distributed system that supports adding and removing cluster nodes on demand. Ignite also allows for storing multiple copies of the data, making it resilient to partial cluster failures. If the persistence is enabled, then data stored in Ignite will also survive full cluster failures. Cluster restarts in Ignite can be very fast, as the data becomes operational instantaneously directly from disk. As a result, the data does not need to be preload [...]
+GridGain is an elastic, horizontally scalable distributed system that supports adding and removing cluster nodes on demand. GridGain also allows for storing multiple copies of the data, making it resilient to partial cluster failures. If the persistence is enabled, then data stored in GridGain will also survive full cluster failures. Cluster restarts in GridGain can be very fast, as the data becomes operational instantaneously directly from disk. As a result, the data does not need to be [...]
-[Read More](https://apacheignite-cpp.readme.io/docs/cluster)
+[Read More](https://apacheignite-net.readme.io/docs/cluster)
## Ignite and Ignite C++
* Ignite C++ is built on top of Ignite.
* Ignite C++ starts the JVM in the same process and communicates with it via JNI.
* .NET, C++ and Java nodes can join the same cluster, use the same caches, and interoperate using common binary protocol.
* Java compute jobs can execute on any node (Java, .NET, C++).
+* .NET compute jobs can only execute on .NET nodes.
-## Ignite Components
+GridGain.NET also has Thin Client mode (see `Ignition.StartClient()`), which does not start JVM and does not require Java on machine.
-You can view Apache Ignite as a collection of independent, well-integrated components geared to improve performance and
+## GridGain Components
+
+You can view GridGain as a collection of independent, well-integrated components geared to improve performance and
scalability of your application.
Some of these components include:
* [Advanced Clustering](#advanced-clustering)
-* [Data Grid](#data-grid-jcache)
+* [Data Grid](##data-grid-jcache)
* [SQL Database](#sql-database)
* [Compute Grid](#compute-grid)
+* [Service Grid](#service-grid)
Below you’ll find a brief explanation for each of them:
## Advanced Clustering
-Ignite nodes can [automatically discover](https://apacheignite-cpp.readme.io/docs/cluster) each other. This helps to scale the cluster when needed, without having to restart the whole cluster.
-Developers can also leverage Ignite’s hybrid cloud support that allows establishing connection between private cloud and public clouds
+GridGain nodes can [automatically discover](https://apacheignite-net.readme.io/docs/cluster) each other. This helps to scale the cluster when needed, without having to restart the whole cluster.
+Developers can also leverage GridGain’s hybrid cloud support that allows establishing connection between private cloud and public clouds
such as Amazon Web Services, providing them with best of both worlds.
<p align="center">
- <a href="https://apacheignite-cpp.readme.io/docs/cluster">
+ <a href="https://apacheignite-net.readme.io/docs/cluster">
<img src="https://ignite.apache.org/images/advanced-clustering.png" />
</a>
</p>
@@ -101,120 +120,100 @@ such as Amazon Web Services, providing them with best of both worlds.
## Data Grid (Cache)
-[Ignite data grid](https://apacheignite-cpp.readme.io/docs/data-grid) is an in-memory distributed key-value store which can be viewed as a distributed partitioned `Dictionary`, with every cluster node
+[GridGain data grid](https://apacheignite-net.readme.io/docs/data-grid) is an in-memory distributed key-value store which can be viewed as a distributed partitioned `Dictionary`, with every cluster node
owning a portion of the overall data. This way the more cluster nodes we add, the more data we can cache.
-Unlike other key-value stores, Ignite determines data locality using a pluggable hashing algorithm. Every client can determine which node a key
+Unlike other key-value stores, GridGain determines data locality using a pluggable hashing algorithm. Every client can determine which node a key
belongs to by plugging it into a hashing function, without a need for any special mapping servers or name nodes.
-Ignite data grid supports local, replicated, and partitioned data sets and allows to freely cross query between these data sets using standard SQL and LINQ syntax.
-Ignite supports standard SQL and LINQ for querying in-memory data including support for distributed joins.
+GridGain data grid supports local, replicated, and partitioned data sets and allows to freely cross query between these data sets using standard SQL and LINQ syntax.
+GridGain supports standard SQL and LINQ for querying in-memory data including support for distributed joins.
<p align="center">
- <a href="https://apacheignite-cpp.readme.io/docs/data-grid">
+ <a href="https://apacheignite-net.readme.io/docs/data-grid">
<img src="https://ignite.apache.org/images/data_grid.png" vspace="15" width="450px"/>
</a>
</p>
## SQL Database
-Apache Ignite incorporates [distributed SQL database](https://apacheignite-cpp.readme.io/docs/sql-database) capabilities as a part of its platform. The database is horizontally
+GridGain incorporates [distributed SQL database](https://apacheignite-net.readme.io/docs/sql-database) capabilities as a part of its platform. The database is horizontally
scalable, fault tolerant and SQL ANSI-99 compliant. It supports all SQL, DDL, and DML commands including SELECT, UPDATE,
INSERT, MERGE, and DELETE queries. It also provides support for a subset of DDL commands relevant for distributed
databases.
-With Ignite Durable Memory architecture, data as well as indexes can be stored both in memory and, optionally, on disk.
+With GridGain Durable Memory architecture, data as well as indexes can be stored both in memory and, optionally, on disk.
This allows executing distributed SQL operations across different memory layers achieving in-memory performance with the durability of disk.
-You can interact with Apache Ignite using the SQL language via natively developed APIs for Java, .NET and C++, or via
-the Ignite JDBC or ODBC drivers. This provides a true cross-platform connectivity from languages such as PHP, Ruby and more.
+You can interact with GridGain using the SQL language via natively developed APIs for Java, .NET and C++, or via
+the GridGain JDBC or ODBC drivers. This provides a true cross-platform connectivity from languages such as PHP, Ruby and more.
<p align="center">
- <a href="https://apacheignite-cpp.readme.io/docs/sql-database">
+ <a href="https://apacheignite-net.readme.io/docs/sql-database">
<img src="https://ignite.apache.org/images/sql_database.png" vspace="15" width="400px"/>
</a>
</p>
## Compute Grid
-[Distributed computations](https://apacheignite-cpp.readme.io/docs/compute-grid) are performed in parallel fashion to gain high performance, low latency, and linear scalability.
-Ignite compute grid provides a set of simple APIs that allow users distribute computations and data processing across multiple computers in the cluster.
+[Distributed computations](https://apacheignite-net.readme.io/docs/compute-grid) are performed in parallel fashion to gain high performance, low latency, and linear scalability.
+GridGain compute grid provides a set of simple APIs that allow users distribute computations and data processing across multiple computers in the cluster.
Distributed parallel processing is based on the ability to take any computation and execute it on any set of cluster nodes and return the results back.
<p align="center">
- <a href="https://apacheignite-cpp.readme.io/docs/compute-grid">
+ <a href="https://apacheignite-net.readme.io/docs/compute-grid">
<img src="https://ignite.apache.org/images/collocated_processing.png" vspace="15" width="400px"/>
</a>
</p>
We support these features, amongst others:
-* [Distributed Closure Execution](https://apacheignite-cpp.readme.io/docs/distributed-closures)
-* [Load Balancing](https://apacheignite-cpp.readme.io/docs/load-balancing)
-* [Job Scheduling](https://apacheignite-cpp.readme.io/docs/job-scheduling)
-* [Fault Tolerance](https://apacheignite-cpp.readme.io/docs/fault-tolerance)
-
-
-## Ignite Facts
-
-#### Is Ignite a persistent or pure in-memory storage?
-**Both**. Native persistence in Ignite can be turned on and off. This allows Ignite to store data sets bigger than can fit in the available memory. Essentially, the smaller operational data sets can be stored in-memory only, and larger data sets that do not fit in memory can be stored on disk, using memory as a caching layer for better performance.
-
-[Read More](https://apacheignite-cpp.readme.io/docs/ignite-persistence)
-
-#### Is Ignite a distributed database?
-**Yes**. Data in Ignite is either *partitioned* or *replicated* across a cluster of multiple nodes. This provides scalability and adds resilience to the system. Ignite automatically controls how data is partitioned, however, users can plug in their own distribution (affinity) functions and collocate various pieces of data together for efficiency.
+* [Distributed Closure Execution](https://apacheignite-net.readme.io/docs/distributed-closures)
+* [MapReduce & ForkJoin Processing](https://apacheignite-net.readme.io/docs/mapreduce-forkjoin)
+* [Collocation of Compute and Data](https://apacheignite-net.readme.io/docs/colocate-compute-and-data)
+* [Fault Tolerance](https://apacheignite-net.readme.io/docs/fault-tolerance)
-[Read More](https://apacheignite-cpp.readme.io/docs/sql-database)
+## Service Grid
-#### Is Ignite a relational SQL database?
-**Not fully**. Although Ignite aims to behave like any other relational SQL database, there are differences in how Ignite handles constraints and indexes. Ignite supports *primary* and *secondary* indexes, however, the *uniqueness* can only be enforced for the *primary* indexes. Ignite also does not support *foreign key* constraints.
+[Service Grid](https://apacheignite-net.readme.io/docs/service-grid) allows for deployments of arbitrary user-defined services on the cluster. You can implement and deploy any service, such as custom counters, ID generators, hierarchical maps, etc.
-Essentially, Ignite purposely does not support any constraints that would entail a cluster broadcast message for each update and significantly hurt performance and scalability of the system.
+GridGain allows you to control how many instances of your service should be deployed on each cluster node and will automatically ensure proper deployment and fault tolerance of all the services.
-[Read More](https://apacheignite-cpp.readme.io/docs/sql-database)
-
-#### Is Ignite an in-memory database?
-**Yes**. Even though Ignite *durable memory* works well in-memory and on-disk, the disk persistence can be disabled and Ignite can act as a pure *in-memory database*.
-
-[Read More](https://apacheignite-cpp.readme.io/docs/sql-database)
-
-#### Is Ignite a transactional database?
-**Not fully**. ACID Transactions are supported, but only at *key-value* API level. Ignite also supports *cross-partition* transactions, which means that transactions can span keys residing in different partitions on different servers.
-
-At *SQL* level Ignite supports *atomic*, but not yet *transactional* consistency. Ignite community plans to implement SQL transactions in version 2.4.
-
-[Read More](https://apacheignite-cpp.readme.io/docs/sql-database)
+<p align="center">
+ <a href="https://apacheignite-net.readme.io/docs/service-grid">
+ <img src="https://ignite.apache.org/images/service_grid.png" vspace="15" width="400px"/>
+ </a>
+</p>
-#### Is Ignite a key-value store?
-**Yes**. Ignite provides a feature rich key-value API, that is JCache (JSR-107) compliant and supports Java, C++, and .NET.
+## Distributed Data Structures
-[Read More](https://apacheignite-cpp.readme.io/docs/data-grid)
+GridGain.NET supports complex [data structures](https://apacheignite-net.readme.io/docs/atomic-types) in a distributed fashion: `AtomicLong`, `AtomicReference`, `AtomicSequence`.
-#### Is Ignite an in-memory data grid?
-**Yes**. Ignite is a full-featured data grid, which can be used either in pure in-memory mode or with Ignite native persistence. It can also integrate with any 3rd party database, including any RDBMS or NoSQL store.
+## Distributed Messaging
-[Read More](https://apacheignite-cpp.readme.io/docs/data-grid)
+[Distributed messaging](https://apacheignite-net.readme.io/docs/topic-based) allows for topic based cluster-wide communication between all nodes. Messages with a specified message topic can be distributed to
+all or sub-group of nodes that have subscribed to that topic.
-#### What is durable memory?
-Ignite *durable memory* architecture allows Ignite to extend in-memory computing to disk. It is based on a paged-based off-heap memory allocator which becomes durable by persisting to the *write-ahead-log (WAL)* and, then, to main Ignite persistent storage. When persistence is disabled, durable memory acts like a pure in-memory storage.
+GridGain messaging is based on publish-subscribe paradigm where publishers and subscribers are connected together by a common topic.
+When one of the nodes sends a message A for topic T, it is published on all nodes that have subscribed to T.
-[Read More](https://apacheignite-cpp.readme.io/docs/durable-memory)
+## Distributed Events
-#### What is collocated processing?
-Ignite is a distributed system and, therefore, it is important to be able to collocate data with data and compute with data to avoid distributed data noise. Data collocation becomes especially important when performing distributed SQL joins. Ignite also supports sending user logic (functions, lambdas, etc.) directly to the nodes where the data resides and computing on the data locally.
+[Distributed events](https://apacheignite-net.readme.io/docs/local-and-remote-events) allow applications to receive notifications when a variety of events occur in the distributed grid environment.
+You can automatically get notified for task executions, read, write or query operations occurring on local or remote nodes within the cluster.
-[Read More](https://apacheignite.readme.io/docs/collocate-compute-and-data)
+## ASP.NET Integration
+GridGain.NET provides [Output Cache](https://apacheignite-net.readme.io/docs/aspnet-output-caching) and [Session State](https://apacheignite-net.readme.io/docs/aspnet-session-state-caching) clustering: boost performance by storing cache and session data in GridGain distributed cache.
-## Ignite On Other Platforms
+## Entity Framework Integration
-<a href="https://github.com/apache/ignite">Java</a>
+GridGain.NET [Entity Framework Second Level Cache](https://apacheignite-net.readme.io/docs/entity-framework-second-level-cache) improves Entity Framework performance by storing query results in GridGain caches.
-<a href="https://github.com/apache/ignite/tree/master/modules/platforms/dotnet">Ignite.Net</a>
[apache-ignite-homepage]: https://ignite.apache.org/
-[getting-started]: https://apacheignite-cpp.readme.io/docs/getting-started-1
-[docs]: https://apacheignite-cpp.readme.io/docs
\ No newline at end of file
+[GridGain-homepage]: https://www.gridgain.com/
+[getting-started]: https://docs.gridgain.com/docs
+[docs]: https://docs.gridgain.com/docs
diff --git a/modules/platforms/cpp/README.txt b/modules/platforms/cpp/README.txt
index a0a35d4..c3cae85 100644
--- a/modules/platforms/cpp/README.txt
+++ b/modules/platforms/cpp/README.txt
@@ -1,11 +1,11 @@
-Apache Ignite C++
+GridGain C++
==================================
-Apache Ignite C++ provides data grid functionality.
-Using Apache Ignite C++ APIs you can perform concurrent operations on
+GridGain C++ provides data grid functionality.
+Using GridGain C++ APIs you can perform concurrent operations on
the data stored in cache.
-Apache Ignite C++ can access cluster and share data with .Net and
+GridGain C++ can access cluster and share data with .Net and
Java applications using binary object format.
Support for the following will be added in next releases:
@@ -28,23 +28,23 @@ Linux info
Files list:
- * ignite - executable to start standalone Ignite C++ node.
- * libignite.so - Ignite C++ API library.
- * libignite-odbc.so - Ignite ODBC driver.
- * libignite-thin-client.so - Ignite C++ thin client library.
+ * ignite - executable to start standalone GridGain C++ node.
+ * libignite.so - GridGain C++ API library.
+ * libignite-odbc.so - GridGain ODBC driver.
+ * libignite-thin-client.so - GridGain C++ thin client library.
Development:
- * IGNITE_HOME environment variable must be set to Ignite installation directory.
+ * IGNITE_HOME environment variable must be set to GridGain installation directory.
* Once both libraries are built and installed, required headers are placed in the
"/usr/local/include/ignite" directory.
- * Apache Ignite C++ depends on jni.h file located inside ${JAVA_HOME}/include directory.
+ * GridGain C++ depends on jni.h file located inside ${JAVA_HOME}/include directory.
Add this directory to headers search path: "-I${JAVA_HOME}/include".
* Library is placed in the "/usr/local/lib" directory. Link it to your project: "-lignite".
- * Ignite depends on "libjvm.so" library shipped with Java. Typically this library is
+ * GridGain depends on "libjvm.so" library shipped with Java. Typically this library is
located inside $JAVA_HOME/jre/lib/amd64/server directory. Ensure that LD_LIBRARY_PATH
environment variable points to this directory.
- * To start Apache Ignite as a standalone node use "ignite" binary.
+ * To start GridGain as a standalone node use "ignite" binary.
Windows info
@@ -52,14 +52,14 @@ Windows info
Files list:
- * ignite.exe - executable to start standalone Ignite C++ node.
- * ignite.core.dll - Ignite C++ API library.
- * ignite.odbc.dll - Ignite ODBC driver.
- * ignite.thin-client.dll - Ignite thin C++ client.
+ * ignite.exe - executable to start standalone GridGain C++ node.
+ * ignite.core.dll - GridGain C++ API library.
+ * ignite.odbc.dll - GridGain ODBC driver.
+ * ignite.thin-client.dll - GridGain thin C++ client.
Development:
- * IGNITE_HOME environment variable must be set to Ignite installation directory.
+ * IGNITE_HOME environment variable must be set to GridGain installation directory.
* Update Include Directories in Project Properties with paths to:
* $(IGNITE_HOME)\platforms\cpp\common\include
* $(IGNITE_HOME)\platforms\cpp\common\os\win\include
@@ -82,4 +82,4 @@ Development:
ignite.thin-client.dll libraries. The easiest way to achieve this is to either make
sure these files are in %PATH%, or to put them into the output directory of your
project with help of PostBuild events.
- * To start Apache Ignite as a standalone node or Windows service use ignite.exe
+ * To start GridGain as a standalone node or Windows service use ignite.exe
diff --git a/modules/platforms/cpp/examples/README.txt b/modules/platforms/cpp/examples/README.txt
index 823f12d..dcf6d60 100644
--- a/modules/platforms/cpp/examples/README.txt
+++ b/modules/platforms/cpp/examples/README.txt
@@ -1,16 +1,16 @@
-Apache Ignite C++ Examples
+GridGain C++ Examples
==================================
Common requirements
----------------------------------
* Java Development Kit (JDK) must be installed: https://java.com/en/download/index.jsp
* JAVA_HOME environment variable must be set pointing to Java installation directory.
- * IGNITE_HOME environment variable must be set to Ignite installation directory.
- * Ignite must be built and packaged using Maven. You can use the following Maven command: mvn clean package -DskipTests
- * Apache Ignite C++ must be built according to instructions for your platform. Refer to
+ * IGNITE_HOME environment variable must be set to GridGain installation directory.
+ * GridGain must be built and packaged using Maven. You can use the following Maven command: mvn clean package -DskipTests
+ * GridGain C++ must be built according to instructions for your platform. Refer to
$IGNITE_HOME/platforms/cpp/DEVNOTES.txt for instructions.
* For odbc-example additionally ODBC Driver Manager must be present and installed on your platform and
- Apache Ignite ODBC driver must be built and installed according to instructions for your platform. Refer to
+ GridGain ODBC driver must be built and installed according to instructions for your platform. Refer to
$IGNITE_HOME/platforms/cpp/DEVNOTES.txt for build instructions and to $IGNITE_HOME/platforms/cpp/odbc/README.txt.
for installation instructions.
@@ -31,8 +31,8 @@ Before running examples ensure that:
* LD_LIBRARY_PATH environment variable is set and pointing to a directory with "libjvm.so" library. Typically this
library is located in $JAVA_HOME/jre/lib/amd64/server directory.
* For odbc-example additionaly ODBC Driver Manager must be present and installed on your platform and
- Apache Ignite ODBC driver must be built and installed according to instructions for your platform.
- * For odbc-example make sure that path to Ignite libraries is added to LD_LIBRARY_PATH (usually it is /usr/local/lib).
+ GridGain ODBC driver must be built and installed according to instructions for your platform.
+ * For odbc-example make sure that path to GridGain libraries is added to LD_LIBRARY_PATH (usually it is /usr/local/lib).
Running examples on Windows
----------------------------------
diff --git a/modules/platforms/cpp/odbc/README.txt b/modules/platforms/cpp/odbc/README.txt
index 3a83f84..981f62c 100644
--- a/modules/platforms/cpp/odbc/README.txt
+++ b/modules/platforms/cpp/odbc/README.txt
@@ -1,20 +1,20 @@
-Apache Ignite ODBC driver
+GridGain ODBC driver
=======================================
-Apache Ignite provides ODBC driver that can be used to retrieve distributed
+GridGain provides ODBC driver that can be used to retrieve distributed
data from cache using standard SQL queries and native ODBC API.
For more info on ODBC please refer to ODBC Programmer's Reference at
https://msdn.microsoft.com/en-us/library/ms714177.aspx
-To use Apache Ignite ODBC driver you first need to build and install it for
+To use GridGain ODBC driver you first need to build and install it for
your system. You can find driver installation instructions below. For build
instruction please refer to $IGNITE_HOME/platforms/cpp/DEVNOTES.txt.
Connection string and DSN arguments
=======================================
-Apache Ignite ODBC driver supports and uses following connection string/DSN
+GridGain ODBC driver supports and uses following connection string/DSN
arguments:
1. Address of the node to connect to:
@@ -33,11 +33,11 @@ Installing ODBC driver on Linux
=======================================
To be able to build and install ODBC driver on Linux you first need to install
-ODBC Driver Manager. Apache Ignite ODBC driver has been tested with UnixODBC
+ODBC Driver Manager. GridGain ODBC driver has been tested with UnixODBC
(http://www.unixodbc.org).
-Once you have built and installed Ignite ODBC Driver i.e. libignite-odbc.so it
-is most likely placed to /usr/local/lib. To install and be able to use Ignite
+Once you have built and installed GridGain ODBC Driver i.e. libignite-odbc.so it
+is most likely placed to /usr/local/lib. To install and be able to use GridGain
ODBC driver you should perfrom the following steps:
1. Ensure linker is able to locate all dependencies of the ODBC driver. You
@@ -51,7 +51,7 @@ ODBC driver you should perfrom the following steps:
and ensure that "Driver" parameter of the "Apache Ignite" section points
to the right location where libignite-odbc.so is located.
-3. To install Apache Ignite ODBC driver use the following command:
+3. To install GridGain ODBC driver use the following command:
$ odbcinst -i -d -f $IGNITE_HOME/platforms/cpp/odbc/install/ignite-odbc-install.ini
To perform this command you most likely will need root privileges.
@@ -92,7 +92,7 @@ Thats it. Your driver/drivers are installed.
After the installation
=======================================
-Now Apache Ignite ODBC driver is installed and ready for use. You can connect
+Now GridGain ODBC driver is installed and ready for use. You can connect
to it and use it like to any other ODBC driver.
For further instruction on the usage of the ODBC driver please refer to the
diff --git a/modules/platforms/dotnet/README.md b/modules/platforms/dotnet/README.md
index 4830940..5b60cc5 100644
--- a/modules/platforms/dotnet/README.md
+++ b/modules/platforms/dotnet/README.md
@@ -1,6 +1,6 @@
-# Apache Ignite.NET SDK
+# GridGain.NET SDK
-<a href="https://ignite.apache.org/"><img src="https://ignite.apache.org/images/logo3.png" hspace="20"/></a><img src="https://ptupitsyn.github.io/images/net-framework.png" hspace="20" />
+<a href="https://www.gridgain.com/"><img src="https://www.gridgain.com/themes/gridgain1185/images/svg/gridgain-logo.svg?20180912" hspace="10" width="300px"/></a><br/><br/>
<a href="https://www.nuget.org/packages?q=Apache.Ignite"><img src="https://img.shields.io/nuget/v/Apache.Ignite.svg" /></a>
@@ -10,35 +10,45 @@
## Getting Started
-For information on how to get started with Apache Ignite, please visit: [Getting Started][getting-started].
+For information on how to get started with GridGain, please visit: [Getting Started][getting-started].
-## Full Documentation
-You can find the full Apache Ignite documentation here: [Full documentation][docs].
+## What is GridGain?
-## What is Apache Ignite?
-
-[Apache Ignite][apache-ignite-homepage] is a memory-centric multi-model distributed
- <strong>database</strong>, <strong>caching</strong>, and <strong>processing</strong> platform for
- transactional, analytical, and streaming workloads, delivering in-memory speeds at petabyte scale.
+GridGain, built on top of Apache Ignite, is a memory-centric distributed **database**, **caching**,
+ and **processing** platform for transactional, analytical, and streaming workloads delivering in-memory
+ speeds at petabyte scale.
<p align="center">
- <a href="https://apacheignite-net.readme.io/docs/">
- <img src="https://ignite.apache.org/images/durable-memory.png" width="900px"/>
+ <a href="https://www.gridgain.com/">
+ <img src="https://files.readme.io/58b7901-gg_platform.png" width="600px"/>
</a>
</p>
-## Durable Memory
-Ignite's durable memory component treats RAM not just as a caching layer but as a complete fully functional storage layer. This means that users can turn the persistence on and off as needed. If the persistence is off, then Ignite can act as a distributed **in-memory database** or **in-memory data grid**, depending on whether you prefer to use SQL or key-value APIs. If the persistence is turned on, then Ignite becomes a distributed, **horizontally scalable database** that guarantees full [...]
+## Memory-Centric Storage
+GridGain is based on distributed memory-centric architecture that combines the performance and scale of in-memory
+computing together with the disk durability and strong consistency in one system.
-[Read More](https://apacheignite-net.readme.io/docs/durable-memory)
+The main difference between the memory-centric approach and the traditional disk-centric approach is that the memory
+is treated as a fully functional storage, not just as a caching layer, like most databases do.
+For example, GridGain can function in a pure in-memory mode, in which case it can be treated as an
+In-Memory Database (IMDB) and In-Memory Data Grid (IMDG) in one.
-## Ignite Persistence
+On the other hand, when persistence is turned on, GidGain begins to function as a memory-centric system where most of
+the processing happens in memory, but the data and indexes get persisted to disk. The main difference here
+from the traditional disk-centric RDBMS or NoSQL system is that GridGain is strongly consistent, horizontally
+[Read More](https://apacheignite-net.readme.io/docs/durable-memory)
-Ignite Native Persistence is a distributed, ACID, and SQL-compliant **disk store** that transparently integrates with Ignite's Durable Memory as an optional disk layer storing data and indexes on SSD, Flash, 3D XPoint, and other types of non-volatile storages.
+## Native Persistence
-With the Ignite Persistence enabled, you no longer need to keep all the data and indexes in memory or warm it up after a node or cluster restart because the Durable Memory is tightly coupled with persistence and treats it as a secondary memory tier. This implies that if a subset of data or an index is missing in RAM, the Durable Memory will take it from the disk.
+Native Persistence is a distributed, ACID, and SQL-compliant **disk store** that transparently integrates with
+GridGain memory-centric storage as an optional disk layer storing data and indexes on SSD,
+ Flash, 3D XPoint, and other types of non-volatile storages.
+With the Native Persistence enabled, you no longer need to keep all the data and indexes in memory or warm it
+up after a node or cluster restart because the Durable Memory is tightly coupled with persistence and treats
+it as a secondary memory tier. This implies that if a subset of data or an index is missing in RAM,
+the Durable Memory will take it from the disk.
<p align="center">
<a href="https://apacheignite.readme.io/docs/distributed-persistent-store">
<img src="https://ignite.apache.org/images/native_persistence.png?renew" width="400px"/>
@@ -48,43 +58,43 @@ With the Ignite Persistence enabled, you no longer need to keep all the data and
[Read More](https://apacheignite-net.readme.io/docs/ignite-persistent-store)
## ACID Compliance
-Data stored in Ignite is ACID-compliant both in memory and on disk, making Ignite a **strongly consistent** system. Ignite transactions work across the network and can span multiple servers.
+Data stored in GridGain is ACID-compliant both in memory and on disk, making GridGain a **strongly consistent** system. GridGain transactions work across the network and can span multiple servers.
[Read More](https://apacheignite-net.readme.io/docs/transactions)
## Complete SQL Support
-Ignite provides full support for SQL, DDL and DML, allowing users to interact with Ignite using pure SQL without writing any code. This means that users can create tables and indexes as well as insert, update, and query data using only SQL. Having such complete SQL support makes Ignite a one-of-a-kind **distributed SQL database**.
+GridGain provides full support for SQL, DDL and DML, allowing users to interact with GridGain using pure SQL without writing any code. This means that users can create tables and indexes as well as insert, update, and query data using only SQL. Having such complete SQL support makes GridGain a one-of-a-kind **distributed SQL database**.
[Read More](https://apacheignite-net.readme.io/docs/sql-database)
## Key-Value
-The in-memory data grid component in Ignite is a fully transactional **distributed key-value store** that can scale horizontally across 100s of servers in the cluster. When persistence is enabled, Ignite can also store more data than fits in memory and survive full cluster restarts.
+The in-memory data grid component in GridGain is a fully transactional **distributed key-value store** that can scale horizontally across 100s of servers in the cluster. When persistence is enabled, GridGain can also store more data than fits in memory and survive full cluster restarts.
[Read More](https://apacheignite-net.readme.io/docs/data-grid)
## Collocated Processing
-Most traditional databases work in a client-server fashion, meaning that data must be brought to the client side for processing. This approach requires lots of data movement from servers to clients and generally does not scale. Ignite, on the other hand, allows for sending light-weight computations to the data, i.e. **collocating** computations with data. As a result, Ignite scales better and minimizes data movement.
+Most traditional databases work in a client-server fashion, meaning that data must be brought to the client side for processing. This approach requires lots of data movement from servers to clients and generally does not scale. GridGain, on the other hand, allows for sending light-weight computations to the data, i.e. **collocating** computations with data. As a result, GridGain scales better and minimizes data movement.
[Read More](https://apacheignite-net.readme.io/docs/colocate-compute-and-data)
## Scalability and Durability
-Ignite is an elastic, horizontally scalable distributed system that supports adding and removing cluster nodes on demand. Ignite also allows for storing multiple copies of the data, making it resilient to partial cluster failures. If the persistence is enabled, then data stored in Ignite will also survive full cluster failures. Cluster restarts in Ignite can be very fast, as the data becomes operational instantaneously directly from disk. As a result, the data does not need to be preload [...]
+GridGain is an elastic, horizontally scalable distributed system that supports adding and removing cluster nodes on demand. GridGain also allows for storing multiple copies of the data, making it resilient to partial cluster failures. If the persistence is enabled, then data stored in GridGain will also survive full cluster failures. Cluster restarts in GridGain can be very fast, as the data becomes operational instantaneously directly from disk. As a result, the data does not need to be [...]
[Read More](https://apacheignite-net.readme.io/docs/cluster)
-## Ignite and Ignite.NET
+## GridGain and GridGain.NET
-* Ignite.NET is built on top of Ignite.
+* GridGain.NET is built on top of GridGain.
* .NET starts the JVM in the same process and communicates with it via JNI.
* .NET, C++ and Java nodes can join the same cluster, use the same caches, and interoperate using common binary protocol.
* Java compute jobs can execute on any node (Java, .NET, C++).
* .NET compute jobs can only execute on .NET nodes.
-Ignite.NET also has Thin Client mode (see `Ignition.StartClient()`), which does not start JVM and does not require Java on machine.
+GridGain.NET also has Thin Client mode (see `Ignition.StartClient()`), which does not start JVM and does not require Java on machine.
-## Ignite Components
+## GridGain Components
-You can view Apache Ignite as a collection of independent, well-integrated components geared to improve performance and
+You can view GridGain as a collection of independent, well-integrated components geared to improve performance and
scalability of your application.
Some of these components include:
@@ -98,8 +108,8 @@ Below you’ll find a brief explanation for each of them:
## Advanced Clustering
-Ignite nodes can [automatically discover](https://apacheignite-net.readme.io/docs/cluster) each other. This helps to scale the cluster when needed, without having to restart the whole cluster.
-Developers can also leverage Ignite’s hybrid cloud support that allows establishing connection between private cloud and public clouds
+GridGain nodes can [automatically discover](https://apacheignite-net.readme.io/docs/cluster) each other. This helps to scale the cluster when needed, without having to restart the whole cluster.
+Developers can also leverage GridGain’s hybrid cloud support that allows establishing connection between private cloud and public clouds
such as Amazon Web Services, providing them with best of both worlds.
<p align="center">
@@ -111,14 +121,14 @@ such as Amazon Web Services, providing them with best of both worlds.
## Data Grid (Cache)
-[Ignite data grid](https://apacheignite-net.readme.io/docs/data-grid) is an in-memory distributed key-value store which can be viewed as a distributed partitioned `Dictionary`, with every cluster node
+[GridGain data grid](https://apacheignite-net.readme.io/docs/data-grid) is an in-memory distributed key-value store which can be viewed as a distributed partitioned `Dictionary`, with every cluster node
owning a portion of the overall data. This way the more cluster nodes we add, the more data we can cache.
-Unlike other key-value stores, Ignite determines data locality using a pluggable hashing algorithm. Every client can determine which node a key
+Unlike other key-value stores, GridGain determines data locality using a pluggable hashing algorithm. Every client can determine which node a key
belongs to by plugging it into a hashing function, without a need for any special mapping servers or name nodes.
-Ignite data grid supports local, replicated, and partitioned data sets and allows to freely cross query between these data sets using standard SQL and LINQ syntax.
-Ignite supports standard SQL and LINQ for querying in-memory data including support for distributed joins.
+GridGain data grid supports local, replicated, and partitioned data sets and allows to freely cross query between these data sets using standard SQL and LINQ syntax.
+GridGain supports standard SQL and LINQ for querying in-memory data including support for distributed joins.
<p align="center">
<a href="https://apacheignite-net.readme.io/docs/data-grid">
@@ -128,16 +138,16 @@ Ignite supports standard SQL and LINQ for querying in-memory data including supp
## SQL Database
-Apache Ignite incorporates [distributed SQL database](https://apacheignite-net.readme.io/docs/sql-database) capabilities as a part of its platform. The database is horizontally
+GridGain incorporates [distributed SQL database](https://apacheignite-net.readme.io/docs/sql-database) capabilities as a part of its platform. The database is horizontally
scalable, fault tolerant and SQL ANSI-99 compliant. It supports all SQL, DDL, and DML commands including SELECT, UPDATE,
INSERT, MERGE, and DELETE queries. It also provides support for a subset of DDL commands relevant for distributed
databases.
-With Ignite Durable Memory architecture, data as well as indexes can be stored both in memory and, optionally, on disk.
+With GridGain Durable Memory architecture, data as well as indexes can be stored both in memory and, optionally, on disk.
This allows executing distributed SQL operations across different memory layers achieving in-memory performance with the durability of disk.
-You can interact with Apache Ignite using the SQL language via natively developed APIs for Java, .NET and C++, or via
-the Ignite JDBC or ODBC drivers. This provides a true cross-platform connectivity from languages such as PHP, Ruby and more.
+You can interact with GridGain using the SQL language via natively developed APIs for Java, .NET and C++, or via
+the GridGain JDBC or ODBC drivers. This provides a true cross-platform connectivity from languages such as PHP, Ruby and more.
<p align="center">
@@ -149,7 +159,7 @@ the Ignite JDBC or ODBC drivers. This provides a true cross-platform connectivit
## Compute Grid
[Distributed computations](https://apacheignite-net.readme.io/docs/compute-grid) are performed in parallel fashion to gain high performance, low latency, and linear scalability.
-Ignite compute grid provides a set of simple APIs that allow users distribute computations and data processing across multiple computers in the cluster.
+GridGain compute grid provides a set of simple APIs that allow users distribute computations and data processing across multiple computers in the cluster.
Distributed parallel processing is based on the ability to take any computation and execute it on any set of cluster nodes and return the results back.
<p align="center">
@@ -169,7 +179,7 @@ We support these features, amongst others:
[Service Grid](https://apacheignite-net.readme.io/docs/service-grid) allows for deployments of arbitrary user-defined services on the cluster. You can implement and deploy any service, such as custom counters, ID generators, hierarchical maps, etc.
-Ignite allows you to control how many instances of your service should be deployed on each cluster node and will automatically ensure proper deployment and fault tolerance of all the services.
+GridGain allows you to control how many instances of your service should be deployed on each cluster node and will automatically ensure proper deployment and fault tolerance of all the services.
<p align="center">
<a href="https://apacheignite-net.readme.io/docs/service-grid">
@@ -179,14 +189,14 @@ Ignite allows you to control how many instances of your service should be deploy
## Distributed Data Structures
-Ignite.NET supports complex [data structures](https://apacheignite-net.readme.io/docs/atomic-types) in a distributed fashion: `AtomicLong`, `AtomicReference`, `AtomicSequence`.
+GridGain.NET supports complex [data structures](https://apacheignite-net.readme.io/docs/atomic-types) in a distributed fashion: `AtomicLong`, `AtomicReference`, `AtomicSequence`.
## Distributed Messaging
[Distributed messaging](https://apacheignite-net.readme.io/docs/topic-based) allows for topic based cluster-wide communication between all nodes. Messages with a specified message topic can be distributed to
all or sub-group of nodes that have subscribed to that topic.
-Ignite messaging is based on publish-subscribe paradigm where publishers and subscribers are connected together by a common topic.
+GridGain messaging is based on publish-subscribe paradigm where publishers and subscribers are connected together by a common topic.
When one of the nodes sends a message A for topic T, it is published on all nodes that have subscribed to T.
## Distributed Events
@@ -196,74 +206,15 @@ You can automatically get notified for task executions, read, write or query ope
## ASP.NET Integration
-Ignite.NET provides [Output Cache](https://apacheignite-net.readme.io/docs/aspnet-output-caching) and [Session State](https://apacheignite-net.readme.io/docs/aspnet-session-state-caching) clustering: boost performance by storing cache and session data in Ignite distributed cache.
+GridGain.NET provides [Output Cache](https://apacheignite-net.readme.io/docs/aspnet-output-caching) and [Session State](https://apacheignite-net.readme.io/docs/aspnet-session-state-caching) clustering: boost performance by storing cache and session data in GridGain distributed cache.
## Entity Framework Integration
-Ignite.NET [Entity Framework Second Level Cache](https://apacheignite-net.readme.io/docs/entity-framework-second-level-cache) improves Entity Framework performance by storing query results in Ignite caches.
-
-## Ignite Facts
-
-#### Is Ignite a persistent or pure in-memory storage?
-**Both**. Native persistence in Ignite can be turned on and off. This allows Ignite to store data sets bigger than can fit in the available memory. Essentially, the smaller operational data sets can be stored in-memory only, and larger data sets that do not fit in memory can be stored on disk, using memory as a caching layer for better performance.
-
-[Read More](https://apacheignite-net.readme.io/docs/ignite-persistent-store)
-
-#### Is Ignite a distributed database?
-**Yes**. Data in Ignite is either *partitioned* or *replicated* across a cluster of multiple nodes. This provides scalability and adds resilience to the system. Ignite automatically controls how data is partitioned, however, users can plug in their own distribution (affinity) functions and collocate various pieces of data together for efficiency.
-
-[Read More](https://apacheignite-net.readme.io/docs/sql-database)
-
-#### Is Ignite a relational SQL database?
-**Not fully**. Although Ignite aims to behave like any other relational SQL database, there are differences in how Ignite handles constraints and indexes. Ignite supports *primary* and *secondary* indexes, however, the *uniqueness* can only be enforced for the *primary* indexes. Ignite also does not support *foreign key* constraints.
-
-Essentially, Ignite purposely does not support any constraints that would entail a cluster broadcast message for each update and significantly hurt performance and scalability of the system.
-
-[Read More](https://apacheignite-net.readme.io/docs/sql-database)
-
-#### Is Ignite an in-memory database?
-**Yes**. Even though Ignite *durable memory* works well in-memory and on-disk, the disk persistence can be disabled and Ignite can act as a pure *in-memory database*.
-
-[Read More](https://apacheignite-net.readme.io/docs/sql-database)
-
-#### Is Ignite a transactional database?
-**Not fully**. ACID Transactions are supported, but only at *key-value* API level. Ignite also supports *cross-partition* transactions, which means that transactions can span keys residing in different partitions on different servers.
+GridGain.NET [Entity Framework Second Level Cache](https://apacheignite-net.readme.io/docs/entity-framework-second-level-cache) improves Entity Framework performance by storing query results in GridGain caches.
-At *SQL* level Ignite supports *atomic*, but not yet *transactional* consistency. Ignite community plans to implement SQL transactions in version 2.4.
-
-[Read More](https://apacheignite-net.readme.io/docs/sql-database)
-
-#### Is Ignite a key-value store?
-**Yes**. Ignite provides a feature rich key-value API, that is JCache (JSR-107) compliant and supports Java, C++, and .NET.
-
-[Read More](https://apacheignite-net.readme.io/docs/data-grid)
-
-#### Is Ignite an in-memory data grid?
-**Yes**. Ignite is a full-featured data grid, which can be used either in pure in-memory mode or with Ignite native persistence. It can also integrate with any 3rd party database, including any RDBMS or NoSQL store.
-
-[Read More](https://apacheignite-net.readme.io/docs/data-grid)
-
-#### What is durable memory?
-Ignite *durable memory* architecture allows Ignite to extend in-memory computing to disk. It is based on a paged-based off-heap memory allocator which becomes durable by persisting to the *write-ahead-log (WAL)* and, then, to main Ignite persistent storage. When persistence is disabled, durable memory acts like a pure in-memory storage.
-
-[Read More](https://apacheignite-net.readme.io/docs/durable-memory)
-
-#### What is collocated processing?
-Ignite is a distributed system and, therefore, it is important to be able to collocate data with data and compute with data to avoid distributed data noise. Data collocation becomes especially important when performing distributed SQL joins. Ignite also supports sending user logic (functions, lambdas, etc.) directly to the nodes where the data resides and computing on the data locally.
-
-[Read More](https://apacheignite-net.readme.io/docs/colocate-compute-and-data)
[apache-ignite-homepage]: https://ignite.apache.org/
-[getting-started]: https://apacheignite-net.readme.io/docs/getting-started-2
-[docs]: https://apacheignite-net.readme.io/docs
-
-## Contribute to Ignite.NET
-
-See [Ignite.NET Development](https://cwiki.apache.org/confluence/display/IGNITE/Ignite.NET+Development) on wiki.
-
-## Ignite On Other Platforms
-
-<a href="https://github.com/apache/ignite">Java</a>
-
-<a href="https://github.com/apache/ignite/tree/master/modules/platforms/cpp">Ignite C++</a>
\ No newline at end of file
+[GridGain-homepage]: https://www.gridgain.com/
+[getting-started]: https://docs.gridgain.com/docs
+[docs]: https://docs.gridgain.com/docs
diff --git a/modules/platforms/dotnet/README.txt b/modules/platforms/dotnet/README.txt
index 7521dfe..730bf48 100644
--- a/modules/platforms/dotnet/README.txt
+++ b/modules/platforms/dotnet/README.txt
@@ -1,21 +1,21 @@
-Apache Ignite.NET
+GridGain.NET
==================================
-Apache Ignite.NET provides a full featured .NET data grid and .NET compute grid functionality.
-Using Apache Ignite.NET APIs you can execute any computation closure on the grid,
+GridGain.NET provides a full featured .NET data grid and .NET compute grid functionality.
+Using GridGain.NET APIs you can execute any computation closure on the grid,
perform concurrent operations on the data stored in cache, start ACID transactions,
create distributed locks, subscribe for event listeners, etc.
Files list:
- * Apache.Ignite.exe - executable to start standalone Ignite.NET node.
+ * Apache.Ignite.exe - executable to start standalone GridGain.NET node.
* Apache.Ignite.exe.config - standalone node configuration file.
- * Apache.Ignite.Core.dll - Ignite.NET API library.
+ * Apache.Ignite.Core.dll - GridGain.NET API library.
* Apache.Ignite.Core.xml - Library XML documentation.
- * Apache.Ignite.Linq.dll - Ignite LINQ Provider library.
- * Apache.Ignite.AspNet.dll - Ignite ASP.NET integration.
- * Apache.Ignite.NLog.dll - Ignite NLog logger.
- * Apache.Ignite.Log4Net.dll - Ignite Log4Net logger.
+ * Apache.Ignite.Linq.dll - GridGain LINQ Provider library.
+ * Apache.Ignite.AspNet.dll - GridGain ASP.NET integration.
+ * Apache.Ignite.NLog.dll - GridGain NLog logger.
+ * Apache.Ignite.Log4Net.dll - GridGain Log4Net logger.
* IgniteConfigurationSection.xsd - Configuration XML schema.
@@ -32,7 +32,7 @@ Development
* Add Apache.Ignite.Core.dll to your project references.
- * To start Apache Ignite as a standalone node or Windows service use Apache.Ignite.exe.
+ * To start GridGain as a standalone node or Windows service use Apache.Ignite.exe.
Links
diff --git a/modules/platforms/dotnet/docfx/README.txt b/modules/platforms/dotnet/docfx/README.txt
index 4698356..fdfcab9 100644
--- a/modules/platforms/dotnet/docfx/README.txt
+++ b/modules/platforms/dotnet/docfx/README.txt
@@ -1,2 +1,2 @@
-Apache Ignite.NET DocFX Project
+GridGain.NET DocFX Project
See https://dotnet.github.io/docfx/ for more details.
\ No newline at end of file
diff --git a/modules/platforms/dotnet/examples/README.txt b/modules/platforms/dotnet/examples/README.txt
index db38a35..2c73dae 100644
--- a/modules/platforms/dotnet/examples/README.txt
+++ b/modules/platforms/dotnet/examples/README.txt
@@ -1,4 +1,4 @@
-Apache Ignite.NET Examples
+GridGain.NET Examples
==================================
Windows-only. See dotnetcore folder for cross-platform .NET-core based examples.
diff --git a/modules/platforms/dotnet/examples/dotnetcore/README.txt b/modules/platforms/dotnet/examples/dotnetcore/README.txt
index 26c6c1f..5690e1a 100644
--- a/modules/platforms/dotnet/examples/dotnetcore/README.txt
+++ b/modules/platforms/dotnet/examples/dotnetcore/README.txt
@@ -1,4 +1,4 @@
-Apache Ignite.NET Examples for .NET Core
+GridGain.NET Examples for .NET Core
========================================
Cross-platform examples, run on Windows, Linux, macOS.
diff --git a/modules/platforms/nodejs/README.md b/modules/platforms/nodejs/README.md
index 4792caa..f3ef6ed 100644
--- a/modules/platforms/nodejs/README.md
+++ b/modules/platforms/nodejs/README.md
@@ -1,4 +1,4 @@
-# NodeJS Client for Apache Ignite #
+# NodeJS Client for GridGain #
## Installation ##
@@ -29,4 +29,4 @@ npm link
npm link apache-ignite-client #linking examples (optional)
```
-For more information, see [Apache Ignite Node.JS Thin Client documentation](https://apacheignite.readme.io/docs/nodejs-thin-client).
+For more information, see [GridGain Node.JS Thin Client documentation](https://apacheignite.readme.io/docs/nodejs-thin-client).
\ No newline at end of file
diff --git a/modules/platforms/php/README.md b/modules/platforms/php/README.md
index d6cd51d..b8e9610 100644
--- a/modules/platforms/php/README.md
+++ b/modules/platforms/php/README.md
@@ -1,4 +1,4 @@
-# PHP Thin Client #
+# PHP Thin Client for GridGain #
## Installation ##
@@ -34,4 +34,4 @@ To use the client in your application, include `vendor/autoload.php` file, gener
require_once "<local_ignite_path>/vendor/autoload.php";
```
-For more information, see [Apache Ignite PHP Thin Client documentation](https://apacheignite.readme.io/docs/php-thin-client).
+For more information, see [GridGain PHP Thin Client documentation](https://apacheignite.readme.io/docs/php-thin-client).
\ No newline at end of file
diff --git a/modules/platforms/python/LICENSE b/modules/platforms/python/LICENSE
index d645695..4f2f7db 100644
--- a/modules/platforms/python/LICENSE
+++ b/modules/platforms/python/LICENSE
@@ -1,202 +1,13 @@
+Copyright 2019 GridGain Systems, Inc. and Contributors.
- Apache License
- Version 2.0, January 2004
- http://www.apache.org/licenses/
+Licensed under the GridGain Community Edition License (the "License");
+you may not use this file except in compliance with the License.
+You may obtain a copy of the License at
- TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+ https://www.gridgain.com/products/software/community-edition/gridgain-community-edition-license
- 1. Definitions.
-
- "License" shall mean the terms and conditions for use, reproduction,
- and distribution as defined by Sections 1 through 9 of this document.
-
- "Licensor" shall mean the copyright owner or entity authorized by
- the copyright owner that is granting the License.
-
- "Legal Entity" shall mean the union of the acting entity and all
- other entities that control, are controlled by, or are under common
- control with that entity. For the purposes of this definition,
- "control" means (i) the power, direct or indirect, to cause the
- direction or management of such entity, whether by contract or
- otherwise, or (ii) ownership of fifty percent (50%) or more of the
- outstanding shares, or (iii) beneficial ownership of such entity.
-
- "You" (or "Your") shall mean an individual or Legal Entity
- exercising permissions granted by this License.
-
- "Source" form shall mean the preferred form for making modifications,
- including but not limited to software source code, documentation
- source, and configuration files.
-
- "Object" form shall mean any form resulting from mechanical
- transformation or translation of a Source form, including but
- not limited to compiled object code, generated documentation,
- and conversions to other media types.
-
- "Work" shall mean the work of authorship, whether in Source or
- Object form, made available under the License, as indicated by a
- copyright notice that is included in or attached to the work
- (an example is provided in the Appendix below).
-
- "Derivative Works" shall mean any work, whether in Source or Object
- form, that is based on (or derived from) the Work and for which the
- editorial revisions, annotations, elaborations, or other modifications
- represent, as a whole, an original work of authorship. For the purposes
- of this License, Derivative Works shall not include works that remain
- separable from, or merely link (or bind by name) to the interfaces of,
- the Work and Derivative Works thereof.
-
- "Contribution" shall mean any work of authorship, including
- the original version of the Work and any modifications or additions
- to that Work or Derivative Works thereof, that is intentionally
- submitted to Licensor for inclusion in the Work by the copyright owner
- or by an individual or Legal Entity authorized to submit on behalf of
- the copyright owner. For the purposes of this definition, "submitted"
- means any form of electronic, verbal, or written communication sent
- to the Licensor or its representatives, including but not limited to
- communication on electronic mailing lists, source code control systems,
- and issue tracking systems that are managed by, or on behalf of, the
- Licensor for the purpose of discussing and improving the Work, but
- excluding communication that is conspicuously marked or otherwise
- designated in writing by the copyright owner as "Not a Contribution."
-
- "Contributor" shall mean Licensor and any individual or Legal Entity
- on behalf of whom a Contribution has been received by Licensor and
- subsequently incorporated within the Work.
-
- 2. Grant of Copyright License. Subject to the terms and conditions of
- this License, each Contributor hereby grants to You a perpetual,
- worldwide, non-exclusive, no-charge, royalty-free, irrevocable
- copyright license to reproduce, prepare Derivative Works of,
- publicly display, publicly perform, sublicense, and distribute the
- Work and such Derivative Works in Source or Object form.
-
- 3. Grant of Patent License. Subject to the terms and conditions of
- this License, each Contributor hereby grants to You a perpetual,
- worldwide, non-exclusive, no-charge, royalty-free, irrevocable
- (except as stated in this section) patent license to make, have made,
- use, offer to sell, sell, import, and otherwise transfer the Work,
- where such license applies only to those patent claims licensable
- by such Contributor that are necessarily infringed by their
- Contribution(s) alone or by combination of their Contribution(s)
- with the Work to which such Contribution(s) was submitted. If You
- institute patent litigation against any entity (including a
- cross-claim or counterclaim in a lawsuit) alleging that the Work
- or a Contribution incorporated within the Work constitutes direct
- or contributory patent infringement, then any patent licenses
- granted to You under this License for that Work shall terminate
- as of the date such litigation is filed.
-
- 4. Redistribution. You may reproduce and distribute copies of the
- Work or Derivative Works thereof in any medium, with or without
- modifications, and in Source or Object form, provided that You
- meet the following conditions:
-
- (a) You must give any other recipients of the Work or
- Derivative Works a copy of this License; and
-
- (b) You must cause any modified files to carry prominent notices
- stating that You changed the files; and
-
- (c) You must retain, in the Source form of any Derivative Works
- that You distribute, all copyright, patent, trademark, and
- attribution notices from the Source form of the Work,
- excluding those notices that do not pertain to any part of
- the Derivative Works; and
-
- (d) If the Work includes a "NOTICE" text file as part of its
- distribution, then any Derivative Works that You distribute must
- include a readable copy of the attribution notices contained
- within such NOTICE file, excluding those notices that do not
- pertain to any part of the Derivative Works, in at least one
- of the following places: within a NOTICE text file distributed
- as part of the Derivative Works; within the Source form or
- documentation, if provided along with the Derivative Works; or,
- within a display generated by the Derivative Works, if and
- wherever such third-party notices normally appear. The contents
- of the NOTICE file are for informational purposes only and
- do not modify the License. You may add Your own attribution
- notices within Derivative Works that You distribute, alongside
- or as an addendum to the NOTICE text from the Work, provided
- that such additional attribution notices cannot be construed
- as modifying the License.
-
- You may add Your own copyright statement to Your modifications and
- may provide additional or different license terms and conditions
- for use, reproduction, or distribution of Your modifications, or
- for any such Derivative Works as a whole, provided Your use,
- reproduction, and distribution of the Work otherwise complies with
- the conditions stated in this License.
-
- 5. Submission of Contributions. Unless You explicitly state otherwise,
- any Contribution intentionally submitted for inclusion in the Work
- by You to the Licensor shall be under the terms and conditions of
- this License, without any additional terms or conditions.
- Notwithstanding the above, nothing herein shall supersede or modify
- the terms of any separate license agreement you may have executed
- with Licensor regarding such Contributions.
-
- 6. Trademarks. This License does not grant permission to use the trade
- names, trademarks, service marks, or product names of the Licensor,
- except as required for reasonable and customary use in describing the
- origin of the Work and reproducing the content of the NOTICE file.
-
- 7. Disclaimer of Warranty. Unless required by applicable law or
- agreed to in writing, Licensor provides the Work (and each
- Contributor provides its Contributions) on an "AS IS" BASIS,
- WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
- implied, including, without limitation, any warranties or conditions
- of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
- PARTICULAR PURPOSE. You are solely responsible for determining the
- appropriateness of using or redistributing the Work and assume any
- risks associated with Your exercise of permissions under this License.
-
- 8. Limitation of Liability. In no event and under no legal theory,
- whether in tort (including negligence), contract, or otherwise,
- unless required by applicable law (such as deliberate and grossly
- negligent acts) or agreed to in writing, shall any Contributor be
- liable to You for damages, including any direct, indirect, special,
- incidental, or consequential damages of any character arising as a
- result of this License or out of the use or inability to use the
- Work (including but not limited to damages for loss of goodwill,
- work stoppage, computer failure or malfunction, or any and all
- other commercial damages or losses), even if such Contributor
- has been advised of the possibility of such damages.
-
- 9. Accepting Warranty or Additional Liability. While redistributing
- the Work or Derivative Works thereof, You may choose to offer,
- and charge a fee for, acceptance of support, warranty, indemnity,
- or other liability obligations and/or rights consistent with this
- License. However, in accepting such obligations, You may act only
- on Your own behalf and on Your sole responsibility, not on behalf
- of any other Contributor, and only if You agree to indemnify,
- defend, and hold each Contributor harmless for any liability
- incurred by, or claims asserted against, such Contributor by reason
- of your accepting any such warranty or additional liability.
-
- END OF TERMS AND CONDITIONS
-
- APPENDIX: How to apply the Apache License to your work.
-
- To apply the Apache License to your work, attach the following
- boilerplate notice, with the fields enclosed by brackets "[]"
- replaced with your own identifying information. (Don't include
- the brackets!) The text should be enclosed in the appropriate
- comment syntax for the file format. We also recommend that a
- file or class name and description of purpose be included on the
- same "printed page" as the copyright notice for easier
- identification within third-party archives.
-
- Copyright [yyyy] [name of copyright owner]
-
- Licensed under the Apache License, Version 2.0 (the "License");
- you may not use this file except in compliance with the License.
- You may obtain a copy of the License at
-
- http://www.apache.org/licenses/LICENSE-2.0
-
- Unless required by applicable law or agreed to in writing, software
- distributed under the License is distributed on an "AS IS" BASIS,
- WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
- See the License for the specific language governing permissions and
- limitations under the License.
+Unless required by applicable law or agreed to in writing, software
+distributed under the License is distributed on an "AS IS" BASIS,
+WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+See the License for the specific language governing permissions and
+limitations under the License.
\ No newline at end of file
diff --git a/modules/rest-http/README.txt b/modules/rest-http/README.txt
index 0df2cf5..3e6b3b2 100644
--- a/modules/rest-http/README.txt
+++ b/modules/rest-http/README.txt
@@ -1,7 +1,7 @@
-Apache Ignite REST-HTTP Module
+GridGain REST-HTTP Module
------------------------------
-Apache Ignite REST-HTTP module provides Jetty-based server which can be used to execute tasks and/or cache commands
+GridGain REST-HTTP module provides Jetty-based server which can be used to execute tasks and/or cache commands
in grid using REST approach via HTTP protocol.
To enable REST-HTTP module when starting a standalone node, move 'optional/ignite-rest-http' folder to
@@ -12,7 +12,7 @@ Importing REST-HTTP Module In Maven Project
-------------------------------------------
If you are using Maven to manage dependencies of your project, you can add REST-HTTP module
-dependency like this (replace '${ignite.version}' with actual Ignite version you are
+dependency like this (replace '${ignite.version}' with actual GridGain version you are
interested in):
<project xmlns="http://maven.apache.org/POM/4.0.0"
@@ -23,7 +23,7 @@ interested in):
<dependencies>
...
<dependency>
- <groupId>org.apache.ignite</groupId>
+ <groupId>org.gridgain</groupId>
<artifactId>ignite-rest-http</artifactId>
<version>${ignite.version}</version>
</dependency>
diff --git a/modules/rocketmq/README.txt b/modules/rocketmq/README.txt
index 55a117b..d130dd9 100644
--- a/modules/rocketmq/README.txt
+++ b/modules/rocketmq/README.txt
@@ -1,9 +1,9 @@
-Apache Ignite RocketMQ Streamer Module
+GridGain RocketMQ Streamer Module
--------------------------------------
-Apache Ignite RocketMQ Streamer module provides streaming from RocketMQ to Ignite cache.
+GridGain RocketMQ Streamer module provides streaming from RocketMQ to GridGain cache.
-To use Ignite RocketMQ Streamer module, first import it to your Maven project.
+To use GridGain RocketMQ Streamer module, first import it to your Maven project.
<project xmlns="http://maven.apache.org/POM/4.0.0"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
@@ -13,7 +13,7 @@ To use Ignite RocketMQ Streamer module, first import it to your Maven project.
<dependencies>
...
<dependency>
- <groupId>org.apache.ignite</groupId>
+ <groupId>org.gridgain</groupId>
<artifactId>ignite-rocketmq</artifactId>
<version>${ignite.version}</version>
</dependency>
diff --git a/modules/scalar-2.10/README.txt b/modules/scalar-2.10/README.txt
index 535a193..f0092a6 100644
--- a/modules/scalar-2.10/README.txt
+++ b/modules/scalar-2.10/README.txt
@@ -1,4 +1,4 @@
-Apache Ignite Scalar Module
+GridGain Scalar Module
---------------------------
-Apache Ignite Scalar module to be build with Scala 2.10.
+GridGain Scalar module to be build with Scala 2.10.
diff --git a/modules/scalar/README.txt b/modules/scalar/README.txt
index 38c5879..1ecaa3f 100644
--- a/modules/scalar/README.txt
+++ b/modules/scalar/README.txt
@@ -1,7 +1,7 @@
-Apache Ignite Scalar Module
+GridGain Scalar Module
---------------------------
-Apache Ignite Scalar module provides Scala-based DSL with extensions and shortcuts for Apache Ignite API.
+GridGain Scalar module provides Scala-based DSL with extensions and shortcuts for GridGain API.
To enable Scalar module when starting a standalone node, move 'optional/ignite-scalar' folder to
'libs' folder before running 'ignite.{sh|bat}' script. The content of the module folder will
@@ -11,7 +11,7 @@ Importing Scalar Module In Maven Project
----------------------------------------
If you are using Maven to manage dependencies of your project, you can add Scalar module
-dependency like this (replace '${ignite.version}' with actual Ignite version you are
+dependency like this (replace '${ignite.version}' with actual GridGain version you are
interested in):
<project xmlns="http://maven.apache.org/POM/4.0.0"
@@ -22,7 +22,7 @@ interested in):
<dependencies>
...
<dependency>
- <groupId>org.apache.ignite</groupId>
+ <groupId>org.gridgain</groupId>
<artifactId>ignite-scalar</artifactId>
<version>${ignite.version}</version>
</dependency>
diff --git a/modules/schedule/README.txt b/modules/schedule/README.txt
index 27490c4..b05dbe2 100644
--- a/modules/schedule/README.txt
+++ b/modules/schedule/README.txt
@@ -1,7 +1,7 @@
-Apache Ignite Schedule Module
+GridGain Schedule Module
-----------------------------
-Apache Ignite Schedule module provides functionality for scheduling jobs locally using UNIX cron-based syntax.
+GridGain Schedule module provides functionality for scheduling jobs locally using UNIX cron-based syntax.
To enable Schedule module when starting a standalone node, move 'optional/ignite-schedule' folder to
'libs' folder before running 'ignite.{sh|bat}' script. The content of the module folder will
@@ -11,7 +11,7 @@ Importing Schedule Module In Maven Project
------------------------------------------
If you are using Maven to manage dependencies of your project, you can add Schedule module
-dependency like this (replace '${ignite.version}' with actual Ignite version you are
+dependency like this (replace '${ignite.version}' with actual GridGain version you are
interested in):
<project xmlns="http://maven.apache.org/POM/4.0.0"
@@ -22,7 +22,7 @@ interested in):
<dependencies>
...
<dependency>
- <groupId>org.apache.ignite</groupId>
+ <groupId>org.gridgain</groupId>
<artifactId>ignite-schedule</artifactId>
<version>${ignite.version}</version>
</dependency>
@@ -35,13 +35,13 @@ interested in):
LGPL dependencies
-----------------
-Ignite includes the following optional LGPL dependencies:
+GridGain includes the following optional LGPL dependencies:
- Hibernate L2 Cache Integration, http://hibernate.org/orm/
- JTS Topology Suite for Geospatial indexing, http://tsusiatsoftware.net/jts/main.html
- cron4j for cron-based task scheduling, http://www.sauronsoftware.it/projects/cron4j
-Apache binary releases cannot include LGPL dependencies. If you would like include
+GridGain binary releases cannot include LGPL dependencies. If you would like include
optional LGPL dependencies into your release, you should download the source release
-from Ignite website and do the build with the following maven command:
+from GridGain website and do the build with the following maven command:
mvn clean package -DskipTests -Prelease,lgpl
diff --git a/modules/slf4j/README.txt b/modules/slf4j/README.txt
index 2583ce3..d44dcf5 100644
--- a/modules/slf4j/README.txt
+++ b/modules/slf4j/README.txt
@@ -1,7 +1,7 @@
-Apache Ignite SLF4J Module
+GridGain SLF4J Module
--------------------------
-Apache Ignite SLF4J module provides GridLogger implementation based on SLF4J.
+GridGain SLF4J module provides GridLogger implementation based on SLF4J.
To enable SLF4J module when starting a standalone node, move 'optional/ignite-slf4j' folder to
'libs' folder before running 'ignite.{sh|bat}' script. The content of the module folder will
@@ -11,7 +11,7 @@ Importing SLF4J Module In Maven Project
---------------------------------------
If you are using Maven to manage dependencies of your project, you can add SLF4J module
-dependency like this (replace '${ignite.version}' with actual Ignite version you are
+dependency like this (replace '${ignite.version}' with actual GridGain version you are
interested in):
<project xmlns="http://maven.apache.org/POM/4.0.0"
@@ -22,7 +22,7 @@ interested in):
<dependencies>
...
<dependency>
- <groupId>org.apache.ignite</groupId>
+ <groupId>org.gridgain</groupId>
<artifactId>ignite-slf4j</artifactId>
<version>${ignite.version}</version>
</dependency>
diff --git a/modules/spark/README.txt b/modules/spark/README.txt
index 589a050..a612837 100644
--- a/modules/spark/README.txt
+++ b/modules/spark/README.txt
@@ -1,8 +1,8 @@
-Apache Ignite Spark Module
+GridGain Spark Module
---------------------------
-Apache Ignite provides an implementation of Spark RDD abstraction which enables easy access to Ignite caches.
-Ignite RDD does not keep it's state in the memory of the Spark application and provides a view of the corresponding
-Ignite cache. Depending on the chosen deployment mode this state may exist only during the lifespan of the Spark
+GridGain provides an implementation of Spark RDD abstraction which enables easy access to GridGain caches.
+GridGain RDD does not keep it's state in the memory of the Spark application and provides a view of the corresponding
+GridGain cache. Depending on the chosen deployment mode this state may exist only during the lifespan of the Spark
application (embedded mode) or may exist outside of the Spark application (standalone mode), allowing seamless
sharing of the state between multiple Spark jobs.
\ No newline at end of file
diff --git a/modules/spring-data-2.0/README.txt b/modules/spring-data-2.0/README.txt
index f74d97a..fbc81d3 100644
--- a/modules/spring-data-2.0/README.txt
+++ b/modules/spring-data-2.0/README.txt
@@ -1,7 +1,7 @@
-Apache Ignite Spring Module
+GridGain Spring Module
---------------------------
-Apache Ignite Spring Data 2.0 module provides an integration with Spring Data 2.0 framework.
+GridGain Spring Data 2.0 module provides an integration with Spring Data 2.0 framework.
To enable Spring Data 2.0 module when starting a standalone node, move 'optional/ignite-spring-data' folder to
'libs' folder before running 'ignite.{sh|bat}' script. The content of the module folder will
@@ -11,7 +11,7 @@ Importing Spring Data 2.0 Module In Maven Project
----------------------------------------
If you are using Maven to manage dependencies of your project, you can add Spring module
-dependency like this (replace '${ignite.version}' with actual Ignite version you are
+dependency like this (replace '${ignite.version}' with actual GridGain version you are
interested in):
<project xmlns="http://maven.apache.org/POM/4.0.0"
@@ -22,7 +22,7 @@ interested in):
<dependencies>
...
<dependency>
- <groupId>org.apache.ignite</groupId>
+ <groupId>org.gridgain</groupId>
<artifactId>ignite-spring-data_2.0</artifactId>
<version>${ignite.version}</version>
</dependency>
diff --git a/modules/spring-data/README.txt b/modules/spring-data/README.txt
index d957fb6..5c8c179 100644
--- a/modules/spring-data/README.txt
+++ b/modules/spring-data/README.txt
@@ -1,7 +1,7 @@
-Apache Ignite Spring Module
+GridGain Spring Module
---------------------------
-Apache Ignite Spring Data module provides an integration with Spring Data framework.
+GridGain Spring Data module provides an integration with Spring Data framework.
To enable Spring Data module when starting a standalone node, move 'optional/ignite-spring-data' folder to
'libs' folder before running 'ignite.{sh|bat}' script. The content of the module folder will
@@ -22,7 +22,7 @@ interested in):
<dependencies>
...
<dependency>
- <groupId>org.apache.ignite</groupId>
+ <groupId>org.gridgain</groupId>
<artifactId>ignite-spring-data</artifactId>
<version>${ignite.version}</version>
</dependency>
diff --git a/modules/spring/README.txt b/modules/spring/README.txt
index 24718b7..1cff1d3 100644
--- a/modules/spring/README.txt
+++ b/modules/spring/README.txt
@@ -1,7 +1,7 @@
-Apache Ignite Spring Module
+GridGain Spring Module
---------------------------
-Apache Ignite Spring module provides resources injection capabilities and parser for Spring-based
+GridGain Spring module provides resources injection capabilities and parser for Spring-based
configuration XML files.
To enable Spring module when starting a standalone node, move 'optional/ignite-spring' folder to
@@ -12,7 +12,7 @@ Importing Spring Module In Maven Project
----------------------------------------
If you are using Maven to manage dependencies of your project, you can add Spring module
-dependency like this (replace '${ignite.version}' with actual Ignite version you are
+dependency like this (replace '${ignite.version}' with actual GridGain version you are
interested in):
<project xmlns="http://maven.apache.org/POM/4.0.0"
@@ -23,7 +23,7 @@ interested in):
<dependencies>
...
<dependency>
- <groupId>org.apache.ignite</groupId>
+ <groupId>org.gridgain</groupId>
<artifactId>ignite-spring</artifactId>
<version>${ignite.version}</version>
</dependency>
diff --git a/modules/ssh/README.txt b/modules/ssh/README.txt
index a0876e7..c069740 100644
--- a/modules/ssh/README.txt
+++ b/modules/ssh/README.txt
@@ -1,7 +1,7 @@
-Apache Ignite SSH Module
+GridGain SSH Module
------------------------
-Apache Ignite SSH module provides capabilities to start Apache Ignite nodes on remote machines via SSH.
+GridGain SSH module provides capabilities to start GridGain nodes on remote machines via SSH.
To enable SSH module when starting a standalone node, move 'optional/ignite-ssh' folder to
'libs' folder before running 'ignite.{sh|bat}' script. The content of the module folder will
@@ -11,7 +11,7 @@ Importing SSH Module In Maven Project
-------------------------------------
If you are using Maven to manage dependencies of your project, you can add SSH module
-dependency like this (replace '${ignite.version}' with actual Ignite version you are
+dependency like this (replace '${ignite.version}' with actual GridGain version you are
interested in):
<project xmlns="http://maven.apache.org/POM/4.0.0"
@@ -22,7 +22,7 @@ interested in):
<dependencies>
...
<dependency>
- <groupId>org.apache.ignite</groupId>
+ <groupId>org.gridgain</groupId>
<artifactId>ignite-ssh</artifactId>
<version>${ignite.version}</version>
</dependency>
diff --git a/modules/storm/README.txt b/modules/storm/README.txt
index 684fdb5..567b11d 100644
--- a/modules/storm/README.txt
+++ b/modules/storm/README.txt
@@ -1,14 +1,14 @@
-Apache Ignite Storm Streamer Module
+GridGain Storm Streamer Module
-----------------------------------
-Apache Ignite Storm Streamer module provides streaming via Storm to Ignite cache.
+GridGain Storm Streamer module provides streaming via Storm to GridGain cache.
-Starting data transfer to Ignite cache can be done with the following steps.
+Starting data transfer to GridGain cache can be done with the following steps.
-1. Import Ignite Storm Streamer Module In Maven Project
+1. Import GridGain Storm Streamer Module In Maven Project
If you are using Maven to manage dependencies of your project, you can add Storm module
-dependency like this (replace '${ignite.version}' with actual Ignite version you are
+dependency like this (replace '${ignite.version}' with actual GridGain version you are
interested in):
<project xmlns="http://maven.apache.org/POM/4.0.0"
@@ -19,7 +19,7 @@ interested in):
<dependencies>
...
<dependency>
- <groupId>org.apache.ignite</groupId>
+ <groupId>org.gridgain</groupId>
<artifactId>ignite-storm</artifactId>
<version>${ignite.version}</version>
</dependency>
@@ -28,7 +28,7 @@ interested in):
...
</project>
-2. Create an Ignite configuration file (see example-ignite.xml) and make sure it is accessible from the streamer.
+2. Create an GridGain configuration file (see example-ignite.xml) and make sure it is accessible from the streamer.
3. Make sure your key-value data input to the streamer is specified with the field named "ignite"
(or a different one you configure with StormStreamer.setIgniteTupleField(...)).
diff --git a/modules/tensorflow/README.txt b/modules/tensorflow/README.txt
index 21ea88d..08fc397 100644
--- a/modules/tensorflow/README.txt
+++ b/modules/tensorflow/README.txt
@@ -1,14 +1,14 @@
-Apache Ignite TensorFlow Integration Module
+GridGain TensorFlow Integration Module
------------------------
-Apache Ignite TensorFlow Integration Module allowed using TensorFlow with Apache Ignite. In this scenario Apache Ignite
+GridGain TensorFlow Integration Module allowed using TensorFlow with GridGain. In this scenario GridGain
will be a datasource for any TensorFlow model training.
-Import Apache Ignite TensorFlow Integration Module In Maven Project
+Import GridGain TensorFlow Integration Module In Maven Project
-------------------------------------
If you are using Maven to manage dependencies of your project, you can add TensorFlow module
-dependency like this (replace '${ignite.version}' with actual Ignite version you are
+dependency like this (replace '${ignite.version}' with actual GridGain version you are
interested in):
<project xmlns="http://maven.apache.org/POM/4.0.0"
@@ -19,7 +19,7 @@ interested in):
<dependencies>
...
<dependency>
- <groupId>org.apache.ignite</groupId>
+ <groupId>org.gridgain</groupId>
<artifactId>ignite-tensorflow</artifactId>
<version>${ignite.version}</version>
</dependency>
@@ -30,13 +30,13 @@ interested in):
-------------------------------------
TensorFlow integration module provides command line tool that allows to start, maintain and stop distributed deep
-learning utilizing Apache Ignite infrastructure and data. This tool provides several commands that are shown here:
+learning utilizing GridGain infrastructure and data. This tool provides several commands that are shown here:
Usage: ignite-tf [-hV] [-c=<cfg>] [COMMAND]
-Apache Ignite and TensorFlow integration command line utility that allows to
-start, maintain and stop distributed deep learning utilizing Apache Ignite
+GridGain and TensorFlow integration command line utility that allows to
+start, maintain and stop distributed deep learning utilizing GridGain
infrastructure and data.
- -c, --config=<cfg> Apache Ignite client configuration.
+ -c, --config=<cfg> GridGain client configuration.
-h, --help Show this help message and exit.
-V, --version Print version information and exit.
Commands:
@@ -55,7 +55,7 @@ Starts a new TensorFlow cluster and attaches to user script process.
JOB_DIR Job folder (or zip archive).
JOB_CMD Job command.
[JOB_ARGS...] Job arguments.
- -c, --config=<cfg> Apache Ignite client configuration.
+ -c, --config=<cfg> GridGain client configuration.
-h, --help Show this help message and exit.
-V, --version Print version information and exit.
@@ -65,16 +65,16 @@ commands accepts cluster identifier as a parameter:
Usage: ignite-tf attach [-hV] [-c=<cfg>] CLUSTER_ID
Attaches to running TensorFlow cluster (user script process).
CLUSTER_ID Cluster identifier.
- -c, --config=<cfg> Apache Ignite client configuration.
+ -c, --config=<cfg> GridGain client configuration.
-h, --help Show this help message and exit.
-V, --version Print version information and exit.
Usage: ignite-tf stop [-hV] [-c=<cfg>] CLUSTER_ID
Stops a running TensorFlow cluster.
CLUSTER_ID Cluster identifier.
- -c, --config=<cfg> Apache Ignite client configuration.
+ -c, --config=<cfg> GridGain client configuration.
-h, --help Show this help message and exit.
-V, --version Print version information and exit.
-To find out what TensorFlow clusters are currently running on top of Apache Ignite you can use "ps" command that doesn't
+To find out what TensorFlow clusters are currently running on top of GridGain you can use "ps" command that doesn't
require arguments.
\ No newline at end of file
diff --git a/modules/twitter/README.txt b/modules/twitter/README.txt
index 1c412f9..2838a2a 100644
--- a/modules/twitter/README.txt
+++ b/modules/twitter/README.txt
@@ -1,17 +1,17 @@
-Apache Ignite Twitter Streamer Module
+GridGain Twitter Streamer Module
------------------------
-Apache Ignite Twitter Streamer module provides streaming from Twitter to Ignite cache.
+GridGain Twitter Streamer module provides streaming from Twitter to GridGain cache.
To enable Twitter Streamer module when starting a standalone node, move 'optional/ignite-twitter' folder to
'libs' folder before running 'ignite.{sh|bat}' script. The content of the module folder will
be added to classpath in this case.
-Importing Ignite Twitter Streamer Module In Maven Project
+Importing GridGain Twitter Streamer Module In Maven Project
-------------------------------------
If you are using Maven to manage dependencies of your project, you can add JCL module
-dependency like this (replace '${ignite.version}' with actual Ignite version you are
+dependency like this (replace '${ignite.version}' with actual GridGain version you are
interested in):
<project xmlns="http://maven.apache.org/POM/4.0.0"
@@ -22,7 +22,7 @@ interested in):
<dependencies>
...
<dependency>
- <groupId>org.apache.ignite</groupId>
+ <groupId>org.gridgain</groupId>
<artifactId>ignite-twitter</artifactId>
<version>${ignite.version}</version>
</dependency>
diff --git a/modules/urideploy/README.txt b/modules/urideploy/README.txt
index dc3defd..4637d1b 100644
--- a/modules/urideploy/README.txt
+++ b/modules/urideploy/README.txt
@@ -1,7 +1,7 @@
-Apache Ignite URI Deploy Module
+GridGain URI Deploy Module
-------------------------------
-Apache Ignite URI Deploy module provides capabilities to deploy tasks from different sources like
+GridGain URI Deploy module provides capabilities to deploy tasks from different sources like
File System, HTTP, or even Email.
To enable URI Deploy module when starting a standalone node, move 'optional/ignite-urideploy' folder to
@@ -12,7 +12,7 @@ Importing URI Deploy Module In Maven Project
--------------------------------------------
If you are using Maven to manage dependencies of your project, you can add URI Deploy module
-dependency like this (replace '${ignite.version}' with actual Ignite version you are
+dependency like this (replace '${ignite.version}' with actual GridGain version you are
interested in):
<project xmlns="http://maven.apache.org/POM/4.0.0"
@@ -23,7 +23,7 @@ interested in):
<dependencies>
...
<dependency>
- <groupId>org.apache.ignite</groupId>
+ <groupId>org.gridgain</groupId>
<artifactId>ignite-urideploy</artifactId>
<version>${ignite.version}</version>
</dependency>
diff --git a/modules/visor-console-2.10/README.txt b/modules/visor-console-2.10/README.txt
index 1a018b9..d38c9ec 100644
--- a/modules/visor-console-2.10/README.txt
+++ b/modules/visor-console-2.10/README.txt
@@ -1,4 +1,4 @@
-Apache Ignite Visor Console Module
+GridGain Visor Console Module
---------------------------
-Apache Ignite Visor Console module to be build with Scala 2.10.
+GridGain Visor Console module to be build with Scala 2.10.
diff --git a/modules/web-console/README.txt b/modules/web-console/README.txt
index 286082c..ce0dd6f 100644
--- a/modules/web-console/README.txt
+++ b/modules/web-console/README.txt
@@ -1,9 +1,9 @@
-Ignite Web Console
+GridGain Web Console
======================================
-An Interactive Configuration Wizard and Management Tool for Apache Ignite
+An Interactive Configuration Wizard and Management Tool for GridGain
-The Apache Ignite Web Console includes an interactive configuration wizard which helps you create and download configuration
- files for your Apache Ignite cluster. The tool also provides management capabilities which allow you to run SQL queries
+The GridGain Web Console includes an interactive configuration wizard which helps you create and download configuration
+ files for your GridGain cluster. The tool also provides management capabilities which allow you to run SQL queries
on your in-memory cache as well as view execution plans, in-memory schema, and streaming charts.
In order to simplify evaluation of Web Console demo mode was implemented.
@@ -21,7 +21,7 @@ In order to simplify evaluation of Web Console demo mode was implemented.
Demo for SQL.
How to evaluate:
- In this mode internal Ignite node will be started. Cache created and populated with data.
+ In this mode internal GridGain node will be started. Cache created and populated with data.
1) Click "SQL" in Ignite Web Console top menu.
2) "Demo" notebook with preconfigured queries will be opened.
3) You can also execute any SQL queries for tables: "Country, Department, Employee, Parking, Car".
diff --git a/modules/web-console/assembly/README.txt b/modules/web-console/assembly/README.txt
index e88e345..88ee192 100644
--- a/modules/web-console/assembly/README.txt
+++ b/modules/web-console/assembly/README.txt
@@ -2,7 +2,7 @@ Requirements
-------------------------------------
1. JDK 8 suitable for your platform.
2. Supported browsers: Chrome, Firefox, Safari, Edge.
-3. Ignite cluster should be started with `ignite-rest-http` module in classpath.
+3. GridGain cluster should be started with `ignite-rest-http` module in classpath.
For this copy `ignite-rest-http` folder from `libs\optional` to `libs` folder.
How to run
diff --git a/modules/web-console/web-agent/README.txt b/modules/web-console/web-agent/README.txt
index 6b29902..db94bea 100644
--- a/modules/web-console/web-agent/README.txt
+++ b/modules/web-console/web-agent/README.txt
@@ -1,11 +1,11 @@
Ignite Web Agent
======================================
-Ignite Web Agent is a java standalone application that allow to connect Ignite Grid to Ignite Web Console.
+Ignite Web Agent is a java standalone application that allow to connect GridGain Grid to Ignite Web Console.
Ignite Web Agent communicates with grid nodes via REST interface and connects to Ignite Web Console via web-socket.
Two main functions of Ignite Web Agent:
- 1. Proxy between Ignite Web Console and Ignite Grid to execute SQL statements and collect metrics for monitoring.
- You may need to specify URI for connect to Ignite REST server via "-n" option.
+ 1. Proxy between Ignite Web Console and GridGain Grid to execute SQL statements and collect metrics for monitoring.
+ You may need to specify URI for connect to GridGain REST server via "-n" option.
2. Proxy between Ignite Web Console and user RDBMS to collect database metadata for later indexed types configuration.
You may need to copy JDBC driver into "./jdbc-drivers" subfolder or specify path via "-d" option.
@@ -44,9 +44,9 @@ Security tokens:
3) One may specify several comma-separated list of tokens using configuration file or command line arguments of web agent.
Ignite Web agent requirements:
- 1) In order to communicate with web agent Ignite node should be started with REST server (copy "ignite-rest-http" folder from "libs/optional/" to "libs/").
+ 1) In order to communicate with web agent GridGain node should be started with REST server (copy "ignite-rest-http" folder from "libs/optional/" to "libs/").
2) Configure web agent server-uri property with address where Web Console is running.
- 3) Configure web agent node-uri property with Ignite nodes URI(s).
+ 3) Configure web agent node-uri property with GridGain nodes URI(s).
Options:
-h, --help
@@ -58,7 +58,7 @@ Options:
Path to folder with JDBC drivers
Default value: ./jdbc-drivers
-n, --node-uri
- Comma-separated list of URIs for connect to Ignite node via REST
+ Comma-separated list of URIs for connect to GridGain node via REST
Default value: http://localhost:8080
-nl, --node-login
User name that will be used to connect to secured cluster
@@ -90,7 +90,7 @@ Options:
to server and cluster
How to build:
- To build from sources run following command in Ignite project root folder:
+ To build from sources run following command in GridGain project root folder:
mvn clean package -pl :ignite-web-agent -am -P web-console -DskipTests=true
Demo of Ignite Web Agent:
@@ -109,7 +109,7 @@ Demo of Ignite Web Agent:
2) Demo for SQL.
How to evaluate:
- In this mode internal Ignite node will be started. Cache created and populated with data.
+ In this mode internal GridGain node will be started. Cache created and populated with data.
2.1) Click "SQL" in Ignite Web Console top menu.
2.2) "Demo" notebook with preconfigured queries will be opened.
2.3) You can also execute any SQL queries for tables: "Country, Department, Employee, Parking, Car".
diff --git a/modules/web/README.txt b/modules/web/README.txt
index 68f62b3..bbfe932 100644
--- a/modules/web/README.txt
+++ b/modules/web/README.txt
@@ -1,9 +1,9 @@
-Apache Ignite Web Module
+GridGain Web Module
------------------------
-Apache Ignite Web module provides Apache Ignite node startups based on servlet and servlet context listener
-which allow to start Apache Ignite inside any web container. Additionally this module provides
-capabilities to cache web sessions in Apache Ignite cache.
+GridGain Web module provides GridGain node startups based on servlet and servlet context listener
+which allow to start GridGain inside any web container. Additionally this module provides
+capabilities to cache web sessions in GridGain cache.
To enable Web module when starting a standalone node, move 'optional/ignite-web' folder to
'libs' folder before running 'ignite.{sh|bat}' script. The content of the module folder will
@@ -13,7 +13,7 @@ Importing Web Module In Maven Project
-------------------------------------
If you are using Maven to manage dependencies of your project, you can add Web module
-dependency like this (replace '${ignite.version}' with actual Ignite version you are
+dependency like this (replace '${ignite.version}' with actual GridGain version you are
interested in):
<project xmlns="http://maven.apache.org/POM/4.0.0"
@@ -24,7 +24,7 @@ interested in):
<dependencies>
...
<dependency>
- <groupId>org.apache.ignite</groupId>
+ <groupId>org.gridgain</groupId>
<artifactId>ignite-web</artifactId>
<version>${ignite.version}</version>
</dependency>
diff --git a/modules/yardstick/README.txt b/modules/yardstick/README.txt
index 71ed387..e6589b7 100644
--- a/modules/yardstick/README.txt
+++ b/modules/yardstick/README.txt
@@ -1,7 +1,7 @@
-Yardstick Ignite Benchmarks
+Yardstick GridGain Benchmarks
===========================
-Apache Ignite benchmarks are written on top of Yardstick Framework (https://github.com/gridgain/yardstick)
-and allow you to measure performance of various Apache Ignite components and modules.
+GridGain benchmarks are written on top of Yardstick Framework (https://github.com/gridgain/yardstick)
+and allow you to measure performance of various GridGain components and modules.
The documentation below describes how to execute and configure already assembled benchmarks. If you need to add new
benchmarks or build existing one then refer to instruction from `DEVNOTES.txt` in source directory.
@@ -10,7 +10,7 @@ Visit Yardstick Repository (https://github.com/gridgain/yardstick) for detailed
graphs generation and how the frameworks works.
-Running Ignite Benchmarks Locally
+Running GridGain Benchmarks Locally
=================================
The simplest way to start with benchmarking is to use one of the executable scripts available under `benchmarks\bin`
@@ -31,10 +31,10 @@ To get more information about available benchmarks and configuration parameters
to “Provided Benchmarks” and “Properties And Command Line Arguments” sections below.
-Running Ignite Benchmarks Remotely
+Running GridGain Benchmarks Remotely
==================================
-To benchmark Apache Ignite across several remote hosts the following steps need
+To benchmark GridGain across several remote hosts the following steps need
to be done:
1. Go to `config/ignite-remote-config.xml` and replace
@@ -53,7 +53,7 @@ Replace `localhost` occurrences in the same places in
`config/benchmark-remote.properties` files if you plan to execute a full set of
benchmarks available.
-3. Upload Ignite Yardstick Benchmarks to one of your DRIVERS host in its own working directory.
+3. Upload GridGain Yardstick Benchmarks to one of your DRIVERS host in its own working directory.
4. Log in on the remote host that will be the DRIVER and execute the following command:
@@ -106,8 +106,8 @@ The following benchmarks are provided:
Properties And Command Line Arguments
=====================================
-Note that this section only describes configuration parameters specific to Ignite benchmarks, and not for Yardstick
-framework. To run Ignite benchmarks and generate graphs, you will need to run them using Yardstick framework scripts in
+Note that this section only describes configuration parameters specific to GridGain benchmarks, and not for Yardstick
+framework. To run GridGain benchmarks and generate graphs, you will need to run them using Yardstick framework scripts in
`bin` folder.
Refer to Yardstick Documentation (https://github.com/gridgain/yardstick) for common Yardstick properties
@@ -116,7 +116,7 @@ and command line arguments for running Yardstick scripts.
The following Ignite benchmark properties can be defined in the benchmark configuration:
* `-b <num>` or `--backups <num>` - Number of backups for every key
-* `-cfg <path>` or `--Config <path>` - Path to Ignite configuration file
+* `-cfg <path>` or `--Config <path>` - Path to GridGain configuration file
* `-cs` or `--cacheStore` - Enable or disable cache store readThrough, writeThrough
* `-cl` or `--client` - Client flag. Use this flag if you running more than one `DRIVER`, otherwise additional drivers
would behave like a `servers`.
@@ -128,7 +128,7 @@ would behave like a `servers`.
* `-rd or --restartdelay` - Restart delay in seconds
* `-rs or --restartsleep` - Restart sleep in seconds
* `-rth <host>` or `--restHost <host>` - REST TCP host
-* `-rtp <num>` or `--restPort <num>` - REST TCP port, indicates that a Ignite node is ready to process Ignite Clients
+* `-rtp <num>` or `--restPort <num>` - REST TCP port, indicates that a GridGain node is ready to process GridGain Clients
* `-ss` or `--syncSend` - Flag indicating whether synchronous send is used in `TcpCommunicationSpi`
* `-txc <value>` or `--txConcurrency <value>` - Cache transaction concurrency control, either `OPTIMISTIC` or
`PESSIMISTIC` (defined in `CacheTxConcurrency`)
diff --git a/modules/yarn/README.txt b/modules/yarn/README.txt
index 5cdd4a2..9f8f540 100644
--- a/modules/yarn/README.txt
+++ b/modules/yarn/README.txt
@@ -1,13 +1,13 @@
-Apache Ignite Yarn Module
+GridGain Yarn Module
------------------------
-Apache Ignite Yarn module provides integration Apache Ignite with Apache Hadoop Yarn.
+GridGain Yarn module provides integration GridGain with Apache Hadoop Yarn.
-Importing Apache Ignite Yarn Module In Maven Project
+Importing GridGain Yarn Module In Maven Project
-------------------------------------
If you are using Maven to manage dependencies of your project, you can add Cloud module
-dependency like this (replace '${ignite.version}' with actual Ignite version you are
+dependency like this (replace '${ignite.version}' with actual GridGain version you are
interested in):
<project xmlns="http://maven.apache.org/POM/4.0.0"
@@ -18,7 +18,7 @@ interested in):
<dependencies>
...
<dependency>
- <groupId>org.apache.ignite</groupId>
+ <groupId>org.gridgain</groupId>
<artifactId>ignite-yarn</artifactId>
<version>${ignite.version}</version>
</dependency>
diff --git a/modules/zeromq/README.txt b/modules/zeromq/README.txt
index aeb86f8..4393375 100644
--- a/modules/zeromq/README.txt
+++ b/modules/zeromq/README.txt
@@ -1,14 +1,14 @@
-Apache Ignite ZeroMQ Streamer Module
+GridGain ZeroMQ Streamer Module
------------------------
-Apache Ignite ZeroMQ Streamer module provides streaming from ZeroMQ to Ignite cache.
+GridGain ZeroMQ Streamer module provides streaming from ZeroMQ to GridGain cache.
-Starting data transfer to Ignite cache can be done with the following steps.
+Starting data transfer to GridGain cache can be done with the following steps.
-1. Import Ignite ZeroMQ Streamer Module In Maven Project
+1. Import GridGain ZeroMQ Streamer Module In Maven Project
If you are using Maven to manage dependencies of your project, you can add ZeroMQ module
-dependency like this (replace '${ignite.version}' with actual Ignite version you are
+dependency like this (replace '${ignite.version}' with actual GridGain version you are
interested in):
<project xmlns="http://maven.apache.org/POM/4.0.0"
@@ -19,7 +19,7 @@ interested in):
<dependencies>
...
<dependency>
- <groupId>org.apache.ignite</groupId>
+ <groupId>org.gridgain</groupId>
<artifactId>ignite-zeromq</artifactId>
<version>${ignite.version}</version>
</dependency>
@@ -28,7 +28,7 @@ interested in):
...
</project>
-2. Create an Ignite configuration file (see example-ignite.xml) and make sure it is accessible from the streamer.
+2. Create an GridGain configuration file (see example-ignite.xml) and make sure it is accessible from the streamer.
3. Create your StreamSingleTupleExtractor or StreamMultipleTupleExtractor, an example can be found in the tests folder
ZeroMqStringSingleTupleExtractor.java. Now it is necessary to add in a streamer
diff --git a/modules/zookeeper/README.txt b/modules/zookeeper/README.txt
index 6d400ad..121ffa2 100644
--- a/modules/zookeeper/README.txt
+++ b/modules/zookeeper/README.txt
@@ -1,14 +1,14 @@
-Apache Ignite ZooKeeper Module
+GridGain ZooKeeper Module
------------------------------
-Apache Ignite ZooKeeper module provides a TCP Discovery IP Finder that uses a ZooKeeper
-directory to locate other Ignite nodes to connect to.
+GridGain ZooKeeper module provides a TCP Discovery IP Finder that uses a ZooKeeper
+directory to locate other GridGain nodes to connect to.
-Importing Apache Ignite ZooKeeper Module In Maven Project
+Importing GridGain ZooKeeper Module In Maven Project
---------------------------------------------------------
If you are using Maven to manage dependencies of your project, you can add the ZooKeeper
-module dependency like this (replace '${ignite.version}' with actual Ignite version you
+module dependency like this (replace '${ignite.version}' with actual GridGain version you
are interested in):
<project xmlns="http://maven.apache.org/POM/4.0.0"
@@ -19,7 +19,7 @@ are interested in):
<dependencies>
...
<dependency>
- <groupId>org.apache.ignite</groupId>
+ <groupId>org.gridgain</groupId>
<artifactId>ignite-zookeeper</artifactId>
<version>${ignite.version}</version>
</dependency>