ignite-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From dma...@apache.org
Subject svn commit: r1805682 - in /ignite/site/ignite-6036: ./ .htaccess css/all.css features.html features/sql.html images/memory-centric.png index.html memorycentric.html news.html scss/ignite.scss whatisignite.html
Date Mon, 21 Aug 2017 20:56:48 GMT
Author: dmagda
Date: Mon Aug 21 20:56:47 2017
New Revision: 1805682

URL: http://svn.apache.org/viewvc?rev=1805682&view=rev
Log:
merged changes from the trunk

Added:
    ignite/site/ignite-6036/images/memory-centric.png
      - copied unchanged from r1805681, ignite/site/trunk/images/memory-centric.png
Removed:
    ignite/site/ignite-6036/news.html
Modified:
    ignite/site/ignite-6036/   (props changed)
    ignite/site/ignite-6036/.htaccess
    ignite/site/ignite-6036/css/all.css
    ignite/site/ignite-6036/features.html
    ignite/site/ignite-6036/features/sql.html
    ignite/site/ignite-6036/index.html
    ignite/site/ignite-6036/memorycentric.html
    ignite/site/ignite-6036/scss/ignite.scss
    ignite/site/ignite-6036/whatisignite.html

Propchange: ignite/site/ignite-6036/
------------------------------------------------------------------------------
--- svn:mergeinfo (original)
+++ svn:mergeinfo Mon Aug 21 20:56:47 2017
@@ -1 +1,2 @@
+/ignite/site/trunk:1805444-1805681
 /incubator/ignite/site/branches/sidenav:1646576-1658604

Modified: ignite/site/ignite-6036/.htaccess
URL: http://svn.apache.org/viewvc/ignite/site/ignite-6036/.htaccess?rev=1805682&r1=1805681&r2=1805682&view=diff
==============================================================================
--- ignite/site/ignite-6036/.htaccess (original)
+++ ignite/site/ignite-6036/.htaccess Mon Aug 21 20:56:47 2017
@@ -1,6 +1,7 @@
 Options +Includes
 AddOutputFilter INCLUDES .html
 Redirect 301 /download.html /download.cgi
+Redirect 301 /news.html /events.html
 
 RewriteEngine On 
 

Modified: ignite/site/ignite-6036/css/all.css
URL: http://svn.apache.org/viewvc/ignite/site/ignite-6036/css/all.css?rev=1805682&r1=1805681&r2=1805682&view=diff
==============================================================================
--- ignite/site/ignite-6036/css/all.css (original)
+++ ignite/site/ignite-6036/css/all.css Mon Aug 21 20:56:47 2017
@@ -9250,120 +9250,6 @@ div.square {
   background-color: black;
 }
 
-table.common-table {
-  border: none !important;
-  margin-bottom: 20px;
-  position: relative;
-}
-table.common-table > thead > tr {
-  background: #e50000;
-  border: 1px solid #e50000;
-}
-table.common-table > thead > tr > th {
-  color: white;
-  font-size: 20px !important;
-  font-weight: 400;
-  border: none !important;
-}
-table.common-table > thead > tr .left {
-  padding-left: 20px !important;
-}
-table.common-table > tbody > tr {
-  border-bottom: 1px solid #d7d7d7;
-}
-table.common-table > tbody > tr > td {
-  border: none !important;
-  font-weight: 300;
-  letter-spacing: 0.2px;
-  padding-right: 0px !important;
-  line-height: 1.5em;
-}
-table.common-table > tbody > tr > td > p {
-  margin-top: 8px;
-  margin-bottom: 8px;
-}
-@media (max-width: 767px) {
-  table.common-table > tbody > tr > td > p {
-    margin-top: 0px;
-    margin-right: 5px;
-    padding-right: 5px;
-  }
-}
-@media (max-width: 767px) {
-  table.common-table > tbody > tr > td {
-    white-space: normal !important;
-  }
-}
-table.common-table > tbody > tr .left {
-  font-weight: bold;
-  padding-left: 20px !important;
-}
-@media (max-width: 767px) {
-  table.common-table > tbody {
-    border: none !important;
-  }
-}
-@media (max-width: 767px) {
-  table.common-table {
-    display: none !important;
-  }
-}
-
-table.common-table-mobile {
-  display: none;
-}
-@media (max-width: 767px) {
-  table.common-table-mobile {
-    border: none !important;
-    padding-bottom: 20px;
-    position: relative;
-  }
-  table.common-table-mobile > thead {
-    display: block !important;
-  }
-  table.common-table-mobile > thead > tr {
-    background: #e50000;
-    border: 1px solid #e50000;
-    height: 40px;
-  }
-  table.common-table-mobile > thead > tr > th {
-    color: white;
-    font-size: 20px !important;
-    font-weight: 400;
-    border: none !important;
-    display: block !important;
-    text-align: center;
-    padding: 10px !important;
-  }
-  table.common-table-mobile > tbody > tr {
-    border-bottom: 1px solid #d7d7d7;
-  }
-  table.common-table-mobile > tbody > tr > td {
-    border: none !important;
-    font-weight: 300;
-    letter-spacing: 0.2px;
-    vertical-align: middle;
-    line-height: 1.5em;
-    text-align: center;
-  }
-  table.common-table-mobile > tbody > tr > td > span {
-    padding: 0px !important;
-  }
-  table.common-table-mobile > tbody > tr > td .right {
-    float: right;
-    width: 50%;
-    margin-left: 10px;
-  }
-  table.common-table-mobile > tbody > tr.ignite {
-    background: #eee;
-  }
-}
-@media (max-width: 767px) and (max-width: 767px) {
-  table.common-table-mobile > tbody {
-    border: none !important;
-  }
-}
-
 .btn-transparent {
   color: #fff;
   background-color: transparent;

Modified: ignite/site/ignite-6036/features.html
URL: http://svn.apache.org/viewvc/ignite/site/ignite-6036/features.html?rev=1805682&r1=1805681&r2=1805682&view=diff
==============================================================================
--- ignite/site/ignite-6036/features.html (original)
+++ ignite/site/ignite-6036/features.html Mon Aug 21 20:56:47 2017
@@ -320,6 +320,22 @@ under the License.
                         </td>
                     </tr>
                     <tr class="sub-heading">
+                        <th colspan="2" class="left">Tooling</th>
+                    </tr>
+                    <tr></tr> <!-- this empty row is required to change the
background color-->
+                    <tr>
+                        <td class="features-left">SQL Tooling</td>
+                            <td>
+                                <p>
+                                    You can process data stored in the Ignite cluster using
a SQL tool of your choice -
+                                    <b>DBeaver</b>, <b>Pentaho</b>,
<b>Tableau</b>, <b>Web Console</b>, <b>Apache Zeppelin</b>.
+                                </p>
+                                <div class="page-links">
+                                    <a href="https://apacheignite.readme.io/docs/sql-tooling"
target="docs">Docs for this Feature <i class="fa fa-angle-double-right"></i></a>
+                                </div>
+                            </td>
+                    </tr>
+                    <tr class="sub-heading">
                         <th colspan="2" class="left">STANDARDS</th>
                     </tr>
                     <tr></tr> <!-- this empty row is required to change the
background color-->
@@ -334,6 +350,7 @@ under the License.
                     <tr class="sub-heading">
                         <th colspan="2" class="left">INTEGRATIONS</th>
                     </tr>
+                    <tr></tr> <!-- this empty row is required to change the
background color-->
                     <tr>
                         <td class="features-left">Apache Zeppelin</td>
                         <td>

Modified: ignite/site/ignite-6036/features/sql.html
URL: http://svn.apache.org/viewvc/ignite/site/ignite-6036/features/sql.html?rev=1805682&r1=1805681&r2=1805682&view=diff
==============================================================================
Binary files - no diff available.

Modified: ignite/site/ignite-6036/index.html
URL: http://svn.apache.org/viewvc/ignite/site/ignite-6036/index.html?rev=1805682&r1=1805681&r2=1805682&view=diff
==============================================================================
Binary files - no diff available.

Modified: ignite/site/ignite-6036/memorycentric.html
URL: http://svn.apache.org/viewvc/ignite/site/ignite-6036/memorycentric.html?rev=1805682&r1=1805681&r2=1805682&view=diff
==============================================================================
--- ignite/site/ignite-6036/memorycentric.html (original)
+++ ignite/site/ignite-6036/memorycentric.html Mon Aug 21 20:56:47 2017
@@ -53,69 +53,33 @@ under the License.
     <main id="main" role="main" class="container">
         <section id="memory-centric" class="page-section">
             <h1 class="first">What is Memory-Centric?</h1>
-
-            <p>
-                Apache Ignite is a <b>memory-centric</b> data platform that combines
the performance and scale of
-                in-memory computing together with the disk durability and strong consistency
in one system.
-            </p>
-            <div class="row">
-                <div class="col-sm-6 col-md-2 col-xs-12">
-                </div>
-                <div class="col-sm-6 col-md-8 col-xs-12">
-                    <table id="mc" class="common-table" name="memory-centric">
-                        <thead>
-                        <tr><th>Memory-Centric</th><th>Disk-Centric</th></tr>
-                        </thead>
-                        <tbody>
-                        <tr>
-                            <td>Memory as a Main Storage</td>
-                            <td>Memory as Caching Layer</td>
-
-                        </tr>
-                        <tr style="background-color: #eee;">
-                            <td>Collocated and Client-Server Processing</td>
-                            <td>Client-Server Processing</td>
-                        </tr>
-                        </tbody>
-                    </table>
-
-                    <table id="mc-mobile" class="common-table-mobile" name="memory-centric">
-                        <thead>
-                            <tr><th>Memory-Centric</th><th>Disk-Centric</th></tr>
-                        </thead>
-                        <tbody>
-                            <tr>
-                                <td>Memory as a Main Storage</td></tr>
-                                <tr><td>Collocated and Client-Server Processing</td>
-                            </tr>
-                        </tbody>
-                        <thead>
-                            <tr><th>Disk-Centric</th></tr>
-                        </thead>
-                        <tbody>
-                            <tr><td>Memory as Caching Layer</td></tr>
-                            <tr><td>Client-Server Processing</td></tr>
-                        </tbody>
-                    </table>
+            <div class="col-sm-12 col-md-12 col-xs-12" style="padding:0 0 20px 0;">
+                <div class="col-sm-6 col-md-6 col-xs-12" style="padding-left:0; padding-right:0">
+                    <p>
+                        Apache Ignite is a <b>memory-centric</b> data platform
that combines the performance and scale of
+                        in-memory computing together with the disk durability and strong
consistency in one system.
+                    </p>
+                    <p>
+                        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.
+                    </p>
                 </div>
-                <div class="col-sm-6 col-md-2 col-xs-12">&nbsp;
+                <div class="col-sm-6 col-md-6 col-xs-12" style="padding-right:0">
+                    <img class="img-responsive" src="/images/memory-centric.png" width="440px"
style="float: right; margin-top: -25px;"/>
                 </div>
             </div>
-            <p>
-                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.
-            </p>
+
             <p>
                 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.
-
             </p>
-
-            <h3>Collocated vs Client-Server Processing</h3>
+            <br/>
+            <br/>
+            <h2>Collocated vs Client-Server Processing</h2>
             <p>
                 The disk-centric systems, like RDBMS or NoSQL, generally utilize the classic
client-server approach, where
                 the data is brought from the server to the client side where it gets processed
and then is usually discarded.

Modified: ignite/site/ignite-6036/scss/ignite.scss
URL: http://svn.apache.org/viewvc/ignite/site/ignite-6036/scss/ignite.scss?rev=1805682&r1=1805681&r2=1805682&view=diff
==============================================================================
--- ignite/site/ignite-6036/scss/ignite.scss (original)
+++ ignite/site/ignite-6036/scss/ignite.scss Mon Aug 21 20:56:47 2017
@@ -1808,133 +1808,3 @@ div.square {
 .wrapper-main-banner {
     background-color: rgb(0, 0, 0);
 }
-
-table.common-table {
-    border: none !important;
-    margin-bottom: 20px;
-    position: relative;
-
-    & > thead > tr {
-        background: #e50000;
-        border: 1px solid #e50000;
-
-        & > th {
-            color: white;
-            font-size: 20px !important;
-            font-weight: 400;
-            border: none !important;
-        }
-        & .left {
-            padding-left: 20px !important;
-        }
-    }
-
-    & > tbody {
-
-        & > tr {
-            border-bottom: 1px solid #d7d7d7;
-            & > td {
-                border: none !important;
-                font-weight: 300;
-                letter-spacing: 0.2px;
-                padding-right: 0px !important;
-                line-height: 1.5em;
-
-                & > p {
-                    margin-top : 8px;
-                    margin-bottom : 8px;
-
-
-                    @media (max-width: $mobile) {
-                        margin-top : 0px;
-                        margin-right : 5px;
-                        padding-right: 5px;
-                    }
-                }
-
-                @media (max-width: $mobile) {
-                    white-space: normal !important;
-                }
-            }
-
-            & .left {
-                font-weight: bold;
-                padding-left: 20px !important;
-            }
-        }
-
-        @media (max-width: $mobile) {
-            border: none !important;
-        }
-    }
-
-    @media (max-width: $mobile) {
-        display: none !important;
-    }
-}
-
-table.common-table-mobile {
-    display: none;
-    @media (max-width: $mobile) {
-        border: none !important;
-        padding-bottom: 20px;
-        position: relative;
-
-        & > thead {
-            display: block !important;
-            & > tr {
-                background: #e50000;
-                border: 1px solid #e50000;
-                height: 40px;
-                & > th {
-                    color: white;
-                    font-size: 20px !important;
-                    font-weight: 400;
-                    border: none !important;
-                    display: block !important;
-                    text-align: center;
-                    padding : 10px !important;
-                }
-
-            }
-        }
-
-        & > tbody {
-
-            & > tr {
-                border-bottom: 1px solid #d7d7d7;
-
-                & > td {
-                    border: none !important;
-                    font-weight: 300;
-                    letter-spacing: 0.2px;
-                    vertical-align: middle;
-                    line-height: 1.5em;
-                    text-align: center;
-
-                    & > span {
-                        padding: 0px !important;
-                    }
-
-                    & .right {
-                        float: right;
-                        width: 50%;
-                        margin-left: 10px;
-                    }
-
-                    & .left {
-
-                    }
-                }
-
-                &.ignite {
-                    background: #eee;
-                }
-            }
-
-            @media (max-width: $mobile) {
-                border: none !important;
-            }
-        }
-    }
-}
\ No newline at end of file

Modified: ignite/site/ignite-6036/whatisignite.html
URL: http://svn.apache.org/viewvc/ignite/site/ignite-6036/whatisignite.html?rev=1805682&r1=1805681&r2=1805682&view=diff
==============================================================================
--- ignite/site/ignite-6036/whatisignite.html (original)
+++ ignite/site/ignite-6036/whatisignite.html Mon Aug 21 20:56:47 2017
@@ -69,71 +69,63 @@ under the License.
             </div>
         </section>
         <section id="ignite-faq" class="page-section">
-            <h2>Is Ignite a distributed database?</h2>
+            <h2>Is Ignite an in-memory database (IMDB)?</h2>
             <p>
-                <strong>Yes</strong>. 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.
+                <strong>Yes</strong>. 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
+                support for SQL and distributed joins.
             </p>
             <p><a href="https://apacheignite.readme.io/v2.1/docs/distributed-sql"></a></p><br/><br/>
 
-            <h2>Is Ignite a relational SQL database?</h2>
-            <p>
-                <strong>Not fully</strong>. 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.
-            </p>
+            <h2>Is Ignite an in-memory data grid (IMDG)?</h2>
             <p>
-                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.
+                <strong>Yes</strong>. 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.
             </p>
-            <p><a href="https://apacheignite.readme.io/v2.1/docs/indexes"></a></p><br/><br/>
+            <p><a href="https://apacheignite.readme.io/v2.1/docs/data-grid"></a></p><br/><br/>
 
-            <h2>Is Ignite an in-memory database?</h2>
+            <h2>Is Ignite a distributed database?</h2>
             <p>
-                <strong>Yes</strong>. 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.
+                <strong>Yes</strong>. 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.
             </p>
             <p><a href="https://apacheignite.readme.io/v2.1/docs/distributed-sql"></a></p><br/><br/>
 
-            <h2>Is Ignite a transactional database?</h2>
-            <p>
-                <strong>Not fully</strong>. 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.
-            </p>
-
+            <h2>Is Ignite an SQL database?</h2>
             <p>
-                At SQL level Ignite supports atomic, but not yet transactional consistency.
Ignite community plans to implement SQL transactions in version 2.2.
+                <strong>Not fully</strong>. 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.
             </p>
-            <p><a href="https://apacheignite.readme.io/v2.1/docs/sql-queries#known-limitations"></a></p><br/><br/>
-
-            <h2>Is Ignite a key-value store?</h2>
             <p>
-                <strong>Yes</strong>. Ignite provides a feature rich key-value
API, that is JCache (JSR-107) compliant and supports Java, C++, <nobr>and .NET.</nobr>
+                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.
             </p>
-            <p><a href="https://apacheignite.readme.io/v2.1/docs/data-grid"></a></p><br/><br/>
+            <p><a href="https://apacheignite.readme.io/v2.1/docs/indexes"></a></p><br/><br/>
 
-            <h2>Is Ignite an in-memory data grid (IMDG)?</h2>
+            <h2>Is Ignite a transactional database?</h2>
             <p>
-                <strong>Yes</strong>. Ignite is a full-featured data grid, which
can be used either in pure in-memory mode or with Ignite native persistence.
-                It can also integrate with any 3rd party database, including any RDBMS or
NoSQL store.
+                <strong>Not fully</strong>. 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.
             </p>
-            <p><a href="https://apacheignite.readme.io/v2.1/docs/data-grid"></a></p><br/><br/>
 
-            <h2>What is durable memory?</h2>
             <p>
-                Ignite durable memory architecture allows Ignite to extend in-memory computing
to disk. It is based on a paged-based off-heap memory
-                allocator which becomes durable by persisting to the write-ahead-log (WAL)
and, then, to main Ignite persistent storage. When persistence
-                is disabled, durable memory acts like a pure in-memory storage.
+                At SQL level Ignite supports atomic, but not yet transactional consistency.
Ignite community plans
+                to implement SQL transactions in version 2.3.
             </p>
-            <p><a href="https://apacheignite.readme.io/v2.1/docs/durable-memory"></a></p><br/><br/>
+            <p><a href="https://apacheignite.readme.io/v2.1/docs/sql-queries#known-limitations"></a></p><br/><br/>
 
-            <h2>What is collocated processing?</h2>
+            <h2>Is Ignite a key-value store?</h2>
             <p>
-                Ignite is a distributed system and, therefore, it is important to be able
collocate data with data and compute with data to avoid distributed data noise.
-                Data collocation becomes especially important when performing distributed
SQL joins. Ignite also supports sending user logic
-                (functions, lambdas, etc.) directly to the nodes where the data resides and
computing on data locally.
+                <strong>Yes</strong>. Ignite provides a feature rich key-value
API, that is JCache (JSR-107) compliant
+                and supports Java, C++, <nobr>and .NET.</nobr>
             </p>
-            <p><a href="https://apacheignite.readme.io/v2.1/docs/collocate-compute-and-data"></a></p><br/><br/>
+            <p><a href="https://apacheignite.readme.io/v2.1/docs/data-grid"></a></p><br/><br/>
 
             <h2>Book</h2>
                 <p>Learn even more from <a href="http://a.co/h4MBi1v" target="_blank">High-Performance
in-memory computing with Apache Ignite</a> book.</p>



Mime
View raw message