svn commit: r929652 - in /websites/staging/drill/trunk/content: ./ drill/architecture/index.html

[bu...@apache.org]

Author: buildbot
Date: Tue Nov 18 13:12:36 2014
New Revision: 929652

Log:
Staging update by buildbot for drill

Modified:
    websites/staging/drill/trunk/content/   (props changed)
    websites/staging/drill/trunk/content/drill/architecture/index.html

Propchange: websites/staging/drill/trunk/content/
------------------------------------------------------------------------------
--- cms:source-revision (original)
+++ cms:source-revision Tue Nov 18 13:12:36 2014
@@ -1 +1 @@
-1640327
+1640329

Modified: websites/staging/drill/trunk/content/drill/architecture/index.html
==============================================================================
--- websites/staging/drill/trunk/content/drill/architecture/index.html (original)
+++ websites/staging/drill/trunk/content/drill/architecture/index.html Tue Nov 18 13:12:36 2014
@@ -80,7 +80,7 @@
             <p>
 
             	The following image represents the flow of a Drill query:
-            	<img src="/drillimages/arc-1.jpg" alt="The flow of a Drill query" width="550">
+            	<img src="/drill/images/arc-1.jpg" alt="The flow of a Drill query" width="550">
 
                 The flow of a Drill query typically involves the following steps:
 
@@ -97,7 +97,7 @@
             <h2>Core Modules within a Drillbit</h2>
             <p>The following image represents Drillbit components:</p>
 
-           	<img src="/drillimages/arc-2.jpg" alt="Drillbit components" width="525">
+           	<img src="/drill/images/arc-2.jpg" alt="Drillbit components" width="525">
 
             <p>• RPC end point: Drill exposes a low overhead protobuf-based RPC protocol to communicate with the clients. Additionally, a C++ and Java API layers are also available for the client applications to interact with Drill. Clients can communicate to a specific Drillbit directly or go through a ZooKeeper quorum to discover the available Drillbits before submitting queries. It is recommended that the clients always go through ZooKeeper to shield clients from the intricacies of cluster management, such as the addition or removal of nodes.</p>
             <p>• SQL parser: Drill uses Optiq, the open source framework, to parse incoming queries. The output of the parser component is a language agnostic, computer-friendly logical plan that represents the query.</p>
@@ -162,7 +162,7 @@ The following list provides a few exampl
 &nbsp;</p>
 <li><p><strong>Runtime compilation</strong>: 
 Runtime compilation is faster compared to the interpreted execution. Drill generates highly efficient custom code for every single query for every single operator.  Here is a quick overview of the Drill compilation/code generation process at a glance.
-<br><img src="/drillimages/drillcompiler.png" width="500">
+<br><img src="/drill/images/drillcompiler.png" width="500">
 &nbsp;</p>
 <li><p><strong>Optimistic and pipelined query execution</strong>: Drill adopts an optimistic execution model to process queries. Drill assumes that failures are infrequent within the short span of a query and therefore does not spend time creating boundaries or checkpoints to minimize recovery time. Failures at node level are handled gracefully. In the instance of a single query failure, the query is rerun. Drill execution uses a pipeline model where all tasks are scheduled at once. The query execution happens in-memory as much as possible to move data through task pipelines, persisting to disk only if there is memory overflow. 
 &nbsp;</p>