svn commit: r1843616 - /ignite/site/trunk/whatisignite.html

[dsetrakyan]

Author: dsetrakyan
Date: Fri Oct 12 01:37:26 2018
New Revision: 1843616

URL: http://svn.apache.org/viewvc?rev=1843616=rev
Log:
Minor fix.

Modified:
ignite/site/trunk/whatisignite.html

Modified: ignite/site/trunk/whatisignite.html
URL: 
http://svn.apache.org/viewvc/ignite/site/trunk/whatisignite.html?rev=1843616=1843615=1843616=diff
==
--- ignite/site/trunk/whatisignite.html (original)
+++ ignite/site/trunk/whatisignite.html Fri Oct 12 01:37:26 2018
@@ -74,50 +74,48 @@ under the License.
 
 
 
+
 
-Is Ignite an 
in-memory database?
+
+Is Ignite a 
distributed cache?
 
-Yes. Even though Ignite 
memory-centric storage works well in-memory and on-disk, the disk
-persistence can be disabled and Ignite can act as 
a distributed in-memory database, with
-support for SQL and distributed joins.
+Yes. When native persistence is 
disabled, Ignite becomes a distributed in-memory cache
+with support for JCache specification (JSR 107), 
distributed ACID transactions,
+SQL queries, on-disk persistence, and more.
 
-Read more: In-Memory Database
+Read more: Database Caching
 
 
 
-Is Ignite an 
in-memory data grid?
+Is Ignite a 
distributed database?
 
-Yes. Ignite is a full-featured 
distributed key-value data grid, which can be used either in
-memory-only mode or with Ignite native 
persistence. It can also automatically integrate with any 3rd party databases,
-including any RDBMS or NoSQL stores.
+Yes. Ignite is a strongly 
consistent distributed database. Data in Ignite is
+stored in-memory and/or on-disk and is either 
partitioned or replicated across a cluster of
+multiple nodes. This provides for scalability, 
performance, and resiliency.
 
-Read more: In-Memory Data Grid
+Read more: Distributed 
Database
 
 
 
 
-
 
-
-Is Ignite a 
distributed cache?
+Is Ignite an 
in-memory database?
 
-Yes. When native persistence is 
disabled, Ignite becomes a distributed cache.
-Ignite implements JCache specification (JSR 107) 
and provides
-a lot more functionality than required by the 
specification, including partitioned and replicated
-distribution modes, distributed ACID transactions, 
SQL queries, native persistence, and more.
+Yes. Even though Ignite 
memory-centric storage works well in-memory and on-disk, the disk
+persistence can be disabled and Ignite can act as 
a distributed in-memory database, with
+support for SQL and distributed joins.
 
-Read more: Database Caching
+Read more: In-Memory Database
 
 
 
-Is Ignite a 
distributed database?
+Is Ignite an 
in-memory data grid?
 
-Yes. Data in Ignite is either 
partitioned or replicated across a cluster of
-multiple nodes. This provides scalability and adds 
resiliency to the system. Ignite automatically
-controls how data is partitioned, however, users 
can plugin their own distribution (affinity) functions
-and collocate various pieces of data together for 
efficiency.
+Yes. Ignite is a full-featured 
distributed key-value data grid, which can be used either in
+memory-only mode or with Ignite native 
persistence. It can also automatically integrate with any 3rd party databases,
+including any RDBMS or NoSQL stores.
 
-Read more: Distributed 
Database
+Read more: In-Memory Data Grid
 
 
 

svn commit: r1843615 - /ignite/site/trunk/arch/memorycentric.html

[dsetrakyan]

Author: dsetrakyan
Date: Fri Oct 12 01:22:04 2018
New Revision: 1843615

URL: http://svn.apache.org/viewvc?rev=1843615=rev
Log:
Minor fix.

Modified:
ignite/site/trunk/arch/memorycentric.html

Modified: ignite/site/trunk/arch/memorycentric.html
URL: 
http://svn.apache.org/viewvc/ignite/site/trunk/arch/memorycentric.html?rev=1843615=1843614=1843615=diff
==
--- ignite/site/trunk/arch/memorycentric.html (original)
+++ ignite/site/trunk/arch/memorycentric.html Fri Oct 12 01:22:04 2018
@@ -84,16 +84,11 @@ under the License.
 distributed cache and a distributed database together.
 
 
-Ignite distributed cache can be used either stand-alone, or 
can also integrate with any existing database, including
-Oracle, MySQL, Cassandra, Mongo, and others. However, in this 
case, the memory-layer may not be able to
-fit the whole data set, causing Ignite indexing and SQL 
queries to only function
-over the in-memory subset. This approach is recommended 
whenever there is already
-an existing database present and replacing it is not an option.
-
-
-However, in order to ensure that the whole data set is durable 
and available for querying and collocated processing,
-it is preferable to enable native persistence and use Ignite 
as a distributed system-of-record.
-In this case Ignite will always store a superset of data on 
disk,  with a subset of data cached in memory.
+In partitioned (not replicated) mode, the data is partitioned 
across multiple servers, with each server responsible
+for a subset of the data. Collectively, the full data set is 
stored across all servers. Each server
+has its subset persisted on disk. Depending on how much memory 
is available,
+each server also has either the whole subset or a portion of 
it cached in memory. Such combination
+of memory and disk creates a distributed memory-centric 
storage.
 
 
 The following memory and disk usage modes are supported:
@@ -233,16 +228,6 @@ under the License.
 all cluster members.
 
 
-
-Ignite Native Persistence
-
-
-
-Ignite native persistence is a distributed, ACID and 
SQL-compliant disk store
-that transparently integrates with Ignite's in-memory cache. 
Ignite persistence is optional
-and can be turned on and off. When turned off Ignite becomes a 
pure in-memory store.
-
-
 
 Write-Ahead Log
 

svn commit: r1843608 - /ignite/site/trunk/features.html

[dsetrakyan]

Author: dsetrakyan
Date: Thu Oct 11 22:13:49 2018
New Revision: 1843608

URL: http://svn.apache.org/viewvc?rev=1843608=rev
Log:
Minor fix.

Modified:
ignite/site/trunk/features.html

Modified: ignite/site/trunk/features.html
URL: 
http://svn.apache.org/viewvc/ignite/site/trunk/features.html?rev=1843608=1843607=1843608=diff
==
--- ignite/site/trunk/features.html (original)
+++ ignite/site/trunk/features.html Thu Oct 11 22:13:49 2018
@@ -616,7 +616,7 @@ under the License.
 Ignite can automatically integrate with 
external databases - RDBMS, NoSQL, and HDFS.
 
 
-https://apacheignite.readme.io/docs/persistent-store; target="docs">Docs 
for this feature 
+https://apacheignite.readme.io/docs/3rd-party-store; target="docs">Docs 
for this feature 
 
 
 

svn commit: r1843607 - in /ignite/site/trunk/arch: memorycentric.html persistence.html

[dsetrakyan]

Author: dsetrakyan
Date: Thu Oct 11 22:04:47 2018
New Revision: 1843607

URL: http://svn.apache.org/viewvc?rev=1843607=rev
Log:
Updated memory-centric description.

Modified:
ignite/site/trunk/arch/memorycentric.html
ignite/site/trunk/arch/persistence.html

Modified: ignite/site/trunk/arch/memorycentric.html
URL: 
http://svn.apache.org/viewvc/ignite/site/trunk/arch/memorycentric.html?rev=1843607=1843606=1843607=diff
==
--- ignite/site/trunk/arch/memorycentric.html (original)
+++ ignite/site/trunk/arch/memorycentric.html Thu Oct 11 22:04:47 2018
@@ -61,24 +61,43 @@ under the License.
 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
-In-Memory Database (IMDB) and In-Memory Data Grid 
(IMDG) in one.
+When native persistence is turned on, Ignite functions 
as a memory-centric system-of-record,
+where most of the processing happens in memory on 
cached data, but the superset of data and indexes gets persisted to disk.
 
 
 
-
+
 
 
 
-On the other hand, when persistence is turned on, Ignite 
functions as a memory-centric system-of-record,
-where most of the processing happens in memory on cached data, 
but the superset of data and indexes get persisted to disk.
+When persistence is turned off, Ignite functions as a 
memory-only store, in which case it can be treated as a Distributed Cache,
+In-Memory Database (IMDB) or In-Memory Data Grid (IMDG).
 
-
-Memory and Disk Usage Modes
-
+
+
+Database and Caching in One
+
 
+
+One of the main advantages of Ignite is that it comes with a 
distributed in-memory cache and a
+distributed on-disk storage in one platform. In other words, 
Ignite users get both, a
+distributed cache and a distributed database together.
+
+
+Ignite distributed cache can be used either stand-alone, or 
can also integrate with any existing database, including
+Oracle, MySQL, Cassandra, Mongo, and others. However, in this 
case, the memory-layer may not be able to
+fit the whole data set, causing Ignite indexing and SQL 
queries to only function
+over the in-memory subset. This approach is recommended 
whenever there is already
+an existing database present and replacing it is not an option.
+
+
+However, in order to ensure that the whole data set is durable 
and available for querying and collocated processing,
+it is preferable to enable native persistence and use Ignite 
as a distributed system-of-record.
+In this case Ignite will always store a superset of data on 
disk,  with a subset of data cached in memory.
+
+
+The following memory and disk usage modes are supported:
+
 
 
 
@@ -91,12 +110,9 @@ under the License.
 In-Memory
 
 
-The whole data set is stored in memory. In this 
scenario, you can achieve the maximum
-performance possible because the data is never 
written to disk. To prevent possible data
-loss when a single cluster node fails, it is 
recommended to configure a number of backup
-copies (aka. replication factor) appropriately.
-Swap 
space can be used to prevent memory
-overflow.
+The whole data set is stored in memory. In order 
to survive
+node failures, it is recommended to configure a 
number of redundant backup
+copies (aka. replication factor) across the 
cluster.
 
 
 
@@ -109,9 +125,9 @@ under the License.
 In-Memory + 3rd party database
 
 
-Ignite can be used as a caching layer (aka. data 
grid) above

svn commit: r1843516 - /ignite/site/trunk/whatisignite.html

[dsetrakyan]

Author: dsetrakyan
Date: Wed Oct 10 21:52:37 2018
New Revision: 1843516

URL: http://svn.apache.org/viewvc?rev=1843516=rev
Log:
Minor.

Modified:
ignite/site/trunk/whatisignite.html

Modified: ignite/site/trunk/whatisignite.html
URL: 
http://svn.apache.org/viewvc/ignite/site/trunk/whatisignite.html?rev=1843516=1843515=1843516=diff
==
--- ignite/site/trunk/whatisignite.html (original)
+++ ignite/site/trunk/whatisignite.html Wed Oct 10 21:52:37 2018
@@ -63,7 +63,7 @@ under the License.
 
 
 
-
+
 
 
 

svn commit: r1843515 - /ignite/site/trunk/whatisignite.html

[dsetrakyan]

Author: dsetrakyan
Date: Wed Oct 10 21:51:12 2018
New Revision: 1843515

URL: http://svn.apache.org/viewvc?rev=1843515=rev
Log:
Minor.

Modified:
ignite/site/trunk/whatisignite.html

Modified: ignite/site/trunk/whatisignite.html
URL: 
http://svn.apache.org/viewvc/ignite/site/trunk/whatisignite.html?rev=1843515=1843514=1843515=diff
==
--- ignite/site/trunk/whatisignite.html (original)
+++ ignite/site/trunk/whatisignite.html Wed Oct 10 21:51:12 2018
@@ -63,7 +63,7 @@ under the License.
 
 
 
-
+
 
 
 

svn commit: r1843511 - /ignite/site/trunk/arch/memorycentric.html

[dsetrakyan]

Author: dsetrakyan
Date: Wed Oct 10 21:31:02 2018
New Revision: 1843511

URL: http://svn.apache.org/viewvc?rev=1843511=rev
Log:
Minor.

Modified:
ignite/site/trunk/arch/memorycentric.html

Modified: ignite/site/trunk/arch/memorycentric.html
URL: 
http://svn.apache.org/viewvc/ignite/site/trunk/arch/memorycentric.html?rev=1843511=1843510=1843511=diff
==
--- ignite/site/trunk/arch/memorycentric.html (original)
+++ ignite/site/trunk/arch/memorycentric.html Wed Oct 10 21:31:02 2018
@@ -72,7 +72,7 @@ under the License.
 
 
 
-On the other hand, when persistence is turned on, Ignite 
begins to function as a memory-centric system
+On the other hand, when persistence is turned on, Ignite 
functions as a memory-centric system-of-record,
 where most of the processing happens in memory on cached data, 
but the superset of data and indexes get persisted to disk.
 
 

svn commit: r1843508 - /ignite/site/trunk/features.html

[dsetrakyan]

Author: dsetrakyan
Date: Wed Oct 10 20:36:52 2018
New Revision: 1843508

URL: http://svn.apache.org/viewvc?rev=1843508=rev
Log:
Minor.

Modified:
ignite/site/trunk/features.html

Modified: ignite/site/trunk/features.html
URL: 
http://svn.apache.org/viewvc/ignite/site/trunk/features.html?rev=1843508=1843507=1843508=diff
==
--- ignite/site/trunk/features.html (original)
+++ ignite/site/trunk/features.html Wed Oct 10 20:36:52 2018
@@ -71,10 +71,10 @@ under the License.
onclick="ga('send', 'event', 
'apache_ignite_features', 'features_page_click', 'distributed_key_value');">
 Distributed Key-Value
 
-
-   
-
-
+
+Distributed Persistence
+
 
 ACID Transactions

svn commit: r1843506 - /ignite/site/trunk/arch/memorycentric.html

[dsetrakyan]

Author: dsetrakyan
Date: Wed Oct 10 20:27:34 2018
New Revision: 1843506

URL: http://svn.apache.org/viewvc?rev=1843506=rev
Log:
Minor.

Modified:
ignite/site/trunk/arch/memorycentric.html

Modified: ignite/site/trunk/arch/memorycentric.html
URL: 
http://svn.apache.org/viewvc/ignite/site/trunk/arch/memorycentric.html?rev=1843506=1843505=1843506=diff
==
--- ignite/site/trunk/arch/memorycentric.html (original)
+++ ignite/site/trunk/arch/memorycentric.html Wed Oct 10 20:27:34 2018
@@ -73,9 +73,7 @@ under the License.
 
 
 On the other hand, when persistence is turned on, Ignite 
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 scalable, and supports both SQL and key-value 
processing APIs.
+where most of the processing happens in memory on cached data, 
but the superset of data and indexes get persisted to disk.
 
 
 Memory and Disk Usage Modes

svn commit: r1843500 - /ignite/site/trunk/arch/memorycentric.html

[dsetrakyan]

Author: dsetrakyan
Date: Wed Oct 10 20:03:04 2018
New Revision: 1843500

URL: http://svn.apache.org/viewvc?rev=1843500=rev
Log:
Minor.

Modified:
ignite/site/trunk/arch/memorycentric.html

Modified: ignite/site/trunk/arch/memorycentric.html
URL: 
http://svn.apache.org/viewvc/ignite/site/trunk/arch/memorycentric.html?rev=1843500=1843499=1843500=diff
==
--- ignite/site/trunk/arch/memorycentric.html (original)
+++ ignite/site/trunk/arch/memorycentric.html Wed Oct 10 20:03:04 2018
@@ -78,7 +78,7 @@ under the License.
 horizontally scalable, and supports both SQL and key-value 
processing APIs.
 
 
-Memory Usage Modes
+Memory and Disk Usage Modes
 
 
 

svn commit: r1843498 - in /ignite/site/trunk: arch/clustering.html arch/persistence.html download.html features.html includes/header.html index.html

[dsetrakyan]

Author: dsetrakyan
Date: Wed Oct 10 19:59:08 2018
New Revision: 1843498

URL: http://svn.apache.org/viewvc?rev=1843498=rev
Log:
Navigation change

Modified:
ignite/site/trunk/arch/clustering.html
ignite/site/trunk/arch/persistence.html
ignite/site/trunk/download.html
ignite/site/trunk/features.html
ignite/site/trunk/includes/header.html
ignite/site/trunk/index.html

Modified: ignite/site/trunk/arch/clustering.html
URL: 
http://svn.apache.org/viewvc/ignite/site/trunk/arch/clustering.html?rev=1843498=1843497=1843498=diff
==
--- ignite/site/trunk/arch/clustering.html (original)
+++ ignite/site/trunk/arch/clustering.html Wed Oct 10 19:59:08 2018
@@ -39,7 +39,7 @@ under the License.
 
 
 
-Clustering and Deployment - Apache Ignite
+Deploy Anywhere - Apache Ignite
 
 https://netdna.bootstrapcdn.com/font-awesome/4.2.0/css/font-awesome.css; 
rel="stylesheet">
 
@@ -52,7 +52,7 @@ under the License.
 
 
 
-Clustering and Deployment
+Deploy Anywhere
 
 
 

Modified: ignite/site/trunk/arch/persistence.html
URL: 
http://svn.apache.org/viewvc/ignite/site/trunk/arch/persistence.html?rev=1843498=1843497=1843498=diff
==
--- ignite/site/trunk/arch/persistence.html (original)
+++ ignite/site/trunk/arch/persistence.html Wed Oct 10 19:59:08 2018
@@ -39,7 +39,7 @@ under the License.
 
 
 
-Peristence - Apache Ignite
+Distributed Peristence - Apache Ignite
 
 
 https://netdna.bootstrapcdn.com/font-awesome/4.2.0/css/font-awesome.css; 
rel="stylesheet">
@@ -53,7 +53,7 @@ under the License.
 
 
 
-Ignite Persistence
+Distributed Persistence
 
 
 

Modified: ignite/site/trunk/download.html
URL: 
http://svn.apache.org/viewvc/ignite/site/trunk/download.html?rev=1843498=1843497=1843498=diff
==
--- ignite/site/trunk/download.html (original)
+++ ignite/site/trunk/download.html Wed Oct 10 19:59:08 2018
@@ -152,6 +152,10 @@ under the License.
 
 
 Features
+
+Memory-Centric Storage
+
 
 Distributed SQL
@@ -160,6 +164,10 @@ under the License.
onclick="ga('send', 'event', 
'apache_ignite_features', 'menu_click', 'distributed_key_value');">
 Distributed Key-Value
 
+
+
+
+
 
 ACID Transactions
@@ -176,27 +184,12 @@ under the License.
onclick="ga('send', 'event', 
'apache_ignite_features', 'menu_click', 'multi_language');">
 Multi-Language
 
-More 
Features
-
-
-
-Architecture
 
-Clustering and Deployment
-
-
-Memory-Centric Storage
-
-
-   
-
-
-
-Distributed Persistence
+Deploy Anywhere
 
+More 
Features
+
 
 
 
@@ -209,22 +202,6 @@ under the License.
onclick="ga('send', 'event', 
'apache_ignite_features', 'menu_click', 'data_visualization');">
   

svn commit: r1825264 - in /ignite/site/branches/ignite-7061: download.html features/datagrid.html includes/header.html use-cases/database/distributed-database.html use-cases/database/in-memory-databas

[dsetrakyan]

Author: dsetrakyan
Date: Sat Feb 24 17:00:35 2018
New Revision: 1825264

URL: http://svn.apache.org/viewvc?rev=1825264=rev
Log:
Text updates.

Modified:
ignite/site/branches/ignite-7061/download.html
ignite/site/branches/ignite-7061/features/datagrid.html
ignite/site/branches/ignite-7061/includes/header.html

ignite/site/branches/ignite-7061/use-cases/database/distributed-database.html
ignite/site/branches/ignite-7061/use-cases/database/in-memory-database.html

Modified: ignite/site/branches/ignite-7061/download.html
URL: 
http://svn.apache.org/viewvc/ignite/site/branches/ignite-7061/download.html?rev=1825264=1825263=1825264=diff
==
--- ignite/site/branches/ignite-7061/download.html (original)
+++ ignite/site/branches/ignite-7061/download.html Sat Feb 24 17:00:35 2018
@@ -232,7 +232,7 @@ under the License.
 
 
 
-Database
+Data Store
 
 Distributed Database
@@ -252,20 +252,8 @@ under the License.
 
 
 
-
-Comparison
-
-Ignite for NoSQL Users
-
-
-Ignite for RDBMS Users
-
-
-
-
-In-Memory Caching
+
+In-Memory Cache
 
 Database Caching
@@ -284,7 +272,19 @@ under the License.
 
 
 
-
+
+Comparison
+
+Ignite for NoSQL Users
+
+
+Ignite for RDBMS Users
+
+
+
+
 Ignite with Spark & Hadoop
 

Modified: ignite/site/branches/ignite-7061/features/datagrid.html
URL: 
http://svn.apache.org/viewvc/ignite/site/branches/ignite-7061/features/datagrid.html?rev=1825264=1825263=1825264=diff
==
--- ignite/site/branches/ignite-7061/features/datagrid.html (original)
+++ ignite/site/branches/ignite-7061/features/datagrid.html Sat Feb 24 17:00:35 
2018
@@ -58,11 +58,11 @@ under the License.
 
 
 
-Ignite can be accessed with simple key-value APIs and, 
thus, act as a in-memory data grid.
-In this scenario, you can think of Ignite as of a 
distributed partitioned hash map with every
+Ignite provides extensive and rich key-value APIs and 
can act as an in-memory data grid.
+You can think of Ignite as of a distributed 
partitioned hash map with every
 cluster node owning a portion of the overall data set. 
Unlike other in-memory data grids (IMDG),
 Ignite enables storing data both, in memory and on 
disk, and
-therefore is able to store more data than can fit in 
physical memory.
+therefore is able to store more data than can fit in 
the physical memory.
 
 
 Ignite data grid is one of the fastest implementations 
of ACID transactions or
@@ -74,11 +74,19 @@ under the License.
 
 
 
+3rd Party Databases
 
-The in-memory data grid can also improve performance and 
scalability by integrating with existing 3rd party
-databases, like RDBMS, NoSQL, or Hadoop-based storages. This 
approach does not require
-rip-and-replace of the existing data, but has its limitations. 
For example, SQL or scan queries will only include the
-results stored in memory, and not in the external database, 
since Ignite does not have any knowl

svn commit: r1824488 - in /ignite/site/branches/ignite-7061/features: collocatedprocessing.html machinelearning.html sql.html transactions.html

[dsetrakyan]

Author: dsetrakyan
Date: Fri Feb 16 14:03:58 2018
New Revision: 1824488

URL: http://svn.apache.org/viewvc?rev=1824488=rev
Log:
Text updates.

Modified:
ignite/site/branches/ignite-7061/features/collocatedprocessing.html
ignite/site/branches/ignite-7061/features/machinelearning.html
ignite/site/branches/ignite-7061/features/sql.html
ignite/site/branches/ignite-7061/features/transactions.html

Modified: ignite/site/branches/ignite-7061/features/collocatedprocessing.html
URL: 
http://svn.apache.org/viewvc/ignite/site/branches/ignite-7061/features/collocatedprocessing.html?rev=1824488=1824487=1824488=diff
==
--- ignite/site/branches/ignite-7061/features/collocatedprocessing.html 
(original)
+++ ignite/site/branches/ignite-7061/features/collocatedprocessing.html Fri Feb 
16 14:03:58 2018
@@ -76,13 +76,13 @@ under the License.
 Data Collocation
 
 To start benefiting from the collocated processing, we need to 
ensure that the data is properly collocated
-at the first place. If business logic requires to access more 
than one entry it can be reasonable to
-collocate dependent entries by storing them on a single 
cluster node. This technique is also known as
-affinity collocation of the data.
+in the first place. If the business logic requires to access 
more than one entry, it is usually best to
+collocate dependent entries on a single cluster node. This 
technique is also known as
+affinity collocation of the data.
 
 
 In the example below, we have Country and 
City tables and want to collocate
-City entries with Country entries 
for where a city is located. To achieve this,
+City entries with their corresponding 
Country entries. To achieve this,
 we use the WITH clause and specify 
affinityKey=CountryCode as shown below:
 
 
@@ -119,10 +119,10 @@ under the License.
 SQL and Distributed JOINs
 
 Apache Ignite SQL engine will always perform much more 
efficiently if a query is run against the
-collocated data. Especially it is crucial for distributed 
JOINs supported by Ignite.
+collocated data. It is especially crucial for execution of 
distributed JOINs within the cluster.
 
 
-Taking the example of the two tables created above, let's get 
the most inhabited cities across China,
+Taking the example of the two tables created above, let's get 
the most populated cities across China,
 Russia and the USA joining the data stored in the 
Country and City tables, as follows:
 
 
@@ -139,17 +139,15 @@ under the License.
 
 
 
-Since all the cities were collocated with their countries 
beforehand, Ignite will execute the query and
-join the data on concrete nodes that store China, Russia and 
the USA entries. This approach, again, avoids
-expensive data movement across the network, needed to complete 
the query, because all the data will be available
-on the nodes locally.
+Since all the cities were collocated with their countries, the 
JOIN will execute only on the nodes
+that store China, Russia and the USA entries. This approach 
avoids expensive data movement
+across the network, and therefore scales better and provides 
the fastest performance.
 
 Distributed Collocated Computations
 
-Apache Ignite compute grid and machine learning component 
allows to perform computations and execute
-machine learning algorithms in parallel fashion to gain high 
performance, low latency, and linear scalability.
-Furthermore, both components highly rely on data collocation 
(and collocated processing in general) giving
-the ways to optimize specific tasks or calculations.
+Apache Ignite compute grid and machine learning components 
allow to perform computations and execute
+machine learning algorithms in parallel to achieve high 
performance, low latency, and linear scalability.
+Furthermore, both components work best with collocated data 
and collocated processing in general.
 
 
 For instance, let's assume that a blizzard is approaching New 
York. As a telecommunication company,
@@ -158,9 +156,9 @@ under the License.
 from the database to the client text messaging application, 
which does not scale.
 
 
-A much more efficient approach

svn commit: r1822834 - /ignite/site/trunk/features/datagrid.html

[dsetrakyan]

Author: dsetrakyan
Date: Wed Jan 31 20:53:33 2018
New Revision: 1822834

URL: http://svn.apache.org/viewvc?rev=1822834=rev
Log:
minor.

Modified:
ignite/site/trunk/features/datagrid.html

Modified: ignite/site/trunk/features/datagrid.html
URL: 
http://svn.apache.org/viewvc/ignite/site/trunk/features/datagrid.html?rev=1822834=1822833=1822834=diff
==
--- ignite/site/trunk/features/datagrid.html (original)
+++ ignite/site/trunk/features/datagrid.html Wed Jan 31 20:53:33 2018
@@ -60,7 +60,7 @@ under the License.
 
 Ignite data grid is a distributed, transactional 
key-value store. Unlike other
 in-memory data grids (IMDG), Ignite enables storing 
data both, in memory and on disk, and
-therefore is able to store more data than can fit in 
memory.
+therefore is able to store more data than can fit in 
physical memory.
 On top of the standard key-value data operations, 
including ACID transactions and all the
 JCache (JSR 107) functionality, Ignite also supports 
SQL queries
 over its data with the support for 
distributed joins.

svn commit: r1822833 - /ignite/site/trunk/features/datagrid.html

[dsetrakyan]

Author: dsetrakyan
Date: Wed Jan 31 20:52:29 2018
New Revision: 1822833

URL: http://svn.apache.org/viewvc?rev=1822833=rev
Log:
minor.

Modified:
ignite/site/trunk/features/datagrid.html

Modified: ignite/site/trunk/features/datagrid.html
URL: 
http://svn.apache.org/viewvc/ignite/site/trunk/features/datagrid.html?rev=1822833=1822832=1822833=diff
==
--- ignite/site/trunk/features/datagrid.html (original)
+++ ignite/site/trunk/features/datagrid.html Wed Jan 31 20:52:29 2018
@@ -59,7 +59,8 @@ under the License.
 
 
 Ignite data grid is a distributed, transactional 
key-value store. Unlike other
-in-memory data grids (IMDG), Ignite enables storing 
data both, in memory and on disk.
+in-memory data grids (IMDG), Ignite enables storing 
data both, in memory and on disk, and
+therefore is able to store more data than can fit in 
memory.
 On top of the standard key-value data operations, 
including ACID transactions and all the
 JCache (JSR 107) functionality, Ignite also supports 
SQL queries
 over its data with the support for 
distributed joins.

svn commit: r1822822 - /ignite/site/trunk/whatisignite.html

[dsetrakyan]

Author: dsetrakyan
Date: Wed Jan 31 19:43:40 2018
New Revision: 1822822

URL: http://svn.apache.org/viewvc?rev=1822822=rev
Log:
minor.

Modified:
ignite/site/trunk/whatisignite.html

Modified: ignite/site/trunk/whatisignite.html
URL: 
http://svn.apache.org/viewvc/ignite/site/trunk/whatisignite.html?rev=1822822=1822821=1822822=diff
==
--- ignite/site/trunk/whatisignite.html (original)
+++ ignite/site/trunk/whatisignite.html Wed Jan 31 19:43:40 2018
@@ -91,7 +91,7 @@ under the License.
 memory-only mode or with Ignite native 
persistence. It can also automatically integrate with any 3rd party databases,
 including any RDBMS or NoSQL stores.
 
-Read more: Data Grid
+Read more: In-Memory Data Grid
 
 
 

svn commit: r1822685 - /ignite/site/trunk/use-cases/comparison/ignite-for-nosql.html

[dsetrakyan]

Author: dsetrakyan
Date: Tue Jan 30 19:39:52 2018
New Revision: 1822685

URL: http://svn.apache.org/viewvc?rev=1822685=rev
Log:
minor.

Modified:
ignite/site/trunk/use-cases/comparison/ignite-for-nosql.html

Modified: ignite/site/trunk/use-cases/comparison/ignite-for-nosql.html
URL: 
http://svn.apache.org/viewvc/ignite/site/trunk/use-cases/comparison/ignite-for-nosql.html?rev=1822685=1822684=1822685=diff
==
--- ignite/site/trunk/use-cases/comparison/ignite-for-nosql.html (original)
+++ ignite/site/trunk/use-cases/comparison/ignite-for-nosql.html Tue Jan 30 
19:39:52 2018
@@ -180,7 +180,7 @@ under the License.
 Unlike eventually consistent NoSQL databases, Ignite can 
operate in a strongly consistent mode,
 guaranteeing the data consistency across all cluster nodes. In 
addition, ignte supports
 https://apacheignite.readme.io/docs/transactions;>ACID transactions 
that can span
-multiple keys and multiple nodes acrsoss cluster partitions.
+multiple keys acrsoss multiple cluster ndoes and partitions.
 
 
 

svn commit: r1822684 - /ignite/site/trunk/use-cases/comparison/ignite-for-nosql.html

[dsetrakyan]

Author: dsetrakyan
Date: Tue Jan 30 19:37:30 2018
New Revision: 1822684

URL: http://svn.apache.org/viewvc?rev=1822684=rev
Log:
minor.

Modified:
ignite/site/trunk/use-cases/comparison/ignite-for-nosql.html

Modified: ignite/site/trunk/use-cases/comparison/ignite-for-nosql.html
URL: 
http://svn.apache.org/viewvc/ignite/site/trunk/use-cases/comparison/ignite-for-nosql.html?rev=1822684=1822683=1822684=diff
==
--- ignite/site/trunk/use-cases/comparison/ignite-for-nosql.html (original)
+++ ignite/site/trunk/use-cases/comparison/ignite-for-nosql.html Tue Jan 30 
19:37:30 2018
@@ -178,7 +178,9 @@ under the License.
 
 
 Unlike eventually consistent NoSQL databases, Ignite can 
operate in a strongly consistent mode,
-guaranteeing the data consistency across all cluster nodes. 
Ignite is a fully ACID-compliant platform.
+guaranteeing the data consistency across all cluster nodes. In 
addition, ignte supports
+https://apacheignite.readme.io/docs/transactions;>ACID transactions 
that can span
+multiple keys and multiple nodes acrsoss cluster partitions.
 
 
 

svn commit: r1822683 - in /ignite/site/trunk: index.html whatisignite.html

[dsetrakyan]

Author: dsetrakyan
Date: Tue Jan 30 19:32:19 2018
New Revision: 1822683

URL: http://svn.apache.org/viewvc?rev=1822683=rev
Log:
minor.

Modified:
ignite/site/trunk/index.html
ignite/site/trunk/whatisignite.html

Modified: ignite/site/trunk/index.html
URL: 
http://svn.apache.org/viewvc/ignite/site/trunk/index.html?rev=1822683=1822682=1822683=diff
==
Binary files - no diff available.

Modified: ignite/site/trunk/whatisignite.html
URL: 
http://svn.apache.org/viewvc/ignite/site/trunk/whatisignite.html?rev=1822683=1822682=1822683=diff
==
--- ignite/site/trunk/whatisignite.html (original)
+++ ignite/site/trunk/whatisignite.html Tue Jan 30 19:32:19 2018
@@ -56,10 +56,10 @@ under the License.
 
 Apache Ignite is ...
 
-memory-centric 
distributed
+memory-centric distributed
 database, caching, 
and processing platform 
 for transactional, analytical, and streaming 
workloads,
-delivering in-memory speeds at petabyte 
scale
+delivering in-memory speeds at petabyte 
scale
 
 
 
@@ -152,7 +152,8 @@ under the License.
 Is Ignite a NoSQL 
database?
 
 Not exactly. Just like other 
NoSQL databases, Ignite is highly available and
-horizontally scalable. However, unlike other NoSQL 
databases, Ignite supports SQL and ACID transactions.
+horizontally scalable. However, unlike other NoSQL 
databases, Ignite supports SQL and ACID transactions
+across multiple cluster nodes.
 
 Read more: Ignite for NoSQL
 

svn commit: r1821725 - in /ignite/site/trunk: css/all.css scss/ignite.scss

[dsetrakyan]

Author: dsetrakyan
Date: Sat Jan 20 01:48:04 2018
New Revision: 1821725

URL: http://svn.apache.org/viewvc?rev=1821725=rev
Log:
minor fix

Modified:
ignite/site/trunk/css/all.css
ignite/site/trunk/scss/ignite.scss

Modified: ignite/site/trunk/css/all.css
URL: 
http://svn.apache.org/viewvc/ignite/site/trunk/css/all.css?rev=1821725=1821724=1821725=diff
==
--- ignite/site/trunk/css/all.css (original)
+++ ignite/site/trunk/css/all.css Sat Jan 20 01:48:04 2018
@@ -8760,7 +8760,7 @@ section.page-subsection {
 .social-media h3 {
   margin-bottom: 12px;
   border-bottom: 1px solid black;
-  font-weight: 300;
+  font-weight: 300 !important;
   font-size: 24px !important;
 }
 .social-media ul {

Modified: ignite/site/trunk/scss/ignite.scss
URL: 
http://svn.apache.org/viewvc/ignite/site/trunk/scss/ignite.scss?rev=1821725=1821724=1821725=diff
==
--- ignite/site/trunk/scss/ignite.scss (original)
+++ ignite/site/trunk/scss/ignite.scss Sat Jan 20 01:48:04 2018
@@ -1245,7 +1245,7 @@ section.page-subsection {
 h3 {
 margin-bottom: 12px;
 border-bottom: 1px solid black;
-font-weight: 300;
+font-weight: 300 !important;
 font-size: 24px !important;
 }
 ul {

svn commit: r1821723 - in /ignite/site/trunk: css/all.css index.html scss/ignite.scss

[dsetrakyan]

Author: dsetrakyan
Date: Fri Jan 19 23:26:20 2018
New Revision: 1821723

URL: http://svn.apache.org/viewvc?rev=1821723=rev
Log:
style update

Modified:
ignite/site/trunk/css/all.css
ignite/site/trunk/index.html
ignite/site/trunk/scss/ignite.scss

Modified: ignite/site/trunk/css/all.css
URL: 
http://svn.apache.org/viewvc/ignite/site/trunk/css/all.css?rev=1821723=1821722=1821723=diff
==
--- ignite/site/trunk/css/all.css (original)
+++ ignite/site/trunk/css/all.css Fri Jan 19 23:26:20 2018
@@ -8676,17 +8676,18 @@ section.page-subsection {
 .section-heading {
   height: 75px;
   text-align: center;
-  margin-top: 20px;
+  margin-top: 50px;
   margin-bottom: 20px;
+  padding-top: 30px;
 }
 .section-heading h2 {
-  font-size: 26px;
+  font-size: 28px;
   font-weight: 300;
   letter-spacing: 5px;
   line-height: 35px;
 }
 .section-heading h1 {
-  font-size: 26px;
+  font-size: 30px;
   font-weight: 300;
   letter-spacing: 5px;
   line-height: 35px;
@@ -8697,11 +8698,11 @@ section.page-subsection {
   }
 }
 
-.feature-box h2 {
+.feature-box h3 {
   text-align: center !important;
   font-weight: 300 !important;
 }
-.feature-box h2:hover {
+.feature-box h3:hover {
   color: #e5;
 }
 .feature-box p {
@@ -8920,7 +8921,6 @@ table.comparison-matrix {
   border: none !important;
   margin-bottom: 20px;
   position: relative;
-  top: -30px;
 }
 table.comparison-matrix > thead > tr {
   background: #e5;

Modified: ignite/site/trunk/index.html
URL: 
http://svn.apache.org/viewvc/ignite/site/trunk/index.html?rev=1821723=1821722=1821723=diff
==
Binary files - no diff available.

Modified: ignite/site/trunk/scss/ignite.scss
URL: 
http://svn.apache.org/viewvc/ignite/site/trunk/scss/ignite.scss?rev=1821723=1821722=1821723=diff
==
--- ignite/site/trunk/scss/ignite.scss (original)
+++ ignite/site/trunk/scss/ignite.scss Fri Jan 19 23:26:20 2018
@@ -1155,18 +1155,19 @@ section.page-subsection {
 .section-heading {
 height: 75px;
 text-align: center;
-margin-top: 20px;
+margin-top: 50px;
 margin-bottom: 20px;
+padding-top:30px;
 
 h2 {
-font-size: 26px;
+font-size: 28px;
 font-weight: 300;
 letter-spacing: 5px;
 line-height: 35px;
 }
 
 h1 {
-font-size: 26px;
+font-size: 30px;
 font-weight: 300;
 letter-spacing: 5px;
 line-height: 35px;
@@ -1178,7 +1179,7 @@ section.page-subsection {
 }
 
 .feature-box {
-h2 {
+h3 {
 text-align: center !important;
 font-weight: 300 !important;
 
@@ -1406,7 +1407,6 @@ table.comparison-matrix {
 border: none !important;
 margin-bottom: 20px;
 position: relative;
-top: -30px;
 
 & > thead > tr {
 background: #e5;

svn commit: r1821719 - in /ignite/site/trunk: css/all.css index.html scss/ignite.scss whatisignite-2.html

[dsetrakyan]

Author: dsetrakyan
Date: Fri Jan 19 22:35:18 2018
New Revision: 1821719

URL: http://svn.apache.org/viewvc?rev=1821719=rev
Log:
updated tags

Modified:
ignite/site/trunk/css/all.css
ignite/site/trunk/index.html
ignite/site/trunk/scss/ignite.scss
ignite/site/trunk/whatisignite-2.html

Modified: ignite/site/trunk/css/all.css
URL: 
http://svn.apache.org/viewvc/ignite/site/trunk/css/all.css?rev=1821719=1821718=1821719=diff
==
--- ignite/site/trunk/css/all.css (original)
+++ ignite/site/trunk/css/all.css Fri Jan 19 22:35:18 2018
@@ -8648,6 +8648,12 @@ section.page-subsection {
 font-size: 30px;
   }
 }
+.main-banner .text > h1 {
+  font-size: 30px;
+  line-height: 35px;
+  letter-spacing: 1.1px;
+  font-weight: 400;
+}
 .main-banner p {
   padding-top: 10px;
   font-size: 24px;
@@ -9473,6 +9479,10 @@ div.square {
   list-style-image: 
url(data:image/png;base64,iVBORw0KGgoNSUhEUgEBCAQAAAC1HAwCC0lEQVR42mNkYAYAAjCB0C8ASUVORK5CYII=);
 }
 
+#ignite-facts h3 {
+  line-height: 40px;
+}
+
 .btn-transparent {
   color: #fff;
   background-color: transparent;

Modified: ignite/site/trunk/index.html
URL: 
http://svn.apache.org/viewvc/ignite/site/trunk/index.html?rev=1821719=1821718=1821719=diff
==
Binary files - no diff available.

Modified: ignite/site/trunk/scss/ignite.scss
URL: 
http://svn.apache.org/viewvc/ignite/site/trunk/scss/ignite.scss?rev=1821719=1821718=1821719=diff
==
--- ignite/site/trunk/scss/ignite.scss (original)
+++ ignite/site/trunk/scss/ignite.scss Fri Jan 19 22:35:18 2018
@@ -1119,7 +1119,16 @@ section.page-subsection {
 line-height: 50px;
 font-size: 30px;
 }
+
+
 }
+& > h1 {
+font-size:30px;
+line-height: 35px;
+letter-spacing: 1.1px;
+font-weight: 400;
+}
+
 }
 
 p {
@@ -2047,3 +2056,9 @@ div.square {
 .dropdown-menu > li {
 list-style-image: 
url(data:image/png;base64,iVBORw0KGgoNSUhEUgEBCAQAAAC1HAwCC0lEQVR42mNkYAYAAjCB0C8ASUVORK5CYII=);
 }
+
+#ignite-facts {
+h3 {
+line-height: 40px;
+}
+}

Modified: ignite/site/trunk/whatisignite-2.html
URL: 
http://svn.apache.org/viewvc/ignite/site/trunk/whatisignite-2.html?rev=1821719=1821718=1821719=diff
==
--- ignite/site/trunk/whatisignite-2.html (original)
+++ ignite/site/trunk/whatisignite-2.html Fri Jan 19 22:35:18 2018
@@ -66,32 +66,7 @@ under the License.
 
 
 
-
-
-
-Main Features
-
-Durable 
Memory
-Persistence
-Distributed 
SQL
-Compute 
Grid
-Machine 
Learningeta
-
-
-
-Use Cases
-
-Data 
Grid
-Database Caching
-Distributed 
Database
-In-Memory Database
-SQL Database
-
-
-
-
-
-
+
 
 Ignite 
Facts
 

svn commit: r1821718 - in /ignite/site/trunk: index-2.html index-3.html index.html

[dsetrakyan]

Author: dsetrakyan
Date: Fri Jan 19 21:34:25 2018
New Revision: 1821718

URL: http://svn.apache.org/viewvc?rev=1821718=rev
Log:
homepage update.

Removed:
ignite/site/trunk/index-2.html
ignite/site/trunk/index-3.html
Modified:
ignite/site/trunk/index.html

Modified: ignite/site/trunk/index.html
URL: 
http://svn.apache.org/viewvc/ignite/site/trunk/index.html?rev=1821718=1821717=1821718=diff
==
Binary files - no diff available.

svn commit: r1821717 - /ignite/site/trunk/index-3.html

[dsetrakyan]

Author: dsetrakyan
Date: Fri Jan 19 21:24:27 2018
New Revision: 1821717

URL: http://svn.apache.org/viewvc?rev=1821717=rev
Log:
wip

Modified:
ignite/site/trunk/index-3.html

Modified: ignite/site/trunk/index-3.html
URL: 
http://svn.apache.org/viewvc/ignite/site/trunk/index-3.html?rev=1821717=1821716=1821717=diff
==
Binary files - no diff available.

svn commit: r1821713 - /ignite/site/trunk/index-3.html

[dsetrakyan]

Author: dsetrakyan
Date: Fri Jan 19 20:59:43 2018
New Revision: 1821713

URL: http://svn.apache.org/viewvc?rev=1821713=rev
Log:
wip

Added:
ignite/site/trunk/index-3.html   (with props)

Added: ignite/site/trunk/index-3.html
URL: 
http://svn.apache.org/viewvc/ignite/site/trunk/index-3.html?rev=1821713=auto
==
Binary file - no diff available.

Propchange: ignite/site/trunk/index-3.html
--
svn:mime-type = application/octet-stream

svn commit: r1821710 - /ignite/site/trunk/index-2.html

[dsetrakyan]

Author: dsetrakyan
Date: Fri Jan 19 20:48:03 2018
New Revision: 1821710

URL: http://svn.apache.org/viewvc?rev=1821710=rev
Log:
wip

Modified:
ignite/site/trunk/index-2.html

Modified: ignite/site/trunk/index-2.html
URL: 
http://svn.apache.org/viewvc/ignite/site/trunk/index-2.html?rev=1821710=1821709=1821710=diff
==
--- ignite/site/trunk/index-2.html (original)
+++ ignite/site/trunk/index-2.html Fri Jan 19 20:48:03 2018
@@ -106,17 +106,20 @@ under the License.
 
 
 
-
-APACHE IGNITE
-
+
+
+
 
-
-a memory-centric distributed
+
+Ignite is a memory-centric distributed
 database, caching, and 
processing platform for
 transactional, analytical, and streaming workloads,
 delivering in-memory speeds at petabyte scale
 
-
+
+BENEFITS
+
+
 
 
 
@@ -180,7 +183,7 @@ under the License.
 
 
 
-MAIN FEATURES
+FEATURES
 
 
 

svn commit: r1821700 - in /ignite/site/trunk: css/all.css scss/ignite.scss

[dsetrakyan]

Author: dsetrakyan
Date: Fri Jan 19 19:33:14 2018
New Revision: 1821700

URL: http://svn.apache.org/viewvc?rev=1821700=rev
Log:
nav fix

Modified:
ignite/site/trunk/css/all.css
ignite/site/trunk/scss/ignite.scss

Modified: ignite/site/trunk/css/all.css
URL: 
http://svn.apache.org/viewvc/ignite/site/trunk/css/all.css?rev=1821700=1821699=1821700=diff
==
--- ignite/site/trunk/css/all.css (original)
+++ ignite/site/trunk/css/all.css Fri Jan 19 19:33:14 2018
@@ -9468,8 +9468,8 @@ div.square {
   list-style-image: 
url(data:image/png;base64,iVBORw0KGgoNSUhEUgEBCAQAAAC1HAwCC0lEQVR42mNkYAYAAjCB0C8ASUVORK5CYII=);
 }
 
-/* fix menu for IE, Edge */
-.dropdown-menu > div.items > li {
+/* Fix menu for IE, Edge */
+.dropdown-menu > li {
   list-style-image: 
url(data:image/png;base64,iVBORw0KGgoNSUhEUgEBCAQAAAC1HAwCC0lEQVR42mNkYAYAAjCB0C8ASUVORK5CYII=);
 }
 

Modified: ignite/site/trunk/scss/ignite.scss
URL: 
http://svn.apache.org/viewvc/ignite/site/trunk/scss/ignite.scss?rev=1821700=1821699=1821700=diff
==
--- ignite/site/trunk/scss/ignite.scss (original)
+++ ignite/site/trunk/scss/ignite.scss Fri Jan 19 19:33:14 2018
@@ -2043,7 +2043,7 @@ div.square {
 list-style-image: 
url(data:image/png;base64,iVBORw0KGgoNSUhEUgEBCAQAAAC1HAwCC0lEQVR42mNkYAYAAjCB0C8ASUVORK5CYII=);
 }
 
-/* fix menu for IE, Edge */
-.dropdown-menu > div.items > li {
+/* Fix menu for IE, Edge */
+.dropdown-menu > li {
 list-style-image: 
url(data:image/png;base64,iVBORw0KGgoNSUhEUgEBCAQAAAC1HAwCC0lEQVR42mNkYAYAAjCB0C8ASUVORK5CYII=);
 }

svn commit: r1821428 - in /ignite/site/trunk: css/all.css scss/ignite.scss

[dsetrakyan]

Author: dsetrakyan
Date: Wed Jan 17 22:22:43 2018
New Revision: 1821428

URL: http://svn.apache.org/viewvc?rev=1821428=rev
Log:
minor updates

Modified:
ignite/site/trunk/css/all.css
ignite/site/trunk/scss/ignite.scss

Modified: ignite/site/trunk/css/all.css
URL: 
http://svn.apache.org/viewvc/ignite/site/trunk/css/all.css?rev=1821428=1821427=1821428=diff
==
--- ignite/site/trunk/css/all.css (original)
+++ ignite/site/trunk/css/all.css Wed Jan 17 22:22:43 2018
@@ -7985,7 +7985,7 @@ img[usemap], map area {
   line-height: 1.4;
 }
 
-.dropdown-menu > li {
+.dropdown-menu {
   list-style-type: none !important;
 }
 

Modified: ignite/site/trunk/scss/ignite.scss
URL: 
http://svn.apache.org/viewvc/ignite/site/trunk/scss/ignite.scss?rev=1821428=1821427=1821428=diff
==
--- ignite/site/trunk/scss/ignite.scss (original)
+++ ignite/site/trunk/scss/ignite.scss Wed Jan 17 22:22:43 2018
@@ -412,7 +412,7 @@ img[usemap], map area{
 line-height: 1.4;
 }
 
-.dropdown-menu > li {
+.dropdown-menu {
 list-style-type: none !important;
 }
 

svn commit: r1821427 [1/3] - in /ignite/site/trunk: css/all.css scss/ignite.scss

[dsetrakyan]

Author: dsetrakyan
Date: Wed Jan 17 22:14:44 2018
New Revision: 1821427

URL: http://svn.apache.org/viewvc?rev=1821427=rev
Log:
minor updates

Modified:
ignite/site/trunk/css/all.css
ignite/site/trunk/scss/ignite.scss

svn commit: r1821427 [2/3] - in /ignite/site/trunk: css/all.css scss/ignite.scss

[dsetrakyan]

Modified: ignite/site/trunk/css/all.css
URL: 
http://svn.apache.org/viewvc/ignite/site/trunk/css/all.css?rev=1821427=1821426=1821427=diff
==
--- ignite/site/trunk/css/all.css (original)
+++ ignite/site/trunk/css/all.css Wed Jan 17 22:14:44 2018
@@ -1,9808 +1,9808 @@
-@charset "UTF-8";
-/* colors */
-/* Scaffolding */
-/* Typography */
-/* Iconography */
-/* Buttons */
-/* Grid system */
-/* Container sizes */
-/* Navbar */
-/* Media queries breakpoints */
-/*! normalize.css v3.0.1 | MIT License | git.io/normalize */
-html {
-  font-family: sans-serif;
-  -ms-text-size-adjust: 100%;
-  -webkit-text-size-adjust: 100%;
-}
-
-body {
-  margin: 0;
-}
-
-article,
-aside,
-details,
-figcaption,
-figure,
-footer,
-header,
-hgroup,
-main,
-nav,
-section,
-summary {
-  display: block;
-}
-
-audio,
-canvas,
-progress,
-video {
-  display: inline-block;
-  vertical-align: baseline;
-}
-
-audio:not([controls]) {
-  display: none;
-  height: 0;
-}
-
-[hidden],
-template {
-  display: none;
-}
-
-a {
-  background: transparent;
-}
-
-a:active,
-a:hover {
-  outline: 0;
-}
-
-abbr[title] {
-  border-bottom: 1px dotted;
-}
-
-b,
-strong {
-  font-weight: bold;
-}
-
-dfn {
-  font-style: italic;
-}
-
-h1 {
-  font-size: 2em;
-  margin: 0.67em 0;
-}
-
-mark {
-  background: #ff0;
-  color: #000;
-}
-
-small {
-  font-size: 80%;
-}
-
-sub,
-sup {
-  font-size: 75%;
-  line-height: 0;
-  position: relative;
-  vertical-align: baseline;
-}
-
-sup {
-  top: -0.5em;
-}
-
-sub {
-  bottom: -0.25em;
-}
-
-img {
-  border: 0;
-}
-
-svg:not(:root) {
-  overflow: hidden;
-}
-
-figure {
-  margin: 1em 40px;
-}
-
-hr {
-  -moz-box-sizing: content-box;
-  box-sizing: content-box;
-  height: 0;
-}
-
-pre {
-  overflow: auto;
-}
-
-code,
-kbd,
-pre,
-samp {
-  font-family: monospace, monospace;
-  font-size: 1em;
-}
-
-button,
-input,
-optgroup,
-select,
-textarea {
-  color: inherit;
-  font: inherit;
-  margin: 0;
-}
-
-button {
-  overflow: visible;
-}
-
-button,
-select {
-  text-transform: none;
-}
-
-button,
-html input[type="button"],
-input[type="reset"],
-input[type="submit"] {
-  -webkit-appearance: button;
-  cursor: pointer;
-}
-
-button[disabled],
-html input[disabled] {
-  cursor: default;
-}
-
-button::-moz-focus-inner,
-input::-moz-focus-inner {
-  border: 0;
-  padding: 0;
-}
-
-input {
-  line-height: normal;
-}
-
-input[type="checkbox"],
-input[type="radio"] {
-  box-sizing: border-box;
-  padding: 0;
-}
-
-input[type="number"]::-webkit-inner-spin-button,
-input[type="number"]::-webkit-outer-spin-button {
-  height: auto;
-}
-
-input[type="search"] {
-  -webkit-appearance: textfield;
-  -moz-box-sizing: content-box;
-  -webkit-box-sizing: content-box;
-  box-sizing: content-box;
-}
-
-input[type="search"]::-webkit-search-cancel-button,
-input[type="search"]::-webkit-search-decoration {
-  -webkit-appearance: none;
-}
-
-fieldset {
-  border: 1px solid #c0c0c0;
-  margin: 0 2px;
-  padding: 0.35em 0.625em 0.75em;
-}
-
-legend {
-  border: 0;
-  padding: 0;
-}
-
-textarea {
-  overflow: auto;
-}
-
-optgroup {
-  font-weight: bold;
-}
-
-table {
-  border-collapse: collapse;
-  border-spacing: 0;
-}
-
-td,
-th {
-  padding: 0;
-}
-
-@media print {
-  * {
-text-shadow: none !important;
-color: #000 !important;
-box-shadow: none !important;
-  }
-
-  a,
-  a:visited {
-text-decoration: underline;
-  }
-
-  a[href]:after {
-content: " (" attr(href) ")";
-  }
-
-  abbr[title]:after {
-content: " (" attr(title) ")";
-  }
-
-  a[href^="javascript:"]:after,
-  a[href^="#"]:after {
-content: "";
-  }
-
-  pre,
-  blockquote {
-border: 1px solid #999;
-page-break-inside: avoid;
-  }
-
-  thead {
-display: table-header-group;
-  }
-
-  tr,
-  img {
-page-break-inside: avoid;
-  }
-
-  img {
-max-width: 100% !important;
-  }
-
-  p,
-  h2,
-  h3 {
-orphans: 3;
-widows: 3;
-  }
-
-  h2,
-  h3 {
-page-break-after: avoid;
-  }
-
-  select {
-background: #fff !important;
-  }
-
-  .navbar {
-display: none;
-  }
-
-  .table td,
-  .table th {
-background-color: #fff !important;
-  }
-
-  .btn > .caret,
-  .dropup > .btn > .caret {
-border-top-color: #000 !important;
-  }
-
-  .label {
-border: 1px solid #000;
-  }
-
-  .table {
-border-collapse: collapse !important;
-  }
-
-  .table-bordered th,
-  .table-bordered td {
-border: 1px solid #ddd !important;
-  }
-}
-@font-face {
-  font-family: 'Glyphicons Halflings';
-  src: url("../fonts/glyphicons-halflings-regular.eot");
-  src: url("../fonts/glyphicons-halflings-regular.eot?#iefix") 
format("embedded-opentype"), url("../fonts/glyphicons-halflings-regular.woff") 
format("woff"), url("../fonts/glyphicons-halflings-regular.ttf") 
format("truetype"), 
url("../fonts/glyphicons-halflings-regular.svg#glyphicons_halflingsregular") 
format("svg");
-}
-.glyphicon {
-  position: relative;
-  top: 1px;
-  display: inline-block;
-  

svn commit: r1821427 [3/3] - in /ignite/site/trunk: css/all.css scss/ignite.scss

[dsetrakyan]

Modified: ignite/site/trunk/scss/ignite.scss
URL: 
http://svn.apache.org/viewvc/ignite/site/trunk/scss/ignite.scss?rev=1821427=1821426=1821427=diff
==
--- ignite/site/trunk/scss/ignite.scss (original)
+++ ignite/site/trunk/scss/ignite.scss Wed Jan 17 22:14:44 2018
@@ -412,7 +412,7 @@ img[usemap], map area{
 line-height: 1.4;
 }
 
-.dropdown-menu {
+.dropdown-menu > li {
 list-style-type: none !important;
 }
 

svn commit: r1820618 - /ignite/site/trunk/whatisignite.html

[dsetrakyan]

Author: dsetrakyan
Date: Tue Jan  9 02:41:50 2018
New Revision: 1820618

URL: http://svn.apache.org/viewvc?rev=1820618=rev
Log:
minor updates

Modified:
ignite/site/trunk/whatisignite.html

Modified: ignite/site/trunk/whatisignite.html
URL: 
http://svn.apache.org/viewvc/ignite/site/trunk/whatisignite.html?rev=1820618=1820617=1820618=diff
==
--- ignite/site/trunk/whatisignite.html (original)
+++ ignite/site/trunk/whatisignite.html Tue Jan  9 02:41:50 2018
@@ -123,7 +123,7 @@ under the License.
 Ignite 
Facts
 
 
-Is Ignite a persistent or in-memory-only storage?
+Is Ignite a persistent or memory-only 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, smaller operational data sets

svn commit: r1820617 - /ignite/site/trunk/whatisignite.html

[dsetrakyan]

Author: dsetrakyan
Date: Tue Jan  9 02:13:34 2018
New Revision: 1820617

URL: http://svn.apache.org/viewvc?rev=1820617=rev
Log:
minor updates

Modified:
ignite/site/trunk/whatisignite.html

Modified: ignite/site/trunk/whatisignite.html
URL: 
http://svn.apache.org/viewvc/ignite/site/trunk/whatisignite.html?rev=1820617=1820616=1820617=diff
==
--- ignite/site/trunk/whatisignite.html (original)
+++ ignite/site/trunk/whatisignite.html Tue Jan  9 02:13:34 2018
@@ -149,6 +149,15 @@ under the License.
 
 
 
+Is Ignite a distributed cache?
+
+Yes. When native persistence is disabled, 
Ignite becomes a distributed cache.
+Ignite implements JCache specification (JSR 107) and 
provides
+a lot more functionality than required by the 
specification, including partitioned and replicated
+distribution modes, distributed ACID transactions, SQL 
queries, native persistence, and more.
+
+
+
 Is Ignite a distributed database?
 
 Yes. Data in Ignite is either partitioned 
or replicated across a cluster of

svn commit: r1820616 - /ignite/site/trunk/whatisignite.html

[dsetrakyan]

Author: dsetrakyan
Date: Tue Jan  9 02:05:22 2018
New Revision: 1820616

URL: http://svn.apache.org/viewvc?rev=1820616=rev
Log:
minor updates

Modified:
ignite/site/trunk/whatisignite.html

Modified: ignite/site/trunk/whatisignite.html
URL: 
http://svn.apache.org/viewvc/ignite/site/trunk/whatisignite.html?rev=1820616=1820615=1820616=diff
==
--- ignite/site/trunk/whatisignite.html (original)
+++ ignite/site/trunk/whatisignite.html Tue Jan  9 02:05:22 2018
@@ -126,7 +126,7 @@ under the License.
 Is Ignite a persistent or in-memory-only 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
+data sets bigger than can fit in the available memory. 
Essentially, 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.
 

svn commit: r1820614 - /ignite/site/trunk/whatisignite.html

[dsetrakyan]

Author: dsetrakyan
Date: Tue Jan  9 02:03:10 2018
New Revision: 1820614

URL: http://svn.apache.org/viewvc?rev=1820614=rev
Log:
minor updates

Modified:
ignite/site/trunk/whatisignite.html

Modified: ignite/site/trunk/whatisignite.html
URL: 
http://svn.apache.org/viewvc/ignite/site/trunk/whatisignite.html?rev=1820614=1820613=1820614=diff
==
--- ignite/site/trunk/whatisignite.html (original)
+++ ignite/site/trunk/whatisignite.html Tue Jan  9 02:03:10 2018
@@ -191,6 +191,13 @@ under the License.
 
 
 
+Is Ignite a multi-model database?
+
+Yes. Ignite supports both, key-value and 
SQL for modelling and accessing data.
+In addition, Ignite provides strong processing APIs for 
computing on distributed data.
+
+
+
 Is Ignite a key-value store?
 
 Yes. Ignite provides a feature rich 
key-value API, that is JCache (JSR-107) compliant

svn commit: r1820613 - /ignite/site/trunk/whatisignite.html

[dsetrakyan]

Author: dsetrakyan
Date: Tue Jan  9 01:57:34 2018
New Revision: 1820613

URL: http://svn.apache.org/viewvc?rev=1820613=rev
Log:
minor updates

Modified:
ignite/site/trunk/whatisignite.html

Modified: ignite/site/trunk/whatisignite.html
URL: 
http://svn.apache.org/viewvc/ignite/site/trunk/whatisignite.html?rev=1820613=1820612=1820613=diff
==
--- ignite/site/trunk/whatisignite.html (original)
+++ ignite/site/trunk/whatisignite.html Tue Jan  9 01:57:34 2018
@@ -171,6 +171,13 @@ under the License.
 
 
 
+Is Ignite a NoSQL database?
+
+Not exactly. Just like other NoSQL 
databases, Ignite is highly available and
+horizontally scalable. However, unlike other NoSQL 
databases, Ignite supports SQL and ACID transactions.
+
+
+
 Is Ignite a transactional database?
 
 Not fully. ACID Transactions are 
supported, but only at key-value API level.

svn commit: r1820611 - /ignite/site/trunk/index.html

[dsetrakyan]

Author: dsetrakyan
Date: Tue Jan  9 00:14:46 2018
New Revision: 1820611

URL: http://svn.apache.org/viewvc?rev=1820611=rev
Log:
Homepage update.

Modified:
ignite/site/trunk/index.html

Modified: ignite/site/trunk/index.html
URL: 
http://svn.apache.org/viewvc/ignite/site/trunk/index.html?rev=1820611=1820610=1820611=diff
==
Binary files - no diff available.

svn commit: r1820415 - in /ignite/site/trunk: index.html whatisignite.html

[dsetrakyan]

Author: dsetrakyan
Date: Sat Jan  6 18:43:14 2018
New Revision: 1820415

URL: http://svn.apache.org/viewvc?rev=1820415=rev
Log:
minor updates

Modified:
ignite/site/trunk/index.html
ignite/site/trunk/whatisignite.html

Modified: ignite/site/trunk/index.html
URL: 
http://svn.apache.org/viewvc/ignite/site/trunk/index.html?rev=1820415=1820414=1820415=diff
==
Binary files - no diff available.

Modified: ignite/site/trunk/whatisignite.html
URL: 
http://svn.apache.org/viewvc/ignite/site/trunk/whatisignite.html?rev=1820415=1820414=1820415=diff
==
--- ignite/site/trunk/whatisignite.html (original)
+++ ignite/site/trunk/whatisignite.html Sat Jan  6 18:43:14 2018
@@ -55,10 +55,10 @@ under the License.
 
 Apache 
Ignite is ...
 
-a memory-centric distributed
+memory-centric distributed
 database, caching, and 
processing platform for
-transactional, analytical, and streaming workloads,
-delivering in-memory speeds at petabyte scale
+transactional, analytical, and streaming workloads,
+delivering in-memory speeds at petabyte 
scale
 
 
 

svn commit: r1820159 - /ignite/site/trunk/index.html

[dsetrakyan]

Author: dsetrakyan
Date: Thu Jan  4 17:54:57 2018
New Revision: 1820159

URL: http://svn.apache.org/viewvc?rev=1820159=rev
Log:
Homepage update.

Modified:
ignite/site/trunk/index.html

Modified: ignite/site/trunk/index.html
URL: 
http://svn.apache.org/viewvc/ignite/site/trunk/index.html?rev=1820159=1820158=1820159=diff
==
Binary files - no diff available.

svn commit: r1820158 - /ignite/site/trunk/index.html

[dsetrakyan]

Author: dsetrakyan
Date: Thu Jan  4 17:50:26 2018
New Revision: 1820158

URL: http://svn.apache.org/viewvc?rev=1820158=rev
Log:
Homepage update.

Modified:
ignite/site/trunk/index.html

Modified: ignite/site/trunk/index.html
URL: 
http://svn.apache.org/viewvc/ignite/site/trunk/index.html?rev=1820158=1820157=1820158=diff
==
Binary files - no diff available.

svn commit: r1816096 - /ignite/site/trunk/whatisignite.html

[dsetrakyan]

Author: dsetrakyan
Date: Thu Nov 23 01:08:20 2017
New Revision: 1816096

URL: http://svn.apache.org/viewvc?rev=1816096=rev
Log:
minor

Modified:
ignite/site/trunk/whatisignite.html

Modified: ignite/site/trunk/whatisignite.html
URL: 
http://svn.apache.org/viewvc/ignite/site/trunk/whatisignite.html?rev=1816096=1816095=1816096=diff
==
--- ignite/site/trunk/whatisignite.html (original)
+++ ignite/site/trunk/whatisignite.html Thu Nov 23 01:08:20 2017
@@ -143,7 +143,7 @@ under the License.
 Is Ignite an in-memory data grid (IMDG)?
 
 Yes. Ignite is a full-featured 
distributed key-value data grid, which can be used either in
-in-memory-only mode or with Ignite native persistence. It 
can also automatically integrate with any 3rd party databases,
+memory-only mode or with Ignite native persistence. It can 
also automatically integrate with any 3rd party databases,
 including any RDBMS or NoSQL stores.
 
 

svn commit: r1816095 - /ignite/site/trunk/whatisignite.html

[dsetrakyan]

Author: dsetrakyan
Date: Thu Nov 23 00:56:56 2017
New Revision: 1816095

URL: http://svn.apache.org/viewvc?rev=1816095=rev
Log:
minor

Modified:
ignite/site/trunk/whatisignite.html

Modified: ignite/site/trunk/whatisignite.html
URL: 
http://svn.apache.org/viewvc/ignite/site/trunk/whatisignite.html?rev=1816095=1816094=1816095=diff
==
--- ignite/site/trunk/whatisignite.html (original)
+++ ignite/site/trunk/whatisignite.html Thu Nov 23 00:56:56 2017
@@ -135,15 +135,15 @@ under the License.
 Is Ignite an in-memory database (IMDB)?
 
 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 
distributed in-memory database, with
+persistence can be disabled and Ignite can act as a 
distributed in-memory database, with
 support for SQL and distributed joins.
 
 
 
 Is Ignite an in-memory data grid (IMDG)?
 
-Yes. Ignite is a full-featured 
distributed key-value data grid, which can be used either in pure
-in-memory mode or with Ignite native persistence. It can 
also automatically integrate with any 3rd party databases,
+Yes. Ignite is a full-featured 
distributed key-value data grid, which can be used either in
+in-memory-only mode or with Ignite native persistence. It 
can also automatically integrate with any 3rd party databases,
 including any RDBMS or NoSQL stores.
 
 
@@ -165,7 +165,7 @@ under the License.
 Ignite also does not support foreign key constraints.
 
 
-Essentially, Ignite purposely does not support any 
constraints that would entail a cluster broadcast
+Essentially, Ignite purposely does not support any 
constraints that would entail a cluster-wide broadcast
 message for each update and significantly hurt performance 
and scalability of the system.
 
 
@@ -179,7 +179,7 @@ under the License.
 
 
 At SQL level Ignite supports atomic, but not yet 
transactional consistency. Ignite community plans
-to implement SQL transactions in version 2.4.
+to implement SQL transactions in version 2.5.
 
 
 

svn commit: r1816094 - /ignite/site/trunk/whatisignite.html

[dsetrakyan]

Author: dsetrakyan
Date: Thu Nov 23 00:51:25 2017
New Revision: 1816094

URL: http://svn.apache.org/viewvc?rev=1816094=rev
Log:
minor

Modified:
ignite/site/trunk/whatisignite.html

Modified: ignite/site/trunk/whatisignite.html
URL: 
http://svn.apache.org/viewvc/ignite/site/trunk/whatisignite.html?rev=1816094=1816093=1816094=diff
==
--- ignite/site/trunk/whatisignite.html (original)
+++ ignite/site/trunk/whatisignite.html Thu Nov 23 00:51:25 2017
@@ -122,7 +122,7 @@ under the License.
 Ignite 
Facts
 
 
-Is Ignite a persistent or pure in-memory storage?
+Is Ignite a persistent or in-memory-only 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

svn commit: r1815550 - /ignite/site/trunk/index.html

[dsetrakyan]

Author: dsetrakyan
Date: Fri Nov 17 05:41:39 2017
New Revision: 1815550

URL: http://svn.apache.org/viewvc?rev=1815550=rev
Log:
updated banner text

Modified:
ignite/site/trunk/index.html

Modified: ignite/site/trunk/index.html
URL: 
http://svn.apache.org/viewvc/ignite/site/trunk/index.html?rev=1815550=1815549=1815550=diff
==
Binary files - no diff available.

svn commit: r1812055 - /ignite/site/trunk/whatisignite.html

[dsetrakyan]

Author: dsetrakyan
Date: Thu Oct 12 22:01:13 2017
New Revision: 1812055

URL: http://svn.apache.org/viewvc?rev=1812055=rev
Log:
Minor.

Modified:
ignite/site/trunk/whatisignite.html

Modified: ignite/site/trunk/whatisignite.html
URL: 
http://svn.apache.org/viewvc/ignite/site/trunk/whatisignite.html?rev=1812055=1812054=1812055=diff
==
--- ignite/site/trunk/whatisignite.html (original)
+++ ignite/site/trunk/whatisignite.html Thu Oct 12 22:01:13 2017
@@ -79,7 +79,7 @@ under the License.
 Ignite Persistence
 
 Ignite native 
persistence is a distributed,
-strongly consistent disk store 
that transparently integrates with Ignite's durable memory.
+strongly consistent disk store that transparently 
integrates with Ignite's durable memory.
 
 ACID Compliance
 

svn commit: r1812054 - /ignite/site/trunk/whatisignite.html

[dsetrakyan]

Author: dsetrakyan
Date: Thu Oct 12 21:48:26 2017
New Revision: 1812054

URL: http://svn.apache.org/viewvc?rev=1812054=rev
Log:
Minor.

Modified:
ignite/site/trunk/whatisignite.html

Modified: ignite/site/trunk/whatisignite.html
URL: 
http://svn.apache.org/viewvc/ignite/site/trunk/whatisignite.html?rev=1812054=1812053=1812054=diff
==
--- ignite/site/trunk/whatisignite.html (original)
+++ ignite/site/trunk/whatisignite.html Thu Oct 12 21:48:26 2017
@@ -78,12 +78,8 @@ under the License.
 
 Ignite Persistence
 
-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.
-
-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.
+Ignite native 
persistence is a distributed,
+strongly consistent disk store 
that transparently integrates with Ignite's durable memory.
 
 ACID Compliance
 

svn commit: r1811379 - /ignite/site/trunk/features/persistence.html

[dsetrakyan]

Author: dsetrakyan
Date: Sat Oct  7 02:11:04 2017
New Revision: 1811379

URL: http://svn.apache.org/viewvc?rev=1811379=rev
Log:
Minor.

Modified:
ignite/site/trunk/features/persistence.html

Modified: ignite/site/trunk/features/persistence.html
URL: 
http://svn.apache.org/viewvc/ignite/site/trunk/features/persistence.html?rev=1811379=1811378=1811379=diff
==
--- ignite/site/trunk/features/persistence.html (original)
+++ ignite/site/trunk/features/persistence.html Sat Oct  7 02:11:04 2017
@@ -62,7 +62,7 @@ under the License.
 
 
 With the the native persistence enabled, Ignite 
always stores a superset of data on disk,
-and as much as it can in RAM based on the capacity 
of the latter. For example, if there are
+and as much as possible in RAM. For example, if 
there are
 100 entries and RAM has the capacity to store only 
20, then all 100 will be stored on disk
 and only 20 will be cached in RAM for better 
performance.
 
@@ -72,8 +72,7 @@ under the License.
 
 
 
-The native persistence has the following characteristics 
making it different from 3rd party
-databases that can be used as an alternative persistence 
layer in Ignite:
+The native persistence has the following important 
characteristics:
 
 
 
@@ -81,16 +80,16 @@ under the License.
 Ignite can be used as a memory-centric distributed SQL 
database.
 
 
-No need to have all the data and indexes in memory. 
Ignite persistence allows storing a superset
+No need to have all the data in memory. Ignite 
persistence allows storing a superset
 of data on disk and only most frequently used subsets 
in memory.
 
 
-Instantaneous cluster restarts. If the whole cluster 
goes down there is no need to warm up the
-memory by preloading data from the Ignite Persistence. 
The cluster becomes fully operational
-once all the cluster nodes are interconnected with 
each other.
+Instantaneous cluster restarts. Ignite becomes fully 
operational from disk immediately
+upon cluster startup or restart. There is no need to 
preload or warm up the in-memory caches.
+The data will be loaded in-memory lazily, as it gets 
accessed.
 
 
-Data and indexes are stored in a similar format both 
in memory and on disk which helps avoid
+Data and indexes are stored in a similar format both 
in memory and on disk, which helps avoid
 expensive transformations when moving data between 
memory and disk.
 
 
@@ -101,49 +100,37 @@ under the License.
 Write-Ahead Log
 
 Every time the data is updated in memory, the update will 
be appended to the tail of
-a write-ahead log (WAL). The purpose of the WAL is to 
propagate updates to disk in
-the fastest way possible and provide a recovery mechanism 
for scenarios where a single node or the
-whole cluster goes down.
+the write-ahead log (WAL). The purpose of the WAL is to 
propagate updates to disk in
+the fastest way possible and provide a consistent recovery 
mechanism that supports full cluster failures.
 
 
 The whole WAL is split into several files, called 
segments, that are filled out sequentially.
-Once a segment is full, its content will be copied to the 
WAL archive and kept there for the
-time defined by several configuration parameters. While 
the segment is being copied, another segment
-will be treated as an active WAL file and will accept all 
the updates coming from the application side.
+Once a segment is full, its content will be copied to the 
WAL archive where it will be preserved
+for a configurable amount of time. While the segment is 
being copied, another segment
+will be treated as an active WAL file.
 
 
-It is worth mentioning that a cluster can always be 
recovered to the latest successfully committed
-transaction

svn commit: r1811377 - /ignite/site/trunk/features/sql.html

[dsetrakyan]

Author: dsetrakyan
Date: Sat Oct  7 01:48:30 2017
New Revision: 1811377

URL: http://svn.apache.org/viewvc?rev=1811377=rev
Log:
SQL description update.

Modified:
ignite/site/trunk/features/sql.html

Modified: ignite/site/trunk/features/sql.html
URL: 
http://svn.apache.org/viewvc/ignite/site/trunk/features/sql.html?rev=1811377=1811376=1811377=diff
==
Binary files - no diff available.

svn commit: r1810258 - /ignite/site/trunk/features/sql.html

[dsetrakyan]

Author: dsetrakyan
Date: Sun Oct  1 10:02:56 2017
New Revision: 1810258

URL: http://svn.apache.org/viewvc?rev=1810258=rev
Log:
SQL description update.

Modified:
ignite/site/trunk/features/sql.html

Modified: ignite/site/trunk/features/sql.html
URL: 
http://svn.apache.org/viewvc/ignite/site/trunk/features/sql.html?rev=1810258=1810257=1810258=diff
==
Binary files - no diff available.

svn commit: r1810257 - in /ignite/site/trunk: features/sql.html use-cases/database/in-memory-database.html

[dsetrakyan]

Author: dsetrakyan
Date: Sun Oct  1 09:51:57 2017
New Revision: 1810257

URL: http://svn.apache.org/viewvc?rev=1810257=rev
Log:
Updated text and added distributed joins.

Modified:
ignite/site/trunk/features/sql.html
ignite/site/trunk/use-cases/database/in-memory-database.html

Modified: ignite/site/trunk/features/sql.html
URL: 
http://svn.apache.org/viewvc/ignite/site/trunk/features/sql.html?rev=1810257=1810256=1810257=diff
==
Binary files - no diff available.

Modified: ignite/site/trunk/use-cases/database/in-memory-database.html
URL: 
http://svn.apache.org/viewvc/ignite/site/trunk/use-cases/database/in-memory-database.html?rev=1810257=1810256=1810257=diff
==
--- ignite/site/trunk/use-cases/database/in-memory-database.html (original)
+++ ignite/site/trunk/use-cases/database/in-memory-database.html Sun Oct  1 
09:51:57 2017
@@ -75,7 +75,7 @@ under the License.
 
 
 
-One of distinguishing characteristics of Ignite SQL is the 
support for
+One of the distinguishing characteristics of Ignite SQL is the 
support for
 https://apacheignite.readme.io/docs/sql-queries#distributed-joins; 
target="_blank">distributed SQL JOINs,
 which works in both, collocated and non-collocated fashions. 
When collocated, the JOINs are
 executed on the local data available on each node without 
having to move large data sets

svn commit: r1810256 - /ignite/site/trunk/features/sql.html

[dsetrakyan]

Author: dsetrakyan
Date: Sun Oct  1 09:46:55 2017
New Revision: 1810256

URL: http://svn.apache.org/viewvc?rev=1810256=rev
Log:
Updated text and added distributed joins.

Modified:
ignite/site/trunk/features/sql.html

Modified: ignite/site/trunk/features/sql.html
URL: 
http://svn.apache.org/viewvc/ignite/site/trunk/features/sql.html?rev=1810256=1810255=1810256=diff
==
Binary files - no diff available.

svn commit: r1810255 - in /ignite/site/trunk: features/sql.html use-cases/database/in-memory-database.html

[dsetrakyan]

Author: dsetrakyan
Date: Sun Oct  1 09:45:34 2017
New Revision: 1810255

URL: http://svn.apache.org/viewvc?rev=1810255=rev
Log:
Updated text and added distributed joins.

Modified:
ignite/site/trunk/features/sql.html
ignite/site/trunk/use-cases/database/in-memory-database.html

Modified: ignite/site/trunk/features/sql.html
URL: 
http://svn.apache.org/viewvc/ignite/site/trunk/features/sql.html?rev=1810255=1810254=1810255=diff
==
Binary files - no diff available.

Modified: ignite/site/trunk/use-cases/database/in-memory-database.html
URL: 
http://svn.apache.org/viewvc/ignite/site/trunk/use-cases/database/in-memory-database.html?rev=1810255=1810254=1810255=diff
==
--- ignite/site/trunk/use-cases/database/in-memory-database.html (original)
+++ ignite/site/trunk/use-cases/database/in-memory-database.html Sun Oct  1 
09:45:34 2017
@@ -77,7 +77,7 @@ under the License.
 
 One of distinguishing characteristics of Ignite SQL is the 
support for
 https://apacheignite.readme.io/docs/sql-queries#distributed-joins; 
target="_blank">distributed SQL JOINs,
-which works in both, collocated and non-collocated fashion. 
When collocated, the JOINs are
+which works in both, collocated and non-collocated fashions. 
When collocated, the JOINs are
 executed on the local data available on each node without 
having to move large data sets
 across the network. Such collocated approach provides the best 
scalability and performance
 in distributed clusters.

svn commit: r1810254 - /ignite/site/trunk/features/sql.html

[dsetrakyan]

Author: dsetrakyan
Date: Sun Oct  1 09:44:52 2017
New Revision: 1810254

URL: http://svn.apache.org/viewvc?rev=1810254=rev
Log:
Updated text and added distributed joins.

Modified:
ignite/site/trunk/features/sql.html

Modified: ignite/site/trunk/features/sql.html
URL: 
http://svn.apache.org/viewvc/ignite/site/trunk/features/sql.html?rev=1810254=1810253=1810254=diff
==
Binary files - no diff available.

svn commit: r1810253 - /ignite/site/trunk/index.html

[dsetrakyan]

Author: dsetrakyan
Date: Sun Oct  1 09:06:28 2017
New Revision: 1810253

URL: http://svn.apache.org/viewvc?rev=1810253=rev
Log:
added tooltips.

Modified:
ignite/site/trunk/index.html

Modified: ignite/site/trunk/index.html
URL: 
http://svn.apache.org/viewvc/ignite/site/trunk/index.html?rev=1810253=1810252=1810253=diff
==
Binary files - no diff available.

svn commit: r1809682 - /ignite/site/trunk/features/sql.html

[dsetrakyan]

Author: dsetrakyan
Date: Tue Sep 26 03:01:32 2017
New Revision: 1809682

URL: http://svn.apache.org/viewvc?rev=1809682=rev
Log:
Some content improvements.

Modified:
ignite/site/trunk/features/sql.html

Modified: ignite/site/trunk/features/sql.html
URL: 
http://svn.apache.org/viewvc/ignite/site/trunk/features/sql.html?rev=1809682=1809681=1809682=diff
==
Binary files - no diff available.

svn commit: r1809681 - /ignite/site/trunk/features/sql.html

[dsetrakyan]

Author: dsetrakyan
Date: Tue Sep 26 03:00:49 2017
New Revision: 1809681

URL: http://svn.apache.org/viewvc?rev=1809681=rev
Log:
Some content improvements.

Modified:
ignite/site/trunk/features/sql.html

Modified: ignite/site/trunk/features/sql.html
URL: 
http://svn.apache.org/viewvc/ignite/site/trunk/features/sql.html?rev=1809681=1809680=1809681=diff
==
Binary files - no diff available.

svn commit: r1809680 - /ignite/site/trunk/features/sql.html

[dsetrakyan]

Author: dsetrakyan
Date: Tue Sep 26 02:49:19 2017
New Revision: 1809680

URL: http://svn.apache.org/viewvc?rev=1809680=rev
Log:
Some content improvements.

Modified:
ignite/site/trunk/features/sql.html

Modified: ignite/site/trunk/features/sql.html
URL: 
http://svn.apache.org/viewvc/ignite/site/trunk/features/sql.html?rev=1809680=1809679=1809680=diff
==
Binary files - no diff available.

svn commit: r1809678 - /ignite/site/trunk/features/sql.html

[dsetrakyan]

Author: dsetrakyan
Date: Tue Sep 26 02:41:59 2017
New Revision: 1809678

URL: http://svn.apache.org/viewvc?rev=1809678=rev
Log:
Some content improvements.

Modified:
ignite/site/trunk/features/sql.html

Modified: ignite/site/trunk/features/sql.html
URL: 
http://svn.apache.org/viewvc/ignite/site/trunk/features/sql.html?rev=1809678=1809677=1809678=diff
==
Binary files - no diff available.

svn commit: r1809677 - in /ignite/site/trunk: collocatedprocessing.html use-cases/database/key-value-store.html whatisignite.html

[dsetrakyan]

Author: dsetrakyan
Date: Tue Sep 26 02:34:05 2017
New Revision: 1809677

URL: http://svn.apache.org/viewvc?rev=1809677=rev
Log:
Some content improvements.

Modified:
ignite/site/trunk/collocatedprocessing.html
ignite/site/trunk/use-cases/database/key-value-store.html
ignite/site/trunk/whatisignite.html

Modified: ignite/site/trunk/collocatedprocessing.html
URL: 
http://svn.apache.org/viewvc/ignite/site/trunk/collocatedprocessing.html?rev=1809677=1809676=1809677=diff
==
--- ignite/site/trunk/collocatedprocessing.html (original)
+++ ignite/site/trunk/collocatedprocessing.html Tue Sep 26 02:34:05 2017
@@ -62,7 +62,7 @@ under the License.
 network is the most expensive operation in a 
distributed system.
 
 
-A much more scalable approach is collocated 
processing that reverses the flow by bringing
+A much more scalable approach is 
collocated processing that reverses the flow by bringing
 the computations to the servers where the data 
actually resides. This approach allows you to
 execute advanced logic or distributed SQL with JOINs 
exactly where the data is stored avoiding
 expensive serialization and network trips.
@@ -75,25 +75,19 @@ under the License.
 
 Usage Example
 
-Let's assume that a blizzard is approaching New York City. 
You, as a telecommunication company has to warn
-all the people sending a message to everyone with precise 
instructions on how to behave during such
-weather conditions. There are around 8 million New Yorkers in 
your database that have to receive
-the text message.
+Let's assume that a blizzard is approaching New York. As a 
telecommunication company, you have to
+send a warning text message to 8 million New Yorkers.
+With the client-server approach the company has to move all 
8 million (!) records
+from the database to the client text messaging application, 
which does not scale.
 
 
-With the client-server approach the company has to connect to 
the database, move all 8 million (!) records
-from there to a client application that will text to everyone. 
This is highly inefficient that wastes
-network and computational resources of company's IT 
infrastructure.
-
-
-However, if the company initially collocates all the cities it 
covers with the people who live there then
-it can send a single computation (!) to the cluster node that 
stores information about all New Yorkers
-and send the text message from there. This approach avoids 8 
million records movement over the network
-and helps utilizing cluster resources for computation needs. 
That's the collocated processing in action!
+A much more efficient approach would be to send the 
text-messaging logic to the cluster node responsible
+for storing the New York residents. This approach moves only 1 
computation instead of 8 million records
+across the network, and performs a lot better.
 
 
 
-Code snippet below shows a way how this computation might look 
like:
+Here is an example of how this logic might look like:
 
 
 

Modified: ignite/site/trunk/use-cases/database/key-value-store.html
URL: 
http://svn.apache.org/viewvc/ignite/site/trunk/use-cases/database/key-value-store.html?rev=1809677=1809676=1809677=diff
==
Binary files - no diff available.

Modified: ignite/site/trunk/whatisignite.html
URL: 
http://svn.apache.org/viewvc/ignite/site/trunk/whatisignite.html?rev=1809677=1809676=1809677=diff
==
--- ignite/site/trunk/whatisignite.html (original)
+++ ignite/site/trunk/whatisignite.html Tue Sep 26 02:34:05 2017
@@ -71,17 +71,17 @@ under the License.
 
 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,
+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

svn commit: r1809446 - in /ignite/site/trunk: download.html includes/header.html

[dsetrakyan]

Author: dsetrakyan
Date: Sat Sep 23 18:46:39 2017
New Revision: 1809446

URL: http://svn.apache.org/viewvc?rev=1809446=rev
Log:
Updated navigation.

Modified:
ignite/site/trunk/download.html
ignite/site/trunk/includes/header.html

Modified: ignite/site/trunk/download.html
URL: 
http://svn.apache.org/viewvc/ignite/site/trunk/download.html?rev=1809446=1809445=1809446=diff
==
--- ignite/site/trunk/download.html (original)
+++ ignite/site/trunk/download.html Sat Sep 23 18:46:39 2017
@@ -134,10 +134,10 @@ under the License.
 Data Grid
 Compute Grid
 Machine 
Learningeta
-More
+More Features
 Tooling
-Ignite Web Console
-More
+Ignite Web 
Console
+More Tooling
 
 
 Runs Everywhere
@@ -152,7 +152,7 @@ under the License.
 In-Memory MapReduce
 Add-Ons
 GA Grideta
-More
+More 
Add-ons
 
 
 
@@ -167,10 +167,10 @@ under the License.
 Data Grid
 Compute Grid
 Machine 
Learningeta
-More
+More 
Features
 Tooling
-Ignite Web Console
-More
+Ignite Web 
Console
+More Tooling
 Runs Everywhere
 Java
 .NET
@@ -183,7 +183,7 @@ under the License.
 In-Memory MapReduce
 Add-Ons
 GA 
Grideta
-More
+More 
Add-ons
 
 
 

Modified: ignite/site/trunk/includes/header.html
URL: 
http://svn.apache.org/viewvc/ignite/site/trunk/includes/header.html?rev=1809446=1809445=1809446=diff
==
--- ignite/site/trunk/includes/header.html (original)
+++ ignite/site/trunk/includes/header.html Sat Sep 23 18:46:39 2017
@@ -65,10 +65,10 @@
 Data Grid
 Compute Grid
 Machine 
Learningeta
-More
+More Features
 Tooling
-Ignite Web Console
-More
+Ignite Web 
Console
+More Tooling
 
 
 Runs Everywhere
@@ -83,7 +83,7 @@
 In-Memory MapReduce
 Add-Ons
 GA Grideta
-More
+More 
Add-ons
 


@@ -98,10 +98,10 @@
 Data Grid
 Compute Grid
 Machine 
Learningeta
-More
+More 
Features
 Tooling
-Ignite Web Console
-More
+Ignite Web 
Console
+More Tooling

svn commit: r1808948 - in /ignite/site/trunk: download.html features/sql.html includes/header.html

[dsetrakyan]

Author: dsetrakyan
Date: Tue Sep 19 21:56:17 2017
New Revision: 1808948

URL: http://svn.apache.org/viewvc?rev=1808948=rev
Log:
minor.

Modified:
ignite/site/trunk/download.html
ignite/site/trunk/features/sql.html
ignite/site/trunk/includes/header.html

Modified: ignite/site/trunk/download.html
URL: 
http://svn.apache.org/viewvc/ignite/site/trunk/download.html?rev=1808948=1808947=1808948=diff
==
--- ignite/site/trunk/download.html (original)
+++ ignite/site/trunk/download.html Tue Sep 19 21:56:17 2017
@@ -130,7 +130,7 @@ under the License.
 Main Features
 Durable Memory
 Native Persistence
-Distributed SQL
+SQL Database
 Data Grid
 Compute Grid
 Machine 
Learningeta
@@ -163,7 +163,7 @@ under the License.
 Main Features
 Durable Memory
 Native Persistence
-Distributed SQL
+SQL 
Database
 Data Grid
 Compute Grid
 Machine 
Learningeta
@@ -192,7 +192,7 @@ under the License.
 Database
 Distributed 
Database
 In-Memory Database
-SQL Database
+
 Key-Value Store
 
 Comparison

Modified: ignite/site/trunk/features/sql.html
URL: 
http://svn.apache.org/viewvc/ignite/site/trunk/features/sql.html?rev=1808948=1808947=1808948=diff
==
Binary files - no diff available.

Modified: ignite/site/trunk/includes/header.html
URL: 
http://svn.apache.org/viewvc/ignite/site/trunk/includes/header.html?rev=1808948=1808947=1808948=diff
==
--- ignite/site/trunk/includes/header.html (original)
+++ ignite/site/trunk/includes/header.html Tue Sep 19 21:56:17 2017
@@ -61,7 +61,7 @@
 Main Features
 Durable Memory
 Native Persistence
-Distributed SQL
+SQL Database
 Data Grid
 Compute Grid
 Machine 
Learningeta
@@ -86,7 +86,7 @@
 More
 

-
+   
 Overview
 What 
is Ignite?
 What 
is Memory-Centric?
@@ -94,7 +94,7 @@
 Main Features
 Durable Memory
 Native Persistence
-Distributed SQL
+SQL 
Database
 Data Grid
 Compute Grid
 Machine 
Learningeta
@@ -115,7 +115,7 @@
 Add-Ons
 GA 
Grideta
 More
-
+   
 
 
 Use Cases
@@ -123,7 +123,7 @@
 Database
 Distributed 
Database
 In-Memory Database
-SQL Database
+
 Key-Value Store
 
 Comparison

svn commit: r1808808 - /ignite/site/trunk/whatisignite.html

[dsetrakyan]

Author: dsetrakyan
Date: Tue Sep 19 01:52:17 2017
New Revision: 1808808

URL: http://svn.apache.org/viewvc?rev=1808808=rev
Log:
minor.

Modified:
ignite/site/trunk/whatisignite.html

Modified: ignite/site/trunk/whatisignite.html
URL: 
http://svn.apache.org/viewvc/ignite/site/trunk/whatisignite.html?rev=1808808=1808807=1808808=diff
==
--- ignite/site/trunk/whatisignite.html (original)
+++ ignite/site/trunk/whatisignite.html Tue Sep 19 01:52:17 2017
@@ -146,7 +146,7 @@ under the License.
 
 Is Ignite an in-memory data grid (IMDG)?
 
-Yes. Ignite is a full-featured data grid, 
which can be used either in pure
+Yes. Ignite is a full-featured 
distributed key-value data grid, which can be used either in pure
 in-memory mode or with Ignite native persistence. It can 
also automatically integrate with any 3rd party databases,
 including any RDBMS or NoSQL stores.
 

svn commit: r1808806 - /ignite/site/trunk/features/datagrid.html

[dsetrakyan]

Author: dsetrakyan
Date: Tue Sep 19 01:42:24 2017
New Revision: 1808806

URL: http://svn.apache.org/viewvc?rev=1808806=rev
Log:
minor.

Modified:
ignite/site/trunk/features/datagrid.html

Modified: ignite/site/trunk/features/datagrid.html
URL: 
http://svn.apache.org/viewvc/ignite/site/trunk/features/datagrid.html?rev=1808806=1808805=1808806=diff
==
--- ignite/site/trunk/features/datagrid.html (original)
+++ ignite/site/trunk/features/datagrid.html Tue Sep 19 01:42:24 2017
@@ -65,7 +65,7 @@ under the License.
 over its data with the support for 
distributed joins.
 
 
-The Data Grid has been built from the ground up to 
linearly scale to hundreds of nodes with strong
+The data grid has been built from the ground up to 
linearly scale to hundreds of nodes with strong
 semantics for data locality and affinity data routing 
to reduce redundant data noise. It 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.

svn commit: r1808804 - /ignite/site/trunk/features/datagrid.html

[dsetrakyan]

Author: dsetrakyan
Date: Tue Sep 19 01:39:50 2017
New Revision: 1808804

URL: http://svn.apache.org/viewvc?rev=1808804=rev
Log:
minor.

Modified:
ignite/site/trunk/features/datagrid.html

Modified: ignite/site/trunk/features/datagrid.html
URL: 
http://svn.apache.org/viewvc/ignite/site/trunk/features/datagrid.html?rev=1808804=1808803=1808804=diff
==
--- ignite/site/trunk/features/datagrid.html (original)
+++ ignite/site/trunk/features/datagrid.html Tue Sep 19 01:39:50 2017
@@ -60,9 +60,9 @@ under the License.
 
 Ignite data grid is a distributed, transactional 
key-value store. Unlike other
 in-memory data grids (IMDG), Ignite enables storing 
data both, in memory and on disk.
-On top of the standard key-value data operations, 
including all JCache (JSR 107) features,
-Ignite data grid also supports SQL 
queries over its data with the support for
-distributed joins.
+On top of the standard key-value data operations, 
including ACID transactions and all the
+JCache (JSR 107) functionality, Ignite also supports 
SQL queries
+over its data with the support for 
distributed joins.
 
 
 The Data Grid has been built from the ground up to 
linearly scale to hundreds of nodes with strong

svn commit: r1808803 - /ignite/site/trunk/index.html

[dsetrakyan]

Author: dsetrakyan
Date: Tue Sep 19 01:31:35 2017
New Revision: 1808803

URL: http://svn.apache.org/viewvc?rev=1808803=rev
Log:
minor.

Modified:
ignite/site/trunk/index.html

Modified: ignite/site/trunk/index.html
URL: 
http://svn.apache.org/viewvc/ignite/site/trunk/index.html?rev=1808803=1808802=1808803=diff
==
Binary files - no diff available.

svn commit: r1808799 - /ignite/site/trunk/features/datagrid.html

[dsetrakyan]

Author: dsetrakyan
Date: Tue Sep 19 01:27:08 2017
New Revision: 1808799

URL: http://svn.apache.org/viewvc?rev=1808799=rev
Log:
minor.

Modified:
ignite/site/trunk/features/datagrid.html

Modified: ignite/site/trunk/features/datagrid.html
URL: 
http://svn.apache.org/viewvc/ignite/site/trunk/features/datagrid.html?rev=1808799=1808798=1808799=diff
==
--- ignite/site/trunk/features/datagrid.html (original)
+++ ignite/site/trunk/features/datagrid.html Tue Sep 19 01:27:08 2017
@@ -60,17 +60,19 @@ under the License.
 
 Ignite data grid is a distributed, transactional 
key-value store. Unlike other
 in-memory data grids (IMDG), Ignite enables storing 
data both, in memory and on disk.
+On top of the standard key-value data operations, 
including all JCache (JSR 107) features,
 Ignite data grid also supports SQL 
queries over its data with the support for
 distributed joins.
-The data grid 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.
 
 
-Ignite Data Grid has been built from the ground up to 
linearly scale to hundreds of nodes with strong
-semantics for data locality and affinity data routing 
to reduce redundant data noise.
-It is one of the fastest implementations of 
transactional or
-atomic data in distributed clusters today. We know it 
because we constantly benchmark it ourselves.
+The Data Grid has been built from the ground up to 
linearly scale to hundreds of nodes with strong
+semantics for data locality and affinity data routing 
to reduce redundant data noise. It 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.
+
+
+Ignite data grid is one of the fastest implementations 
of ACID transactions or
+atomic data updates in distributed clusters today. We 
know it because we constantly benchmark it ourselves.
 
 
 

svn commit: r1808793 - /ignite/site/trunk/use-cases/database/in-memory-database.html

[dsetrakyan]

Author: dsetrakyan
Date: Tue Sep 19 00:11:47 2017
New Revision: 1808793

URL: http://svn.apache.org/viewvc?rev=1808793=rev
Log:
minor

Modified:
ignite/site/trunk/use-cases/database/in-memory-database.html

Modified: ignite/site/trunk/use-cases/database/in-memory-database.html
URL: 
http://svn.apache.org/viewvc/ignite/site/trunk/use-cases/database/in-memory-database.html?rev=1808793=1808792=1808793=diff
==
--- ignite/site/trunk/use-cases/database/in-memory-database.html (original)
+++ ignite/site/trunk/use-cases/database/in-memory-database.html Tue Sep 19 
00:11:47 2017
@@ -69,20 +69,20 @@ under the License.
 Ignite will function as a pure in-memory 
database supporting SQL, together with
 all the existing APIs for pure in-memory use cases.
 
-
-One of distinguishing characteristics of Ignite SQL is 
the support for
-https://apacheignite.readme.io/docs/sql-queries#distributed-joins; 
target="_blank">distributed SQL JOINs,
-which works in both, collocated and non-collocated 
fashion. When collocated, the JOINs are
-executed on the local data available on each node 
without having to move large data sets
-across the network. Such collocated approach provides 
the best scalability and performance
-in distributed clusters.
-
 
 
 
 
 
 
+One of distinguishing characteristics of Ignite SQL is the 
support for
+https://apacheignite.readme.io/docs/sql-queries#distributed-joins; 
target="_blank">distributed SQL JOINs,
+which works in both, collocated and non-collocated fashion. 
When collocated, the JOINs are
+executed on the local data available on each node without 
having to move large data sets
+across the network. Such collocated approach provides the best 
scalability and performance
+in distributed clusters.
+
+
 You should also check Ignite distributed SQL and
 data 
grid features.
 

svn commit: r1808792 - /ignite/site/trunk/use-cases/database/in-memory-database.html

[dsetrakyan]

Author: dsetrakyan
Date: Tue Sep 19 00:10:25 2017
New Revision: 1808792

URL: http://svn.apache.org/viewvc?rev=1808792=rev
Log:
minor

Modified:
ignite/site/trunk/use-cases/database/in-memory-database.html

Modified: ignite/site/trunk/use-cases/database/in-memory-database.html
URL: 
http://svn.apache.org/viewvc/ignite/site/trunk/use-cases/database/in-memory-database.html?rev=1808792=1808791=1808792=diff
==
--- ignite/site/trunk/use-cases/database/in-memory-database.html (original)
+++ ignite/site/trunk/use-cases/database/in-memory-database.html Tue Sep 19 
00:10:25 2017
@@ -83,8 +83,8 @@ under the License.
 
 
 
-You should also check Ignite SQL and
-Data 
Grid features.
+You should also check Ignite distributed SQL and
+data 
grid features.
 
 
 

svn commit: r1808791 - /ignite/site/trunk/features/datagrid.html

[dsetrakyan]

Author: dsetrakyan
Date: Tue Sep 19 00:04:28 2017
New Revision: 1808791

URL: http://svn.apache.org/viewvc?rev=1808791=rev
Log:
minor

Modified:
ignite/site/trunk/features/datagrid.html

Modified: ignite/site/trunk/features/datagrid.html
URL: 
http://svn.apache.org/viewvc/ignite/site/trunk/features/datagrid.html?rev=1808791=1808790=1808791=diff
==
--- ignite/site/trunk/features/datagrid.html (original)
+++ ignite/site/trunk/features/datagrid.html Tue Sep 19 00:04:28 2017
@@ -58,18 +58,18 @@ under the License.
 
 
 
-Ignite Data Grid is a distributed, transactional 
key-value store. Unlike other
+Ignite data grid is a distributed, transactional 
key-value store. Unlike other
 in-memory data grids (IMDG), Ignite enables storing 
data both, in memory and on disk.
-Ignite Data Grid can be viewed as a distributed 
partitioned hash map with every
+Ignite data grid also supports SQL 
queries over its data with the support for
+distributed joins.
+The data grid 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.
 
 
 Ignite Data Grid has been built from the ground up to 
linearly scale to hundreds of nodes with strong
 semantics for data locality and affinity data routing 
to reduce redundant data noise.
-
-
-Ignite Data Grid is lightning fast and is one of the 
fastest implementations of transactional or
+It is one of the fastest implementations of 
transactional or
 atomic data in distributed clusters today. We know it 
because we constantly benchmark it ourselves.
 
 
@@ -80,7 +80,7 @@ under the License.
 
 
 
-The data in the data grid can be stored only in memory, or can 
also be persisted to disk.
+The data in the data grid can be stored either purely in 
memory, or can also be persisted to disk.
 If Ignite 
native persistence is enabled,
 then data and indexes will be persisted natively by Ignite on 
every cluster node. In this case,
 memory only serves as a smaller caching layer of the overall 
persisted data set. All queries and transactions

svn commit: r1808499 - /ignite/site/trunk/memorycentric.html

[dsetrakyan]

Author: dsetrakyan
Date: Sat Sep 16 08:00:51 2017
New Revision: 1808499

URL: http://svn.apache.org/viewvc?rev=1808499=rev
Log:
minor.

Modified:
ignite/site/trunk/memorycentric.html

Modified: ignite/site/trunk/memorycentric.html
URL: 
http://svn.apache.org/viewvc/ignite/site/trunk/memorycentric.html?rev=1808499=1808498=1808499=diff
==
--- ignite/site/trunk/memorycentric.html (original)
+++ ignite/site/trunk/memorycentric.html Sat Sep 16 08:00:51 2017
@@ -91,7 +91,7 @@ under the License.
 exactly where the data is stored avoiding expensive 
serialization and network trips.
 
 
-Learn more about Apache 
Ignite.
+Learn more
 
 
 

svn commit: r1808498 - /ignite/site/trunk/use-cases/caching/database-caching.html

[dsetrakyan]

Author: dsetrakyan
Date: Sat Sep 16 07:58:33 2017
New Revision: 1808498

URL: http://svn.apache.org/viewvc?rev=1808498=rev
Log:
minor.

Modified:
ignite/site/trunk/use-cases/caching/database-caching.html

Modified: ignite/site/trunk/use-cases/caching/database-caching.html
URL: 
http://svn.apache.org/viewvc/ignite/site/trunk/use-cases/caching/database-caching.html?rev=1808498=1808497=1808498=diff
==
--- ignite/site/trunk/use-cases/caching/database-caching.html (original)
+++ ignite/site/trunk/use-cases/caching/database-caching.html Sat Sep 16 
07:58:33 2017
@@ -54,8 +54,9 @@ under the License.
 
 
 
-Ignite Database Caching enables users to keep the most 
frequently accessed data in memory,
-by either partitioning or replicating it across a 
cluster of computers.
+Ignite database caching is implemented in 
the data grid
+component. It enables users to keep the most 
frequently accessed data in memory, by either
+partitioning or replicating it across a cluster of 
computers.
 
 Write-Through & 
Read-Through
 
@@ -86,7 +87,7 @@ under the License.
 
 Data Grid
 
-See Data Grid for more information.
+See data grid for more information.
 
 
 

svn commit: r1808497 - /ignite/site/trunk/use-cases/database/in-memory-database.html

[dsetrakyan]

Author: dsetrakyan
Date: Sat Sep 16 06:45:33 2017
New Revision: 1808497

URL: http://svn.apache.org/viewvc?rev=1808497=rev
Log:
minor.

Modified:
ignite/site/trunk/use-cases/database/in-memory-database.html

Modified: ignite/site/trunk/use-cases/database/in-memory-database.html
URL: 
http://svn.apache.org/viewvc/ignite/site/trunk/use-cases/database/in-memory-database.html?rev=1808497=1808496=1808497=diff
==
--- ignite/site/trunk/use-cases/database/in-memory-database.html (original)
+++ ignite/site/trunk/use-cases/database/in-memory-database.html Sat Sep 16 
06:45:33 2017
@@ -72,7 +72,7 @@ under the License.
 
 One of distinguishing characteristics of Ignite SQL is 
the support for
 https://apacheignite.readme.io/docs/sql-queries#distributed-joins; 
target="_blank">distributed SQL JOINs,
-which work in both, collocated and non-collocated 
fashion. When collocated, the JOINs are
+which works in both, collocated and non-collocated 
fashion. When collocated, the JOINs are
 executed on the local data available on each node 
without having to move large data sets
 across the network. Such collocated approach provides 
the best scalability and performance
 in distributed clusters.

svn commit: r1808492 - /ignite/site/trunk/use-cases/database/in-memory-database.html

[dsetrakyan]

Author: dsetrakyan
Date: Sat Sep 16 01:44:57 2017
New Revision: 1808492

URL: http://svn.apache.org/viewvc?rev=1808492=rev
Log:
minor.

Modified:
ignite/site/trunk/use-cases/database/in-memory-database.html

Modified: ignite/site/trunk/use-cases/database/in-memory-database.html
URL: 
http://svn.apache.org/viewvc/ignite/site/trunk/use-cases/database/in-memory-database.html?rev=1808492=1808491=1808492=diff
==
--- ignite/site/trunk/use-cases/database/in-memory-database.html (original)
+++ ignite/site/trunk/use-cases/database/in-memory-database.html Sat Sep 16 
01:44:57 2017
@@ -54,21 +54,28 @@ under the License.
 
 
 
-Apache Ignite can be used as all-in-one 
-distributed database that supports SQL, key-value, 
compute, machine learning and other
-data processing APIs.
+Apache Ignite can be used as a distributed and 
horizontally scalable
+in-memory database (IMDB) that supports 
ACID transactions and
+can be used with SQL, key-value, compute, machine 
learning and other data processing APIs.
 
 
-With Ignite Durable Memory
-architecture, data as well as indexes can be stored 
both in memory and, optionally, on disk.
-This allows executing distributed SQL, key-value and 
other operations across different memory
-layers achieving the performance and scale of 
in-memory computing together with the disk
-durability and strong consistency in one system.
+With Ignite durable memory
+architecture, data and indexes can be stored both, in 
memory and on disk. The disk persistence
+is optional. When persistence is turned on, Ignite can 
store more data than fits in the available memory, and
+will act as a complete distributed SQL 
database.
 
 
-In the scenarios, when the whole data set and indexes 
fit in memory and the persistence is disabled
-on purpose, Apache Ignite will function as a 
full-fledged in-memory database supporting
-all the existing APIs for a pure in-memory use case.
+In scenarios when the whole data set and indexes fit 
in memory, and the persistence is disabled,
+Ignite will function as a pure in-memory 
database supporting SQL, together with
+all the existing APIs for pure in-memory use cases.
+
+
+One of distinguishing characteristics of Ignite SQL is 
the support for
+https://apacheignite.readme.io/docs/sql-queries#distributed-joins; 
target="_blank">distributed SQL JOINs,
+which work in both, collocated and non-collocated 
fashion. When collocated, the JOINs are
+executed on the local data available on each node 
without having to move large data sets
+across the network. Such collocated approach provides 
the best scalability and performance
+in distributed clusters.
 
 
 
@@ -76,9 +83,8 @@ under the License.
 
 
 
-Check SQL and
-Data 
Grid features sections
-for more technical details.
+You should also check Ignite SQL and
+Data 
Grid features.
 
 
 

svn commit: r1808304 - /ignite/site/trunk/whatisignite.html

[dsetrakyan]

Author: dsetrakyan
Date: Thu Sep 14 03:09:59 2017
New Revision: 1808304

URL: http://svn.apache.org/viewvc?rev=1808304=rev
Log:
minor.

Modified:
ignite/site/trunk/whatisignite.html

Modified: ignite/site/trunk/whatisignite.html
URL: 
http://svn.apache.org/viewvc/ignite/site/trunk/whatisignite.html?rev=1808304=1808303=1808304=diff
==
--- ignite/site/trunk/whatisignite.html (original)
+++ ignite/site/trunk/whatisignite.html Thu Sep 14 03:09:59 2017
@@ -137,7 +137,7 @@ under the License.
 Is Ignite an in-memory data grid (IMDG)?
 
 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 databases,
+in-memory mode or with Ignite native persistence. It can 
also automatically integrate with any 3rd party databases,
 including any RDBMS or NoSQL stores.
 
 

svn commit: r1808303 - /ignite/site/trunk/features/datagrid.html

[dsetrakyan]

Author: dsetrakyan
Date: Thu Sep 14 02:27:52 2017
New Revision: 1808303

URL: http://svn.apache.org/viewvc?rev=1808303=rev
Log:
updated data grid page.

Modified:
ignite/site/trunk/features/datagrid.html

Modified: ignite/site/trunk/features/datagrid.html
URL: 
http://svn.apache.org/viewvc/ignite/site/trunk/features/datagrid.html?rev=1808303=1808302=1808303=diff
==
--- ignite/site/trunk/features/datagrid.html (original)
+++ ignite/site/trunk/features/datagrid.html Thu Sep 14 02:27:52 2017
@@ -39,7 +39,7 @@ under the License.
 
 
 
-
+
 In-Memory Data Grid - Apache Ignite
 
 https://netdna.bootstrapcdn.com/font-awesome/4.2.0/css/font-awesome.css; 
rel="stylesheet"/>

svn commit: r1808302 - /ignite/site/trunk/features/datagrid.html

[dsetrakyan]

Author: dsetrakyan
Date: Thu Sep 14 02:27:18 2017
New Revision: 1808302

URL: http://svn.apache.org/viewvc?rev=1808302=rev
Log:
updated data grid page.

Modified:
ignite/site/trunk/features/datagrid.html

Modified: ignite/site/trunk/features/datagrid.html
URL: 
http://svn.apache.org/viewvc/ignite/site/trunk/features/datagrid.html?rev=1808302=1808301=1808302=diff
==
--- ignite/site/trunk/features/datagrid.html (original)
+++ ignite/site/trunk/features/datagrid.html Thu Sep 14 02:27:18 2017
@@ -281,30 +281,28 @@ under the License.
 
 
 
-Durable Memory
+SQL Support
 
 
-Ignite Durable Memory allows 
storing and processing data and indexes
-both, in memory and on disk. The in-memory 
data, including indexes, is always
-stored and managed off-heap, 
completely removing any type of Garbage
-Collection overhead.
+In addition to key-value API, Ignite data grid 
has complete SQL support, including primary
+and secondary indexes and distributed JOINs.
 
 
-https://apacheignite.readme.io/docs/durable-memory; target="docs">Docs 
for this Feature 
+https://apacheignite.readme.io/docs/sql-queries; target="docs">Docs for 
this Feature 
 
 
 
 
-Native Persistence
+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
-persistence layer, storing data and indexes on 
SSD, Flash, 3D XPoint, or any other
-types of storages.
+Ignite Durable Memory allows 
storing and processing data and indexes
+both, in memory and on disk. The in-memory 
data, including indexes, is always
+stored and managed off-heap, 
completely removing any type of Garbage
+Collection overhead.
 
 
-https://apacheignite.readme.io/docs/distributed-persistent-store; 
target="docs">Docs for this Feature 
+https://apacheignite.readme.io/docs/durable-memory; target="docs">Docs 
for this Feature 
 
 
 
@@ -317,13 +315,13 @@ under the License.
 
 
 Some of the JCache API features include:
-
-Basic Cache Operations
-ConcurrentMap APIs
-Collocated Processing 
(EntryProcessor)
-Events and Metrics
-Pluggable Persistence
-
+
+Basic Cache Operations
+ConcurrentMap APIs
+Collocated Processing (EntryProcessor)
+Events and Metrics
+Pluggable Persistence
+
 
 
 http://apacheignite.readme.io/docs/jcache; target="docs">Docs for this 
Feature 
@@ -454,6 +452,20 @@ under the License.
 
 
 
+
+Native Persistence
+
+
+Ignite Native Persistence is a 
distributed ACID and SQL-compliant disk
+store that transparently integrates with 
Ignite's Durable Memory as an optional
+persistence layer, storing data and indexes on 
SSD, Flash, 3D XPoint, or any other
+types of storages.
+
+
+https://apacheignite.readme.io/docs/d

svn commit: r1808300 - in /ignite/site/trunk: features/datagrid.html whatisignite.html

[dsetrakyan]

Author: dsetrakyan
Date: Thu Sep 14 02:12:41 2017
New Revision: 1808300

URL: http://svn.apache.org/viewvc?rev=1808300=rev
Log:
updated data grid page.

Modified:
ignite/site/trunk/features/datagrid.html
ignite/site/trunk/whatisignite.html

Modified: ignite/site/trunk/features/datagrid.html
URL: 
http://svn.apache.org/viewvc/ignite/site/trunk/features/datagrid.html?rev=1808300=1808299=1808300=diff
==
--- ignite/site/trunk/features/datagrid.html (original)
+++ ignite/site/trunk/features/datagrid.html Thu Sep 14 02:12:41 2017
@@ -39,10 +39,11 @@ under the License.
 
 
 
+
 In-Memory Data Grid - Apache Ignite
-
-https://netdna.bootstrapcdn.com/font-awesome/4.2.0/css/font-awesome.css; 
rel="stylesheet">
-
+
+https://netdna.bootstrapcdn.com/font-awesome/4.2.0/css/font-awesome.css; 
rel="stylesheet"/>
+
 
 
 
@@ -56,9 +57,9 @@ under the License.
 
 
 
-Ignite Data Grid is a distributed key-value store that
-enables storing data both in memory and on disk within 
distributed clusters and provides extensive
-key-value APIs. Ignite Data Grid can be viewed as a 
distributed partitioned hash map with every
+Ignite Data Grid is a distributed, transactional 
key-value store. Unlike other
+in-memory data grids (IMDG), Ignite enables storing 
data both, in memory and on disk.
+Ignite Data Grid 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.
 
@@ -71,12 +72,21 @@ under the License.
 atomic data in distributed clusters today. We know it 
because we constantly benchmark it ourselves.
 
 
-Data along with indexes can be persisted in 
-Ignite Native Persistence or in a 3rd party 
database such as RDBMS, NoSQL or Hadoop. If a
-3rd party database is used then Ignite can 
significantly accelerate performance by storing
-a full copy of data in memory.
-https://apacheignite.readme.io/docs/distributed-persistent-store; 
target="_blank">Learn more
-when to use one type of persistence over another.
+The data in the data grid can be stored only in 
memory, or can also be persisted to disk.
+If Ignite native persistence is enabled,
+then data and indexes will be persisted natively by 
Ignite on every cluster node. In this case,
+memory only serves as a smaller caching layer of the 
overall persisted data set. All queries and transactions
+span the whole data set stored on disk.
+
+
+The in-memory data grid can also improve performance 
and scalability by integrating with existing 3rd party
+databases, like RDBMS, NoSQL, or Hadoop-based 
storages. This approach does not require
+rip-and-replace of the existing data, but has its 
limitations. For example, SQL or scan queries will only include the
+results stored in memory, and not in the external 
database, since Ignite does not have any knowledge of the external data.
+
+
+https://apacheignite.readme.io/docs/distributed-persistent-store; 
target="_blank">Read more
+about different types of persistence in Ignite.
 
 
 
@@ -255,9 +265,10 @@ under the License.
 Key-Value Store
 
 
-Ignite data grid is an in-memory 
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.
+Ignite data grid is a key-value 
store which can store data both, in-memory
+and on-disk. It 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 store.
 
 

svn commit: r1808286 - /ignite/site/trunk/whatisignite.html

[dsetrakyan]

Author: dsetrakyan
Date: Wed Sep 13 20:51:33 2017
New Revision: 1808286

URL: http://svn.apache.org/viewvc?rev=1808286=rev
Log:
updated what is ignite v.2

Modified:
ignite/site/trunk/whatisignite.html

Modified: ignite/site/trunk/whatisignite.html
URL: 
http://svn.apache.org/viewvc/ignite/site/trunk/whatisignite.html?rev=1808286=1808285=1808286=diff
==
--- ignite/site/trunk/whatisignite.html (original)
+++ ignite/site/trunk/whatisignite.html Wed Sep 13 20:51:33 2017
@@ -118,6 +118,14 @@ under the License.
 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 users
+to store smaller operational data sets in-memory only, and 
larger data sets on disk, using memory as
+a caching layer for better performance.
+
+
+
 Is Ignite an in-memory database (IMDB)?
 
 Yes. Even though Ignite durable memory 
works well in-memory and on-disk, the disk
@@ -134,14 +142,6 @@ under the License.
 
 
 
-Is Ignite a persistent or pure in-memory storage?
-
-Both. Native persistence in Ignite can be 
turned on and off. This allows Ignite users
-to store smaller operational data sets in-memory only, and 
larger data sets on disk, using memory as
-a caching layer for better performance.
-
-
-
 Is Ignite a distributed database?
 
 Yes. Data in Ignite is either partitioned 
or replicated across a cluster of

svn commit: r1808198 - /ignite/site/trunk/whatisignite-2.html

[dsetrakyan]

Author: dsetrakyan
Date: Wed Sep 13 01:31:37 2017
New Revision: 1808198

URL: http://svn.apache.org/viewvc?rev=1808198=rev
Log:
updated what is ignite v.2

Modified:
ignite/site/trunk/whatisignite-2.html

Modified: ignite/site/trunk/whatisignite-2.html
URL: 
http://svn.apache.org/viewvc/ignite/site/trunk/whatisignite-2.html?rev=1808198=1808197=1808198=diff
==
--- ignite/site/trunk/whatisignite-2.html (original)
+++ ignite/site/trunk/whatisignite-2.html Wed Sep 13 01:31:37 2017
@@ -40,7 +40,7 @@ under the License.
 
 
 What is Apache Ignite
-
+
 
 https://netdna.bootstrapcdn.com/font-awesome/4.2.0/css/font-awesome.css; 
rel="stylesheet">
 
@@ -95,8 +95,8 @@ under the License.
 
 Key-Value
 
-Ignite's data grid component is an in-memory 
distributed key-value store that that can be viewed as a
-distributed partitioned hash map with every cluster node 
owning a portion of the overall data. Ignite data grid can linearly scale to 
hundreds of node.
+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.
 
 
 Collocated Processing

svn commit: r1808193 - /ignite/site/trunk/whatisignite-2.html

[dsetrakyan]

Author: dsetrakyan
Date: Wed Sep 13 01:15:55 2017
New Revision: 1808193

URL: http://svn.apache.org/viewvc?rev=1808193=rev
Log:
updated what is ignite v.2

Modified:
ignite/site/trunk/whatisignite-2.html

Modified: ignite/site/trunk/whatisignite-2.html
URL: 
http://svn.apache.org/viewvc/ignite/site/trunk/whatisignite-2.html?rev=1808193=1808192=1808193=diff
==
--- ignite/site/trunk/whatisignite-2.html (original)
+++ ignite/site/trunk/whatisignite-2.html Wed Sep 13 01:15:55 2017
@@ -126,7 +126,7 @@ under the License.
 Is Ignite an in-memory database (IMDB)?
 
 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 
distributed in-memory database, with strong
+persistence can be disabled and Ignite can act as a pure 
distributed in-memory database, with
 support for SQL and distributed joins.
 
 
@@ -175,11 +175,10 @@ under the License.
 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.3.
+to implement SQL transactions in version 2.4.
 
 
 

svn commit: r1808192 - /ignite/site/trunk/whatisignite-2.html

[dsetrakyan]

Author: dsetrakyan
Date: Wed Sep 13 01:08:03 2017
New Revision: 1808192

URL: http://svn.apache.org/viewvc?rev=1808192=rev
Log:
updated what is ignite v.2

Modified:
ignite/site/trunk/whatisignite-2.html

Modified: ignite/site/trunk/whatisignite-2.html
URL: 
http://svn.apache.org/viewvc/ignite/site/trunk/whatisignite-2.html?rev=1808192=1808191=1808192=diff
==
--- ignite/site/trunk/whatisignite-2.html (original)
+++ ignite/site/trunk/whatisignite-2.html Wed Sep 13 01:08:03 2017
@@ -40,7 +40,7 @@ under the License.
 
 
 What is Apache Ignite
-
+
 
 https://netdna.bootstrapcdn.com/font-awesome/4.2.0/css/font-awesome.css; 
rel="stylesheet">
 
@@ -71,38 +71,39 @@ under the License.
 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, like always,
-can act as a distributed in-memory 
database or as an 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 data consistency and is
+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 data consistency and is
 resilient to full cluster failures.
 
 
 
 Complete SQL Support
 
-In addition to SQL querying, Ignite provides support for 
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.
+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.
 
 
 
 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. This makes Ignite stand out from the eventually c
-onsistent NoSQL systems that hardly support any type of 
transactions.
+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.
 
 
 Key-Value
 
-Ignite's data grid component is an in-memory 
distributed key-value store that that can be viewed as a
+Ignite's data grid component is an in-memory 
distributed key-value store that that can be viewed as a
 distributed partitioned hash map with every cluster node 
owning a portion of the overall data. Ignite data grid can linearly scale to 
hundreds of node.
 
 
 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 computations to the data, moving only the lightweight compute functions 
across the network.
-As a result, Ignite scales better and minimizes data 
movement. When collocated, all the data processing 
happens locally on the node that stores the data, and only the result is 
brought back to the user.
+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 a

svn commit: r1805995 - in /ignite/site/trunk: index.html whatisignite.html

[dsetrakyan]

Author: dsetrakyan
Date: Thu Aug 24 05:21:56 2017
New Revision: 1805995

URL: http://svn.apache.org/viewvc?rev=1805995=rev
Log:
product message update.

Modified:
ignite/site/trunk/index.html
ignite/site/trunk/whatisignite.html

Modified: ignite/site/trunk/index.html
URL: 
http://svn.apache.org/viewvc/ignite/site/trunk/index.html?rev=1805995=1805994=1805995=diff
==
Binary files - no diff available.

Modified: ignite/site/trunk/whatisignite.html
URL: 
http://svn.apache.org/viewvc/ignite/site/trunk/whatisignite.html?rev=1805995=1805994=1805995=diff
==
--- ignite/site/trunk/whatisignite.html (original)
+++ ignite/site/trunk/whatisignite.html Thu Aug 24 05:21:56 2017
@@ -52,11 +52,11 @@ under the License.
 
 
 
-WHAT IS IGNITE?
+What is Ignite?
 
 
 
-A memory-centric data 
platform
+the in-memory computing 
platform
 that is strongly 
consistent
 and highly available
 with powerful SQL,

svn commit: r1805601 - /ignite/site/trunk/whatisignite.html

[dsetrakyan]

Author: dsetrakyan
Date: Mon Aug 21 05:44:27 2017
New Revision: 1805601

URL: http://svn.apache.org/viewvc?rev=1805601=rev
Log:
Tuned the message a bit.

Modified:
ignite/site/trunk/whatisignite.html

Modified: ignite/site/trunk/whatisignite.html
URL: 
http://svn.apache.org/viewvc/ignite/site/trunk/whatisignite.html?rev=1805601=1805600=1805601=diff
==
--- ignite/site/trunk/whatisignite.html (original)
+++ ignite/site/trunk/whatisignite.html Mon Aug 21 05:44:27 2017
@@ -72,7 +72,7 @@ under the License.
 Is Ignite an in-memory database (IMDB)?
 
 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, with strong
+persistence can be disabled and Ignite can act as a pure 
distributed in-memory database, with strong
 support for SQL and distributed joins.
 
 https://apacheignite.readme.io/v2.1/docs/distributed-sql;>

svn commit: r1805599 - /ignite/site/trunk/whatisignite.html

[dsetrakyan]

Author: dsetrakyan
Date: Mon Aug 21 05:37:52 2017
New Revision: 1805599

URL: http://svn.apache.org/viewvc?rev=1805599=rev
Log:
Tuned the message a bit.

Modified:
ignite/site/trunk/whatisignite.html

Modified: ignite/site/trunk/whatisignite.html
URL: 
http://svn.apache.org/viewvc/ignite/site/trunk/whatisignite.html?rev=1805599=1805598=1805599=diff
==
--- ignite/site/trunk/whatisignite.html (original)
+++ ignite/site/trunk/whatisignite.html Mon Aug 21 05:37:52 2017
@@ -69,71 +69,63 @@ under the License.
 
 
 
-Is Ignite a distributed database?
+Is Ignite an in-memory database (IMDB)?
 
-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 plugin their own distribution (affinity) 
functions and collocate various pieces of data together for efficiency.
+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, with strong
+support for SQL and distributed joins.
 
 https://apacheignite.readme.io/v2.1/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 Ignite an in-memory data grid (IMDG)?
 
-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.
+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 databases,
+including any RDBMS or NoSQL stores.
 
-https://apacheignite.readme.io/v2.1/docs/indexes;>
+https://apacheignite.readme.io/v2.1/docs/data-grid;>
 
-Is Ignite an in-memory database?
+Is Ignite a distributed 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.
+Yes. Data in Ignite is either partitioned or 
replicated across a cluster of
+multiple nodes. This provides scalability and adds resiliency 
to the system. Ignite automatically
+controls how data is partitioned, however, users can plugin 
their own distribution (affinity) functions
+and collocate various pieces of data together for efficiency.
 
 https://apacheignite.readme.io/v2.1/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 Ignite an SQL database?
 
-At SQL level Ignite supports atomic, but not yet transactional 
consistency. Ignite community plans to implement SQL transactions in version 
2.2.
+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.
 
-https://apacheignite.readme.io/v2.1/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.
+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.
 
-https://apacheignite.readme.io/v2.1

svn commit: r1755384 - /ignite/site/trunk/download.html

[dsetrakyan]

Author: dsetrakyan
Date: Sat Aug  6 03:03:28 2016
New Revision: 1755384

URL: http://svn.apache.org/viewvc?rev=1755384=rev
Log:
Updated release dates.

Modified:
ignite/site/trunk/download.html

Modified: ignite/site/trunk/download.html
URL: 
http://svn.apache.org/viewvc/ignite/site/trunk/download.html?rev=1755384=1755383=1755384=diff
==
--- ignite/site/trunk/download.html (original)
+++ ignite/site/trunk/download.html Sat Aug  6 03:03:28 2016
@@ -496,7 +496,7 @@ under the License.
 https://ignite.apache.org/releases/1.7.0/javadoc/;>javadoc,
 https://ignite.apache.org/releases/1.7.0/scaladoc/scalar/;>scaladoc
 
-2016-05-23
+2016-08-05
 
 
 https://apacheignite.readme.io/v1.7/docs/hadoop-accelerator;>guide
 
-2016-05-23
+2016-08-05
 
 

svn commit: r1755229 - in /ignite/site/trunk/features: cpp.html dotnet.html java.html

[dsetrakyan]

Author: dsetrakyan
Date: Thu Aug  4 20:03:47 2016
New Revision: 1755229

URL: http://svn.apache.org/viewvc?rev=1755229=rev
Log:
platform pages.

Added:
ignite/site/trunk/features/cpp.html   (with props)
ignite/site/trunk/features/dotnet.html   (with props)
ignite/site/trunk/features/java.html   (with props)

Added: ignite/site/trunk/features/cpp.html
URL: 
http://svn.apache.org/viewvc/ignite/site/trunk/features/cpp.html?rev=1755229=auto
==
Binary file - no diff available.

Propchange: ignite/site/trunk/features/cpp.html
--
svn:mime-type = application/octet-stream

Added: ignite/site/trunk/features/dotnet.html
URL: 
http://svn.apache.org/viewvc/ignite/site/trunk/features/dotnet.html?rev=1755229=auto
==
Binary file - no diff available.

Propchange: ignite/site/trunk/features/dotnet.html
--
svn:mime-type = application/octet-stream

Added: ignite/site/trunk/features/java.html
URL: 
http://svn.apache.org/viewvc/ignite/site/trunk/features/java.html?rev=1755229=auto
==
Binary file - no diff available.

Propchange: ignite/site/trunk/features/java.html
--
svn:mime-type = application/octet-stream

svn commit: r1755128 - in /ignite/site/trunk: css/all.css download.html includes/header.html includes/sh.html scss/ignite.scss

[dsetrakyan]

Author: dsetrakyan
Date: Thu Aug  4 00:07:35 2016
New Revision: 1755128

URL: http://svn.apache.org/viewvc?rev=1755128=rev
Log:
Added cross-platform pages.

Modified:
ignite/site/trunk/css/all.css
ignite/site/trunk/download.html
ignite/site/trunk/includes/header.html
ignite/site/trunk/includes/sh.html
ignite/site/trunk/scss/ignite.scss

Modified: ignite/site/trunk/css/all.css
URL: 
http://svn.apache.org/viewvc/ignite/site/trunk/css/all.css?rev=1755128=1755127=1755128=diff
==
--- ignite/site/trunk/css/all.css (original)
+++ ignite/site/trunk/css/all.css Thu Aug  4 00:07:35 2016
@@ -8358,6 +8358,12 @@ tr.sub-heading > th {
   }
 }
 
+.github-image {
+  font-size: 1.7em !important;
+  position: relative;
+  top: -5px;
+}
+
 .btn-transparent {
   color: #fff;
   background-color: transparent;

Modified: ignite/site/trunk/download.html
URL: 
http://svn.apache.org/viewvc/ignite/site/trunk/download.html?rev=1755128=1755127=1755128=diff
==
--- ignite/site/trunk/download.html (original)
+++ ignite/site/trunk/download.html Thu Aug  4 00:07:35 2016
@@ -105,6 +105,11 @@ under the License.
 Runs Everywhere
 Client Protocols
 Deployment Options
+
+Cross Platform
+Java
+.NET
+C++
 
 
 
@@ -223,8 +228,8 @@ under the License.
 [define disturl]https://www.apache.org/dist[end]
 
 
-
-
+
+
 Downloads
 
 Source Releases
@@ -238,6 +243,7 @@ under the License.
 
 
 
+
 http://svn.apache.org/viewvc/ignite/site/trunk/includes/header.html?rev=1755128=1755127=1755128=diff
==
--- ignite/site/trunk/includes/header.html (original)
+++ ignite/site/trunk/includes/header.html Thu Aug  4 00:07:35 2016
@@ -37,6 +37,11 @@
 Runs Everywhere
 Client Protocols
 Deployment Options
+
+Cross Platform
+Java
+.NET
+C++
 
 
 

Modified: ignite/site/trunk/includes/sh.html
URL: 
http://svn.apache.org/viewvc/ignite/site/trunk/includes/sh.html?rev=1755128=1755127=1755128=diff
==
--- ignite/site/trunk/includes/sh.html (original)
+++ ignite/site/trunk/includes/sh.html Thu Aug  4 00:07:35 2016
@@ -5,6 +5,8 @@
 
 
 
+
+
 
 
 

Modified: ignite/site/trunk/scss/ignite.scss
URL: 
http://svn.apache.org/viewvc/ignite/site/trunk/scss/ignite.scss?rev=1755128=1755127=1755128=diff
==
--- ignite/site/trunk/scss/ignite.scss (original)
+++ ignite/site/trunk/scss/ignite.scss Thu Aug  4 00:07:35 2016
@@ -850,3 +850,9 @@ tr.sub-heading {
 margin-top: 17px;
 }
 }
+
+.github-image {
+font-size: 1.7em !important;
+position: relative;
+top: -5px;
+}

svn commit: r1755014 - in /ignite/site/trunk/images: cpp.png dotnet.png java.png

[dsetrakyan]

Author: dsetrakyan
Date: Wed Aug  3 01:05:15 2016
New Revision: 1755014

URL: http://svn.apache.org/viewvc?rev=1755014=rev
Log:
new images

Added:
ignite/site/trunk/images/cpp.png   (with props)
ignite/site/trunk/images/dotnet.png   (with props)
ignite/site/trunk/images/java.png   (with props)

Added: ignite/site/trunk/images/cpp.png
URL: 
http://svn.apache.org/viewvc/ignite/site/trunk/images/cpp.png?rev=1755014=auto
==
Binary file - no diff available.

Propchange: ignite/site/trunk/images/cpp.png
--
svn:mime-type = application/octet-stream

Added: ignite/site/trunk/images/dotnet.png
URL: 
http://svn.apache.org/viewvc/ignite/site/trunk/images/dotnet.png?rev=1755014=auto
==
Binary file - no diff available.

Propchange: ignite/site/trunk/images/dotnet.png
--
svn:mime-type = application/octet-stream

Added: ignite/site/trunk/images/java.png
URL: 
http://svn.apache.org/viewvc/ignite/site/trunk/images/java.png?rev=1755014=auto
==
Binary file - no diff available.

Propchange: ignite/site/trunk/images/java.png
--
svn:mime-type = application/octet-stream

svn commit: r1754809 - in /ignite/site/trunk: css/all.css download.html includes/header.html index.html scss/ignite.scss

[dsetrakyan]

Author: dsetrakyan
Date: Tue Aug  2 02:08:11 2016
New Revision: 1754809

URL: http://svn.apache.org/viewvc?rev=1754809=rev
Log:
Updated download page.

Modified:
ignite/site/trunk/css/all.css
ignite/site/trunk/download.html
ignite/site/trunk/includes/header.html
ignite/site/trunk/index.html
ignite/site/trunk/scss/ignite.scss

Modified: ignite/site/trunk/css/all.css
URL: 
http://svn.apache.org/viewvc/ignite/site/trunk/css/all.css?rev=1754809=1754808=1754809=diff
==
--- ignite/site/trunk/css/all.css (original)
+++ ignite/site/trunk/css/all.css Tue Aug  2 02:08:11 2016
@@ -8347,11 +8347,16 @@ tr.sub-heading > th {
   padding: 14px 16px;
 }
 
-.gstat {
+.github-stat {
   width: 120px;
   height: 30px;
   border: none;
 }
+@media (max-width: 767px) {
+  .github-stat {
+margin-top: 17px;
+  }
+}
 
 .btn-transparent {
   color: #fff;

Modified: ignite/site/trunk/download.html
URL: 
http://svn.apache.org/viewvc/ignite/site/trunk/download.html?rev=1754809=1754808=1754809=diff
==
--- ignite/site/trunk/download.html (original)
+++ ignite/site/trunk/download.html Tue Aug  2 02:08:11 2016
@@ -200,6 +200,8 @@ under the License.
 
 Build from Source
 
+Git Repository
+
 3rd Party Binaries
 
 
@@ -221,24 +223,44 @@ under the License.
 [define disturl]https://www.apache.org/dist[end]
 
 
-Downloads
-
-Source Releases
-Binary Releases
-Docker and Cloud Images
-Download from Maven
-Build from Source
-3rd Party Binaries
-
+
+
+Downloads
+
+Source Releases
+Binary Releases
+Docker and Cloud Images
+Download from Maven
+Build from Source
+Git Repository
+3rd Party 
Binaries
+
+
+
+
+https://buttons.github.io/buttons.html#href=https%3A%2F%2Fgithub.com%2Fapache%2Fignite=Star=%2Frepos%2Fapache%2Fignite%23stargazers_count=%2Fapache%2Fignite%2Fstargazers=%23%20stargazers%20on%20GitHub=mega=octicon-star=Star%20apache%2Fignite%20on%20GitHub;>
+
+https://buttons.github.io/buttons.html#href=https%3A%2F%2Fgithub.com%2Fapache%2Fignite%2Ffork=Fork=%2Frepos%2Fapache%2Fignite%23forks_count=%2Fapache%2Fignite%2Fnetwork=%23%20forks%20on%20GitHub=mega=octicon-repo-forked=Fork%20apache%2Fignite%20on%20GitHub;>
+
+https://buttons.github.io/buttons.html#href=https%3A%2F%2Fgithub.com%2Fapache%2Fignite=Watch=%2Frepos%2Fapache%2Fignite%23subscribers_count=%2Fapache%2Fignite%2Fwatchers=%23%20watchers%20on%20GitHub=mega=octicon-eye=Watch%20apache%2Fignite%20on%20GitHub;>
+
+
+
+
 
-Downloads contain
-
-startup scripts
-default configuration
-examples for all major components
-libraries (required and optional, without LGPL)
-to get LGPL dependencies (e.g. Hibernate L2 Cache), see Building The Binaries.
-
+* To get LGPL dependencies (e.g. Hibernate L2 Cache), see Building The Binaries.
 
 
 
@@ -848,11 +870,13 @@ under the License.
# (optionally specify version of hadoop to use)
$ mvn clean package -DskipTests -Dignite.edition=hadoop 
[-Dhadoop.version=X.X.X]
 
-GIT repository:
+
+
+GIT Repository
 
$ git clone https://git-wip-us.apache.org/repos/asf/ignite
 
-
+
 
 
 3rd Party Binaries

Modified: ignite/site/trunk/includes/header.html
URL: 
http://svn.apache.org/viewvc/ignite/site/trunk/includes/header.html?rev=1754809=1754808=1754809=diff
==
--- ignite/site/trunk/includes/header.html (original)
+++ ignite/site/trunk/includes/header.html Tue Aug  2 02:08:11 2016
@@ -133,6 +133,8 @@
 
 Build from Source
 
+Git Repository
+
 3rd Party Binaries
 
 

Modified: ignite/site/trunk/in

svn commit: r1753724 - in /ignite/site/trunk: community/contribute.html css/all.css index.html scss/ignite.scss

[dsetrakyan]

Author: dsetrakyan
Date: Thu Jul 21 18:55:17 2016
New Revision: 1753724

URL: http://svn.apache.org/viewvc?rev=1753724=rev
Log:
Added GitHub stats to the home page.

Modified:
ignite/site/trunk/community/contribute.html
ignite/site/trunk/css/all.css
ignite/site/trunk/index.html
ignite/site/trunk/scss/ignite.scss

Modified: ignite/site/trunk/community/contribute.html
URL: 
http://svn.apache.org/viewvc/ignite/site/trunk/community/contribute.html?rev=1753724=1753723=1753724=diff
==
--- ignite/site/trunk/community/contribute.html (original)
+++ ignite/site/trunk/community/contribute.html Thu Jul 21 18:55:17 2016
@@ -85,6 +85,10 @@ under the License.
 
 One of the committers will add you to the contributor list 
and assign the ticket to you.
 
+
+Visit our https://cwiki.apache.org/confluence/display/IGNITE/How+to+Contribute;>How 
to Contribute page for details about the project workflow and JIRA process.
+
+
 
 
 

Modified: ignite/site/trunk/css/all.css
URL: 
http://svn.apache.org/viewvc/ignite/site/trunk/css/all.css?rev=1753724=1753723=1753724=diff
==
--- ignite/site/trunk/css/all.css (original)
+++ ignite/site/trunk/css/all.css Thu Jul 21 18:55:17 2016
@@ -8332,6 +8332,27 @@ tr.sub-heading > th {
   width: 35%;
 }
 
+.btn-download {
+  color: #fff;
+  background-color: #c51017;
+  border-color: #ad0e14;
+}
+.btn-download:hover {
+  color: #fff;
+  background-color: #960c11;
+  border-color: #960c11;
+}
+
+.btn-lg, .btn-group-lg > .btn {
+  padding: 14px 16px;
+}
+
+.gstat {
+  width: 120px;
+  height: 30px;
+  border: none;
+}
+
 .btn-transparent {
   color: #fff;
   background-color: transparent;

Modified: ignite/site/trunk/index.html
URL: 
http://svn.apache.org/viewvc/ignite/site/trunk/index.html?rev=1753724=1753723=1753724=diff
==
--- ignite/site/trunk/index.html (original)
+++ ignite/site/trunk/index.html Thu Jul 21 18:55:17 2016
@@ -110,7 +110,31 @@ under the License.
 Apache Ignite In-Memory Data Fabric is designed to 
deliver
 uncompromised performance for a wide set of in-memory 
computing
 use cases from high 
performance computing, to the industry most advanced data grid, highly available service grid, and streaming.
-
+
+
+
+
+Download Ignite
+
+https://buttons.github.io/buttons.html#href=https%3A%2F%2Fgithub.com%2Fapache%2Fignite=Star=%2Frepos%2Fapache%2Fignite%23stargazers_count=%2Fapache%2Fignite%2Fstargazers=%23%20stargazers%20on%20GitHub=mega=octicon-star=Star%20apache%2Fignite%20on%20GitHub;>
+
+https://buttons.github.io/buttons.html#href=https%3A%2F%2Fgithub.com%2Fapache%2Fignite%2Ffork=Fork=%2Frepos%2Fapache%2Fignite%23forks_count=%2Fapache%2Fignite%2Fnetwork=%23%20forks%20on%20GitHub=mega=octicon-repo-forked=Fork%20apache%2Fignite%20on%20GitHub;>
+
+https://buttons.github.io/buttons.html#href=https%3A%2F%2Fgithub.com%2Fapache%2Fignite=Watch=%2Frepos%2Fapache%2Fignite%23subscribers_count=%2Fapache%2Fignite%2Fwatchers=%23%20watchers%20on%20GitHub=mega=octicon-eye=Watch%20apache%2Fignite%20on%20GitHub;>
+
+
 
 
 Latest News

Modified: ignite/site/trunk/scss/ignite.scss
URL: 
http://svn.apache.org/viewvc/ignite/site/trunk/scss/ignite.scss?rev=1753724=1753723=1753724=diff
==
--- ignite/site/trunk/scss/ignite.scss (original)
+++ ignite/site/trunk/scss/ignite.scss Thu Jul 21 18:55:17 2016
@@ -823,3 +823,26 @@ tr.sub-heading {
 font-weight: bold;
 width :35%;
 }
+
+.btn-download {
+color: #fff;
+background-color: #c51017;
+border-color: #ad0e14;
+
+&:hover {
+color: #fff;
+background-color: #960c11;
+border-color: #960c11;
+}
+
+ }
+
+.btn-lg {
+padding: 14px 16px;
+}
+
+.gstat {
+width: 120px;
+height: 30px;
+border: none;
+}

ignite git commit: Updated dependencies

[dsetrakyan]

Repository: ignite
Updated Branches:
  refs/heads/master 34a957cf6 -> 4f038c158


Updated dependencies


Project: http://git-wip-us.apache.org/repos/asf/ignite/repo
Commit: http://git-wip-us.apache.org/repos/asf/ignite/commit/4f038c15
Tree: http://git-wip-us.apache.org/repos/asf/ignite/tree/4f038c15
Diff: http://git-wip-us.apache.org/repos/asf/ignite/diff/4f038c15

Branch: refs/heads/master
Commit: 4f038c1586990bb550a0cd2f4156b46d359a9c8f
Parents: 34a957c
Author: Dmitiry Setrakyan 
Authored: Sat Jul 16 01:38:56 2016 +0300
Committer: Dmitiry Setrakyan 
Committed: Sat Jul 16 01:38:56 2016 +0300

--
 assembly/libs/README.txt | 39 +--
 1 file changed, 29 insertions(+), 10 deletions(-)
--


http://git-wip-us.apache.org/repos/asf/ignite/blob/4f038c15/assembly/libs/README.txt
--
diff --git a/assembly/libs/README.txt b/assembly/libs/README.txt
index 38d8dbd..9902e8c 100644
--- a/assembly/libs/README.txt
+++ b/assembly/libs/README.txt
@@ -71,24 +71,43 @@ Here is how it can be imported into your POM file:
 All optional modules can be imported just like the core module, but with 
different artifact IDs.
 
 The following modules are available:
-- ignite-spring (for Spring-based configuration support)
-- ignite-indexing (for SQL querying and indexing)
+- ignite-aop (for AOP-based grid-enabling)
+- ignite-aws (for seemless cluster discovery on AWS S3)
+- 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-gce (for automatic cluster discovery on Google Compute Engine)
+- ignite-hadoop (for Apache Hadoop Accelerator)
 - ignite-hibernate (for Hibernate integration)
-- ignite-web (for Web Sessions Clustering)
-- ignite-schedule (for Cron-based task scheduling)
-- ignite-logj4 (for Log4j logging)
+- 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-jta (for XA integration)
-- ignite-hadoop (for Apache Hadoop Accelerator)
+- ignite-kafka (for streaming messages from Apache Kafka into Ignite)
+- 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-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-scalar (for ignite Scala API)
+- ignite-scalar_2.10 (for Ignite 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-spark_2.10 (for shared in-memory RDDs and faster SQL for Apache Spark 
with Scala 2.10)
+- 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-urideploy (for URI-based deployment)
-- ignite-aws (for seemless cluster discovery on AWS S3)
-- ignite-email (for email alerts)
-- ignite-aop (for AOP-based grid-enabling)
-- ignite-visor-console (open source command line management and monitoring 
tool)
+- 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,
 you should add 'ignite-spring' module like this:

svn commit: r1751731 - /ignite/site/trunk/images/monitoring.png

[dsetrakyan]

Author: dsetrakyan
Date: Wed Jul  6 21:01:57 2016
New Revision: 1751731

URL: http://svn.apache.org/viewvc?rev=1751731=rev
Log:
changed monitoring image

Added:
ignite/site/trunk/images/monitoring.png   (with props)

Added: ignite/site/trunk/images/monitoring.png
URL: 
http://svn.apache.org/viewvc/ignite/site/trunk/images/monitoring.png?rev=1751731=auto
==
Binary file - no diff available.

Propchange: ignite/site/trunk/images/monitoring.png
--
svn:mime-type = application/octet-stream

svn commit: r1751730 - /ignite/site/trunk/addons.html

[dsetrakyan]

Author: dsetrakyan
Date: Wed Jul  6 21:01:41 2016
New Revision: 1751730

URL: http://svn.apache.org/viewvc?rev=1751730=rev
Log:
changed monitoring image

Modified:
ignite/site/trunk/addons.html

Modified: ignite/site/trunk/addons.html
URL: 
http://svn.apache.org/viewvc/ignite/site/trunk/addons.html?rev=1751730=1751729=1751730=diff
==
--- ignite/site/trunk/addons.html (original)
+++ ignite/site/trunk/addons.html Wed Jul  6 21:01:41 2016
@@ -38,7 +38,7 @@ under the License.
 
 
 
-Apache Ignite - Add-ons
+Apache Ignite - Manage
 
 https://netdna.bootstrapcdn.com/font-awesome/4.2.0/css/font-awesome.css; 
rel="stylesheet">
 
@@ -76,7 +76,7 @@ under the License.
 
 
 
-
+
 Click on the image to view full 
size.
 
 
@@ -104,8 +104,8 @@ under the License.
 https://console.gridgain.com; 
target="_blank">GridGain Web Console 
 
 
-
-
+
+
 Click on the image to view full 
size.
 
 

svn commit: r1751577 - in /ignite/site/trunk: download.html includes/header.html

[dsetrakyan]

Author: dsetrakyan
Date: Wed Jul  6 00:04:21 2016
New Revision: 1751577

URL: http://svn.apache.org/viewvc?rev=1751577=rev
Log:
Moved manage meny

Modified:
ignite/site/trunk/download.html
ignite/site/trunk/includes/header.html

Modified: ignite/site/trunk/download.html
URL: 
http://svn.apache.org/viewvc/ignite/site/trunk/download.html?rev=1751577=1751576=1751577=diff
==
--- ignite/site/trunk/download.html (original)
+++ ignite/site/trunk/download.html Wed Jul  6 00:04:21 2016
@@ -125,13 +125,6 @@ under the License.
 
 
 
-Manage
-
-Apache 
Ignite Extensions
-GridGain Web Console
-
-
-
 http://apacheignite.readme.io/docs; target="_blank">Docs
 
 Ignite
@@ -188,6 +181,13 @@ under the License.
 
 
 
+Manage
+
+Apache 
Ignite Extensions
+GridGain Web Console
+
+
+
 Download 
 
 Source Releases

Modified: ignite/site/trunk/includes/header.html
URL: 
http://svn.apache.org/viewvc/ignite/site/trunk/includes/header.html?rev=1751577=1751576=1751577=diff
==
--- ignite/site/trunk/includes/header.html (original)
+++ ignite/site/trunk/includes/header.html Wed Jul  6 00:04:21 2016
@@ -58,13 +58,6 @@
 
 
 
-Manage
-
-Apache 
Ignite Extensions
-GridGain Web Console
-
-
-
 http://apacheignite.readme.io/docs; target="_blank">Docs
 
 Ignite
@@ -121,6 +114,13 @@
 
 
 
+Manage
+
+Apache 
Ignite Extensions
+GridGain Web Console
+
+
+
 Download
 
 Source Releases

svn commit: r1751575 - in /ignite/site/trunk: addons.html download.html includes/header.html

[dsetrakyan]

Author: dsetrakyan
Date: Tue Jul  5 23:41:19 2016
New Revision: 1751575

URL: http://svn.apache.org/viewvc?rev=1751575=rev
Log:
Updated add-ons page.

Modified:
ignite/site/trunk/addons.html
ignite/site/trunk/download.html
ignite/site/trunk/includes/header.html

Modified: ignite/site/trunk/addons.html
URL: 
http://svn.apache.org/viewvc/ignite/site/trunk/addons.html?rev=1751575=1751574=1751575=diff
==
--- ignite/site/trunk/addons.html (original)
+++ ignite/site/trunk/addons.html Tue Jul  5 23:41:19 2016
@@ -51,8 +51,8 @@ under the License.
 
 
 
-Add-ons
-Ignite add-ons are projects that intend to make user experience 
with Ignite easier. To contribute your add-on to Ignite, send an email to mailto:d...@ignite.apache.org;>dev list.
+Manage
+Ignite Manage are projects that intend to make user experience 
with Ignite easier. To contribute your project to Ignite, send an email to mailto:d...@ignite.apache.org;>dev list.
 
 
 
@@ -96,6 +96,8 @@ under the License.
 Create and download various configurations for 
Apache Ignite
 Automatically load SQL metadata from any RDBMS
 Connect to Ignite cluster and run SQL analytics on 
it
+Manage and Monitor Ignite nodes and caches
+View heap, CPU, and other useful node and cache 
metrics
 
 GridGain Web Console is a web application hosted by 
GridGain Systems.
 

Modified: ignite/site/trunk/download.html
URL: 
http://svn.apache.org/viewvc/ignite/site/trunk/download.html?rev=1751575=1751574=1751575=diff
==
--- ignite/site/trunk/download.html (original)
+++ ignite/site/trunk/download.html Tue Jul  5 23:41:19 2016
@@ -125,7 +125,7 @@ under the License.
 
 
 
-Add-ons
+Manage
 
 Apache 
Ignite Extensions
 GridGain Web Console

Modified: ignite/site/trunk/includes/header.html
URL: 
http://svn.apache.org/viewvc/ignite/site/trunk/includes/header.html?rev=1751575=1751574=1751575=diff
==
--- ignite/site/trunk/includes/header.html (original)
+++ ignite/site/trunk/includes/header.html Tue Jul  5 23:41:19 2016
@@ -58,7 +58,7 @@
 
 
 
-Add-ons
+Manage
 
 Apache 
Ignite Extensions
 GridGain Web Console

svn commit: r1750736 - in /ignite/site/trunk: download.html features/computegrid.html includes/header.html index.html

[dsetrakyan]

Author: dsetrakyan
Date: Thu Jun 30 02:44:40 2016
New Revision: 1750736

URL: http://svn.apache.org/viewvc?rev=1750736=rev
Log:
fixed links

Modified:
ignite/site/trunk/download.html
ignite/site/trunk/features/computegrid.html
ignite/site/trunk/includes/header.html
ignite/site/trunk/index.html

Modified: ignite/site/trunk/download.html
URL: 
http://svn.apache.org/viewvc/ignite/site/trunk/download.html?rev=1750736=1750735=1750736=diff
==
--- ignite/site/trunk/download.html (original)
+++ ignite/site/trunk/download.html Thu Jun 30 02:44:40 2016
@@ -151,6 +151,7 @@ under the License.
 https://ignite.apache.org/releases/1.6.0/javadoc; target="_blank">Javadoc 

 https://ignite.apache.org/releases/1.6.0/dotnetdoc; target="_blank">.NET 
API 
 https://ignite.apache.org/releases/1.6.0/cppdoc; target="_blank">C++ API 

+https://ignite.apache.org/releases/1.6.0/scaladoc/scalar; 
target="_blank">Scala API 
 https://github.com/apache/ignite/tree/master/examples; 
target="_blank">Examples 
 
 

Modified: ignite/site/trunk/features/computegrid.html
URL: 
http://svn.apache.org/viewvc/ignite/site/trunk/features/computegrid.html?rev=1750736=1750735=1750736=diff
==
--- ignite/site/trunk/features/computegrid.html (original)
+++ ignite/site/trunk/features/computegrid.html Thu Jun 30 02:44:40 2016
@@ -157,7 +157,7 @@ under the License.
 or a cluster group, including Java 8 lambdas, 
as well as plain Java runnables and callables.
 
 
-http://apacheignite.readme.io/docs/distributed-closures; 
target="docs">Docs for this Feature 
+http://apacheignite.readme.io/docs/distributed-closures; 
target="docs">Docs for this Feature 
 
 
 

Modified: ignite/site/trunk/includes/header.html
URL: 
http://svn.apache.org/viewvc/ignite/site/trunk/includes/header.html?rev=1750736=1750735=1750736=diff
==
--- ignite/site/trunk/includes/header.html (original)
+++ ignite/site/trunk/includes/header.html Thu Jun 30 02:44:40 2016
@@ -81,10 +81,10 @@
 https://apacheignite-fs.readme.io/docs; target="_blank">English 
 
 Code
-https://ignite.apache.org/releases/1.5.0.final/javadoc; 
target="_blank">Javadoc 
-https://ignite.apache.org/releases/1.5.0.final/dotnetdoc; 
target="_blank">.NET API 
-https://ignite.apache.org/releases/1.5.0.final/cppdoc; 
target="_blank">C++ API 
-   
https://ignite.apache.org/releases/1.5.0.final/scaladoc/scalar; 
target="_blank">Scala API 
+https://ignite.apache.org/releases/1.6.0/javadoc; target="_blank">Javadoc 

+https://ignite.apache.org/releases/1.6.0/dotnetdoc; target="_blank">.NET 
API 
+https://ignite.apache.org/releases/1.6.0/cppdoc; target="_blank">C++ API 

+   
https://ignite.apache.org/releases/1.6.0/scaladoc/scalar; 
target="_blank">Scala API 
 https://github.com/apache/ignite/tree/master/examples; 
target="_blank">Examples 
 
 

Modified: ignite/site/trunk/index.html
URL: 
http://svn.apache.org/viewvc/ignite/site/trunk/index.html?rev=1750736=1750735=1750736=diff
==
--- ignite/site/trunk/index.html (original)
+++ ignite/site/trunk/index.html Thu Jun 30 02:44:40 2016
@@ -117,12 +117,12 @@ under the License.
 
 
 http://www.meetup.com/Apache-Ignite-London/events/231963106/; 
target="_blank">
-Apache Ignite London meetup
+Apache Ignite London Mee

svn commit: r1749801 - in /ignite/site/trunk: download.html index.html news.html

[dsetrakyan]

Author: dsetrakyan
Date: Thu Jun 23 00:37:38 2016
New Revision: 1749801

URL: http://svn.apache.org/viewvc?rev=1749801=rev
Log:
updated news

Modified:
ignite/site/trunk/download.html
ignite/site/trunk/index.html
ignite/site/trunk/news.html

Modified: ignite/site/trunk/download.html
URL: 
http://svn.apache.org/viewvc/ignite/site/trunk/download.html?rev=1749801=1749800=1749801=diff
==
--- ignite/site/trunk/download.html (original)
+++ ignite/site/trunk/download.html Thu Jun 23 00:37:38 2016
@@ -175,7 +175,7 @@ under the License.
 Git Repositories
 https://issues.apache.org/jira/browse/IGNITE; target="_blank">Ignite Jira 

 https://cwiki.apache.org/confluence/display/IGNITE/; 
target="_blank">Ignite Wiki 
-http://www.meetup.com/Apache-Ignite-London; target="_blank">Ignite London 
Meetup 
+http://www.meetup.com/Apache-Ignite-London; target="_blank">Ignite Meetup 

 People
 
 Contribute

Modified: ignite/site/trunk/index.html
URL: 
http://svn.apache.org/viewvc/ignite/site/trunk/index.html?rev=1749801=1749800=1749801=diff
==
--- ignite/site/trunk/index.html (original)
+++ ignite/site/trunk/index.html Thu Jun 23 00:37:38 2016
@@ -116,6 +116,16 @@ under the License.
 Latest News
 
 
+http://www.meetup.com/Apache-Ignite-London/events/231963106/; 
target="_blank">
+Apache Ignite London meetup
+July 13, 2016
+
+
+http://www.meetup.com/mysqlnyc/events/231578906/; target="_blank">
+Apache Ignite NYC meetup
+June 28, 2016
+
+
 https://dzone.com/articles/apache-ignite-how-to-read-data-from-persistent-sto;
 target="_blank">
 Real-time In-memory OLTP and Analytics With 
Apache Ignite on AWS
 Blog, Babu Elumalai, 
June 6, 2016
@@ -125,29 +135,15 @@ under the License.
 Apache Ignite: How to Read Data From 
Persistent Store
 Blog, Prachi Garg, 
June 3, 2016
 
+
+Apache Ignite 1.6.0 Released
+May 23, 2016
+
 
 https://dzone.com/articles/pitfalls-of-the-mybatis-caches-with-apache-ignite;
 target="_blank">
 Pitfalls of the MyBatis Caches With Apache 
Ignite
 Blog, Shamim Bhuiyan, 
Mar 9, 2016
 
-
-https://dzone.com/articles/linking-apache-ignite-and-apache-kafka-for-highly;
 target="_blank">
-Linking Apache Ignite and Apache Kafka for 
Highly Scalable and Reliable Data Processing
-Blog, Roman Shtykh, 
Mar 3, 2016
-
-
-Ignite Adds Add-ons
-Feb 17, 2016
-
-
-
-
-
-
-
-
-
-
 
 Read 
More
 

Modified: ignite/site/trunk/news.html
URL: 
http://svn.apache.org/viewvc/ignite/site/trunk/news.html?rev=1749801=1749800=1749801=diff
==
Binary files - no diff available.

svn commit: r1749624 - in /ignite/site/trunk: community/resources.html download.html features/datagrid.html includes/header.html index.html news.html

[dsetrakyan]

Author: dsetrakyan
Date: Wed Jun 22 00:47:36 2016
New Revision: 1749624

URL: http://svn.apache.org/viewvc?rev=1749624=rev
Log:
Updated links and news.

Modified:
ignite/site/trunk/community/resources.html
ignite/site/trunk/download.html
ignite/site/trunk/features/datagrid.html
ignite/site/trunk/includes/header.html
ignite/site/trunk/index.html
ignite/site/trunk/news.html

Modified: ignite/site/trunk/community/resources.html
URL: 
http://svn.apache.org/viewvc/ignite/site/trunk/community/resources.html?rev=1749624=1749623=1749624=diff
==
--- ignite/site/trunk/community/resources.html (original)
+++ ignite/site/trunk/community/resources.html Wed Jun 22 00:47:36 2016
@@ -186,7 +186,7 @@ under the License.
 Evans Ye *Trend Micro
 Yakov Zhdanov *GridGain
Vladisav 
Jelisavcic
-   Pavel Tupitsyn
+   Pavel 
TupitsynGridGain
 
 
 

Modified: ignite/site/trunk/download.html
URL: 
http://svn.apache.org/viewvc/ignite/site/trunk/download.html?rev=1749624=1749623=1749624=diff
==
--- ignite/site/trunk/download.html (original)
+++ ignite/site/trunk/download.html Wed Jun 22 00:47:36 2016
@@ -175,6 +175,7 @@ under the License.
 Git Repositories
 https://issues.apache.org/jira/browse/IGNITE; target="_blank">Ignite Jira 

 https://cwiki.apache.org/confluence/display/IGNITE/; 
target="_blank">Ignite Wiki 
+http://www.meetup.com/Apache-Ignite-London; target="_blank">Ignite London 
Meetup 
 People
 
 Contribute

Modified: ignite/site/trunk/features/datagrid.html
URL: 
http://svn.apache.org/viewvc/ignite/site/trunk/features/datagrid.html?rev=1749624=1749623=1749624=diff
==
--- ignite/site/trunk/features/datagrid.html (original)
+++ ignite/site/trunk/features/datagrid.html Wed Jun 22 00:47:36 2016
@@ -290,14 +290,14 @@ under the License.
 Partitioning & Replication
 
 
-Depending on configuration, Ignite can either 
partition or replicate
+Depending on the configuration, Ignite can 
either partition or replicate
 data in memory. Unlike REPLICATED 
mode, where data is fully replicated across
 all nodes in the cluster, in 
PARTITIONED mode Ignite will equally split the data
 across multiple cluster nodes, allowing for 
caching TBs of data in memory.
 
 
 Ignite also allows to configure multiple 
backup copies to guarantee data resiliency
-in case of failures.
+in case of node failures.
 
 
 http://apacheignite.readme.io/docs/cache-modes; target="docs">Docs for 
this Feature 

Modified: ignite/site/trunk/includes/header.html
URL: 
http://svn.apache.org/viewvc/ignite/site/trunk/includes/header.html?rev=1749624=1749623=1749624=diff
==
--- ignite/site/trunk/includes/header.html (original)
+++ ignite/site/trunk/includes/header.html Wed Jun 22 00:47:36 2016
@@ -109,6 +109,7 @@
 Git Repositories
 https://issues.apache.org/jira/browse/IGNITE; target="_blank">Ignite Jira 

 https://cwiki.apache.org/confluence/display/IGNITE/; 
target="_blank">Ignite Wiki 
+http://www.meetup.com/Apache-Ignite-London; target="_blank">Ignite Meetup 

 People
 
 Contribute

Modified: ignite/site/trunk/index.html
URL: 
http://svn.apache.org/viewvc/ignite/site/trunk/index.html?rev=1749624=1749623=1749624=diff
==
--- ignite/site/trunk/index.html (original)
+++ ignite/site/trunk/index.html We

svn commit: r1746513 - /ignite/site/trunk/features.html

[dsetrakyan]

Author: dsetrakyan
Date: Wed Jun  1 23:07:54 2016
New Revision: 1746513

URL: http://svn.apache.org/viewvc?rev=1746513=rev
Log:
Fixed near-caches link.

Modified:
ignite/site/trunk/features.html

Modified: ignite/site/trunk/features.html
URL: 
http://svn.apache.org/viewvc/ignite/site/trunk/features.html?rev=1746513=1746512=1746513=diff
==
--- ignite/site/trunk/features.html (original)
+++ ignite/site/trunk/features.html Wed Jun  1 23:07:54 2016
@@ -132,7 +132,7 @@ under the License.
 Near cache is local client-side cache that 
stores the most recently and most frequently accessed data.
 
 
-https://apacheignite.readme.io/docs/off-heap-memory; target="docs">Docs 
for this feature 
+https://apacheignite.readme.io/docs/near-caches; target="docs">Docs for 
this feature 
 
 
 

svn commit: r1743599 - /ignite/site/trunk/community/contribute.html

[dsetrakyan]

Author: dsetrakyan
Date: Fri May 13 04:41:17 2016
New Revision: 1743599

URL: http://svn.apache.org/viewvc?rev=1743599=rev
Log:
Added Apache Apex ticket.

Modified:
ignite/site/trunk/community/contribute.html

Modified: ignite/site/trunk/community/contribute.html
URL: 
http://svn.apache.org/viewvc/ignite/site/trunk/community/contribute.html?rev=1743599=1743598=1743599=diff
==
--- ignite/site/trunk/community/contribute.html (original)
+++ ignite/site/trunk/community/contribute.html Fri May 13 04:41:17 2016
@@ -104,6 +104,7 @@ under the License.
 
 
 Spring Transaction Manager, https://issues.apache.org/jira/browse/IGNITE-1227;>IGNITE-1227
+Apache Apex Connectors, https://issues.apache.org/jira/browse/IGNITE-3131;>IGNITE-3131 
 
 
 Streaming: