Author: dmagda
Date: Tue Aug 7 17:53:12 2018
New Revision: 1837609
URL: http://svn.apache.org/viewvc?rev=1837609&view=rev
Log:
fixed SQL page
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=1837609&r1=1837608&r2=1837609&view=diff
==============================================================================
--- ignite/site/trunk/features/sql.html (original)
+++ ignite/site/trunk/features/sql.html Tue Aug 7 17:53:12 2018
@@ -102,18 +102,14 @@ under the License.
</p>
<div class="page-heading">SQL and 3rd Party Databases</div>
- <p>
- Ignite can be used as a caching layer (aka. data grid) above
an existing 3rd party database -
- RDBMS, NoSQL, or HDFS. This mode is used to accelerate the
underlying database. Ignite provides read-through and
- write-through capabilities to read and write database records.
- </p>
- <p>
- In this mode, Ignite requires preloading data into caches for
SELECT queries; however, it propagates all updates - INSERT, UPDATE, DELETE -
to the database.
- </p>
+ <p>Ignite can be used as a caching layer (aka. data grid) above an
existing 3rd party database -
+ RDBMS, NoSQL, or HDFS. This mode is used to accelerate the
underlying database.</p>
- <p>
- Want to learn more? See <a
href="https://apacheignite-sql.readme.io/docs/overview"; target="_blank">Ignite
SQL Capabilities</a>
- </p>
+ <p> When a 3rd party database is configured, Ignite retrieves data
from the memory, and inserts data into both the memory and the database.
+ Therefore, in this mode Ignite requires preloading data into
caches for SELECT queries; however, it propagates all
+ updates - INSERT, UPDATE, DELETE - to the database.</p>
+
+ <p>Want to learn more? See <a
href="https://apacheignite-sql.readme.io/docs/overview"; target="_blank">Ignite
SQL Capabilities</a></p>
<div class="code-examples">
<div class="page-heading">Connectivity</div>
