Author: dmagda
Date: Thu Aug 24 00:48:35 2017
New Revision: 1805981
URL: http://svn.apache.org/viewvc?rev=1805981&view=rev
Log:
completed all the documentation
Modified:
ignite/site/ignite-6036/collocatedprocessing.html
ignite/site/ignite-6036/features/datagrid.html
ignite/site/ignite-6036/use-cases/comparison/ignite-for-rdbms.html
Modified: ignite/site/ignite-6036/collocatedprocessing.html
URL:
http://svn.apache.org/viewvc/ignite/site/ignite-6036/collocatedprocessing.html?rev=1805981&r1=1805980&r2=1805981&view=diff
==============================================================================
--- ignite/site/ignite-6036/collocatedprocessing.html (original)
+++ ignite/site/ignite-6036/collocatedprocessing.html Thu Aug 24 00:48:35 2017
@@ -91,6 +91,60 @@ under the License.
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!
</p>
+
+ <p>
+ Code snippet below shows a way how this computation might look
like:
+ </p>
+ <!--<ul id="compute-example" class="nav nav-tabs">-->
+ <!--<li class="active"><a href="#compute-task"
aria-controls="profile" data-toggle="tab">Message Broadcasting Logic</a></li>-->
+ <!--</ul>-->
+
+ <div class="tab-content">
+
+ <div class="tab-pane active" id="compute-task">
+ <pre class="brush:java">
+
+Ignite ignite = ...
+
+// NewYork ID.
+long newYorkId = 2;
+
+// Sending the logic to a cluster node that stores NewYork and all its
inhabitants.
+ignite.compute().affinityRun("City", newYorkId, new IgniteRunnable() {
+
+ @IgniteInstanceResource
+ Ignite ignite;
+
+ @Override
+ public void run() {
+ // Getting an access to Persons cache.
+ IgniteCache<BinaryObject, BinaryObject> people =
ignite.cache("Person").withKeepBinary();
+
+
+ ScanQuery<BinaryObject, BinaryObject> query = new ScanQuery
<BinaryObject, BinaryObject>();
+
+ try (QueryCursor<Cache.Entry<BinaryObject, BinaryObject>>
cursor = people.query(query)) {
+ // Iteration over the local cluster node data using the scan query.
+ for (Cache.Entry<BinaryObject, BinaryObject> entry : cursor) {
+ BinaryObject personKey = entry.getKey();
+
+ // Picking NewYorker's only.
+ if (personKey.<Long>field("CITY_ID") == newYorkId) {
+ person = entry.getValue();
+
+ // Sending the warning message to the person.
+ }
+ }
+ }
+ }
+}
+
+ </pre>
+ </div>
+ </div>
+ <p>
+ Check more <a
href="https://apacheignite.readme.io/docs/affinity-collocation";
target="_blank">here</a>.
+ </p>
</section>
</main>
Modified: ignite/site/ignite-6036/features/datagrid.html
URL:
http://svn.apache.org/viewvc/ignite/site/ignite-6036/features/datagrid.html?rev=1805981&r1=1805980&r2=1805981&view=diff
==============================================================================
--- ignite/site/ignite-6036/features/datagrid.html (original)
+++ ignite/site/ignite-6036/features/datagrid.html Thu Aug 24 00:48:35 2017
@@ -56,18 +56,27 @@ under the License.
<div class="col-sm-12 col-md-12 col-xs-12" style="padding:0 0 20px
0;">
<div class="col-sm-6 col-md-7 col-xs-12"
style="padding-left:0; padding-right:0">
<p>
- Ignite In-Memory Data Grid is an <code>in-memory
distributed key-value store</code> that
- enables caching data in memory within distributed
clusters. 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.
+ 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
+ cluster node owning a portion of the overall data.
This way the more cluster nodes we add, the
+ more data we can cache.
</p>
<p>
- 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 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.
</p>
<p>
- Ignite Data Grid is lightning fast and is one of the
fastest implementations of transactional or
- atomic data in distributed clusters today. We know it
because we constantly benchmark it ourselves.
+ Ignite Data Grid is lightning fast and is one of the
fastest implementations of transactional or
+ atomic data in distributed clusters today. We know it
because we constantly benchmark it ourselves.
+ </p>
+ <p>
+ Data along with indexes can be persisted in <a
href="/features/persistence.html" target="_blank">
+ Ignite Native Persistence</a> 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.
+ <a
href="https://apacheignite.readme.io/docs/distributed-persistent-store";
target="_blank">Learn more</a>
+ when to use one type of persistence over another.
</p>
<div class="videos">
@@ -76,13 +85,6 @@ under the License.
<li>
<i class="fa fa-lg fa-play-circle-o"></i>
<span class="video-title">
- <a target="youtube"
href="https://www.youtube.com/watch?v=eZUujozYt-g";>Distributed SQL Queries</a>
- </span>
- <span class="video-duration">03:27</span>
- </li>
- <li>
- <i class="fa fa-lg fa-play-circle-o"></i>
- <span class="video-title">
<a target="youtube"
href="https://www.youtube.com/watch?v=pFbDWpOiMOU";>Getting Started with Data
Grid</a>
</span>
<span class="video-duration">03:49</span>
@@ -314,7 +316,7 @@ under the License.
Ignite allows executing any native Java, C++,
and .NET/C# code directly on the server-side, close to the data, in collocated
fashion.
</p>
<div class="page-links">
- <a
href="https://apacheignite.readme.io/docs/affinity-collocation";
target="docs">Docs for this feature <i class="fa fa-angle-double-right"></i></a>
+ <a href="/collocatedprocessing.html"
target="docs">Docs for this feature <i class="fa fa-angle-double-right"></i></a>
</div>
</td>
</tr>
@@ -343,13 +345,28 @@ under the License.
</td>
</tr>
<tr>
- <td class="left">Page Memory</td>
+ <td class="left">Durable Memory</td>
<td>
<p>
- Apache Ignite <code>Page Memory</code> is a
manageable off-heap based memory architecture that is split into pages of fixed
size. Ignite stores data in off-heap memory with an option to store data
on-heap.
+ Apache Ignite <code>Durable Memory</code>
allows storing and processing data and indexes
+ both in memory and on disk when the Ignite
Native Persistence feature is enabled.
</p>
<div class="page-links">
- <a
href="https://apacheignite.readme.io/docs/page-memory"; target="docs">Docs for
this Feature <i class="fa fa-angle-double-right"></i></a>
+ <a
href="https://apacheignite.readme.io/docs/durable-memory"; target="docs">Docs
for this Feature <i class="fa fa-angle-double-right"></i></a>
+ </div>
+ </td>
+ </tr>
+ <tr>
+ <td class="left">Ignite Native Persistence</td>
+ <td>
+ <p>
+ <code>Ignite Native Persistence</code> 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.
+ </p>
+ <div class="page-links">
+ <a
href="https://apacheignite.readme.io/docs/distributed-persistent-store";
target="docs">Docs for this Feature <i class="fa fa-angle-double-right"></i></a>
</div>
</td>
</tr>
@@ -441,28 +458,6 @@ under the License.
</td>
</tr>
<tr>
- <td class="left">SQL Queries</td>
- <td>
- <p>
- Ignite supports the standard SQL syntax (ANSI
99) to query the cache. You can use any SQL function, aggregation, or grouping.
- </p>
- <div class="page-links">
- <a
href="https://apacheignite.readme.io/docs/sql-queries"; target="docs">Docs for
this Feature <i class="fa fa-angle-double-right"></i></a>
- </div>
- </td>
- </tr>
- <tr>
- <td class="left" width="35%">Distributed Joins</td>
- <td>
- <p>
- Ignite supports <b>distributed SQL joins</b>
as well as <b>cross-cache joins</b>.
- </p>
- <div class="page-links">
- <a
href="https://apacheignite.readme.io/docs/sql-queries#distributed-joins";
target="docs">Docs for this feature <i class="fa fa-angle-double-right"></i></a>
- </div>
- </td>
- </tr>
- <tr>
<td class="left" width="35%">Continuous Queries</td>
<td>
<p>
@@ -474,53 +469,6 @@ under the License.
</td>
</tr>
<tr>
- <td class="left" width="35%">Query Indexing</td>
- <td>
- <p>
- For SQL queries, ignites supports in-memory
indexing, so all the data lookups are extremely fast.
- </p>
- <div class="page-links">
- <a
href="https://apacheignite.readme.io/docs/indexes"; target="docs">Docs for this
feature <i class="fa fa-angle-double-right"></i></a>
- </div>
- </td>
- </tr>
- <tr>
- <td class="left" width="35%">Query Consistency</td>
- <td>
- <p>
- In Ignite, provides full query consistency.
Updates that happened after the query execution started do not affect the query
result.
- </p>
- </td>
- </tr>
- <tr>
- <td class="left" width="35%">Query Fault-Tolerance</td>
- <td>
- <p>
- Ignite queries are fault-tolerant, i.e. query
result is always consistent and is not affected by cluster topology changes.
- </p>
- </td>
- </tr>
- <tr>
- <td class="left">JDBC Driver</td>
- <td>
- <p>
- Ignite is shipped with <code>JDBC
Driver</code> that allows you to retrieve distributed data from
- cache using standard SQL queries and JDBC API.
- </p>
- <div class="page-links">
- <a
href="http://apacheignite.readme.io/docs/jdbc-driver"; target="docs">Docs for
this Feature <i class="fa fa-angle-double-right"></i></a>
- </div>
- </td>
- </tr>
- <tr>
- <td class="left">ODBC Driver</td>
- <td>
- <p>
- Ignite ODBC driver allows users to retrieve
data from cache using standard SQL queries and ODBC API.
- </p>
- </td>
- </tr>
- <tr>
<td class="left">
<b>Database Integration</b>
</td>
@@ -631,30 +579,6 @@ under the License.
</div>
</td>
</tr>
- <tr>
- <td class="left">C#/.NET</td>
- <td>
- <p>
- Ignite.NET is built on top of Ignite. This
allows you to perform almost all the in-memory data grid
- operations including ACID transactions, SQL
queries, distributed joins, messaging and events, etc.
- </p>
- <div class="page-links">
- <a
href="https://apacheignite-net.readme.io/docs/"; target="docs">Docs for this
Feature <i class="fa fa-angle-double-right"></i></a>
- </div>
- </td>
- </tr>
- <tr>
- <td class="left">C++</td>
- <td>
- <p>
- Ignite C++ is built on top of Ignite. This
allows you to perform almost all the in-memory
- data grid operations including SQL queries,
and distributed joins.
- </p>
- <div class="page-links">
- <a
href="https://apacheignite-cpp.readme.io/docs"; target="docs">Docs for this
Feature <i class="fa fa-angle-double-right"></i></a>
- </div>
- </td>
- </tr>
<tr>
<td class="left">XA/JTA</td>
<td>
Modified: ignite/site/ignite-6036/use-cases/comparison/ignite-for-rdbms.html
URL:
http://svn.apache.org/viewvc/ignite/site/ignite-6036/use-cases/comparison/ignite-for-rdbms.html?rev=1805981&r1=1805980&r2=1805981&view=diff
==============================================================================
--- ignite/site/ignite-6036/use-cases/comparison/ignite-for-rdbms.html
(original)
+++ ignite/site/ignite-6036/use-cases/comparison/ignite-for-rdbms.html Thu Aug
24 00:48:35 2017
@@ -186,7 +186,7 @@ under the License.
<a href="/features/datagrid.html"
target="_blank">key-value</a> APIs and
<a href="/collocatedprocessing.html"
target="_blank">collocated processing</a> approach.
</p>
-
+
<p>
Check <a href="/features/sql.html" target="_blank">SQL</a>
section for more details or start using
Ignite as a SQL database referring to
