drill-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From krish...@apache.org
Subject [1/5] drill-site git commit: test files built w/jekyll 2.5.3
Date Fri, 18 Dec 2015 02:01:22 GMT
Repository: drill-site
Updated Branches:
  refs/heads/asf-site d2e91ed6f -> f06d89331


http://git-wip-us.apache.org/repos/asf/drill-site/blob/f06d8933/docs/value-window-functions/index.html
----------------------------------------------------------------------
diff --git a/docs/value-window-functions/index.html b/docs/value-window-functions/index.html
index 8703e7a..78847ec 100644
--- a/docs/value-window-functions/index.html
+++ b/docs/value-window-functions/index.html
@@ -373,10 +373,6 @@
             
           
             
-              <li class="toctree-l2"><a class="reference internal" href="/docs/mapr-db-format/">MapR-DB
Format</a></li>
-            
-          
-            
               <li class="toctree-l2"><a class="reference internal" href="/docs/s3-storage-plugin/">S3
Storage Plugin</a></li>
             
           
@@ -1088,12 +1084,12 @@
 
 <h2 id="syntax">Syntax</h2>
 
-<h3 id="lag-|-lead">LAG | LEAD</h3>
+<h3 id="lag-lead">LAG | LEAD</h3>
 <div class="highlight"><pre><code class="language-text" data-lang="text">
  LAG | LEAD
    ( expression )
    OVER ( [ PARTITION BY expr_list ] [ ORDER BY order_list ] )  
 </code></pre></div>
-<h3 id="first_value-|-last_value">FIRST_VALUE | LAST_VALUE</h3>
+<h3 id="first_value-last_value">FIRST_VALUE | LAST_VALUE</h3>
 <div class="highlight"><pre><code class="language-text" data-lang="text">
  FIRST_VALUE | LAST_VALUE
    ( expression ) OVER
    ( [ PARTITION BY expr_list ] [ ORDER BY order_list ][ frame_clause ] )  
@@ -1119,7 +1115,7 @@ The frame clause refines the set of rows in a function&#39;s window,
including o
 
 <p>The following examples show queries that use each of the value window functions
in Drill.  </p>
 
-<h3 id="lag()">LAG()</h3>
+<h3 id="lag">LAG()</h3>
 
 <p>The following example uses the LAG window function to show the quantity of records
sold to the Tower Records customer with customer ID 8  and the dates that customer 8 purchased
records. To compare each sale with the previous sale for customer 8, the query returns the
previous quantity sold for each sale. Since there is no purchase before 1976-01-25, the first
previous quantity sold value is null. Note that the term &quot;date&quot; in the query
is enclosed in back ticks because it is a reserved keyword in Drill.  </p>
 <div class="highlight"><pre><code class="language-text" data-lang="text">
  select cust_id, `date`, qty_sold, lag(qty_sold,1) over (order by cust_id, `date`) as prev_qtysold
from sales where cust_id = 8 order by cust_id, `date`;  
@@ -1135,7 +1131,7 @@ The frame clause refines the set of rows in a function&#39;s window,
including o
    +----------+-------------+-----------+---------------+
    5 rows selected (0.331 seconds)
 </code></pre></div>
-<h3 id="lead()">LEAD()</h3>
+<h3 id="lead">LEAD()</h3>
 
 <p>The following example uses the LEAD window function to provide the commission for
concert tickets with show ID 172 and the next commission for subsequent ticket sales. Since
there is no commission after 40.00, the last next_comm value is null. Note that the term &quot;date&quot;
in the query is enclosed in back ticks because it is a reserved keyword in Drill.  </p>
 <div class="highlight"><pre><code class="language-text" data-lang="text">
  select show_id, `date`, commission, lead(commission,1) over (order by `date`) as next_comm
from commission where show_id = 172;
@@ -1157,7 +1153,7 @@ The frame clause refines the set of rows in a function&#39;s window,
including o
    +----------+-------------+-------------+------------+
    12 rows selected (0.241 seconds)
 </code></pre></div>
-<h3 id="first_value()">FIRST_VALUE()</h3>
+<h3 id="first_value">FIRST_VALUE()</h3>
 
 <p>The following example uses the FIRST_VALUE window function to identify the employee
with the lowest sales for each dealer in Q1:</p>
 <div class="highlight"><pre><code class="language-text" data-lang="text">
  select emp_name, dealer_id, sales, first_value(sales) over (partition by dealer_id order
by sales) as dealer_low from q1_sales;
@@ -1177,7 +1173,7 @@ The frame clause refines the set of rows in a function&#39;s window,
including o
    +-----------------+------------+--------+-------------+
    10 rows selected (0.299 seconds)
 </code></pre></div>
-<h3 id="last_value()">LAST_VALUE()</h3>
+<h3 id="last_value">LAST_VALUE()</h3>
 
 <p>The following example uses the LAST_VALUE window function to identify the last car
sale each employee made at each dealership in 2013:</p>
 <div class="highlight"><pre><code class="language-text" data-lang="text">
  select emp_name, dealer_id, sales, `year`, last_value(sales) over (partition by  emp_name
order by `year`) as last_sale from emp_sales where `year` = 2013;

http://git-wip-us.apache.org/repos/asf/drill-site/blob/f06d8933/docs/where-clause/index.html
----------------------------------------------------------------------
diff --git a/docs/where-clause/index.html b/docs/where-clause/index.html
index 7b8c905..1d7f712 100644
--- a/docs/where-clause/index.html
+++ b/docs/where-clause/index.html
@@ -373,10 +373,6 @@
             
           
             
-              <li class="toctree-l2"><a class="reference internal" href="/docs/mapr-db-format/">MapR-DB
Format</a></li>
-            
-          
-            
               <li class="toctree-l2"><a class="reference internal" href="/docs/s3-storage-plugin/">S3
Storage Plugin</a></li>
             
           

http://git-wip-us.apache.org/repos/asf/drill-site/blob/f06d8933/docs/why-drill/index.html
----------------------------------------------------------------------
diff --git a/docs/why-drill/index.html b/docs/why-drill/index.html
index 3d564bb..4e27564 100644
--- a/docs/why-drill/index.html
+++ b/docs/why-drill/index.html
@@ -373,10 +373,6 @@
             
           
             
-              <li class="toctree-l2"><a class="reference internal" href="/docs/mapr-db-format/">MapR-DB
Format</a></li>
-            
-          
-            
               <li class="toctree-l2"><a class="reference internal" href="/docs/s3-storage-plugin/">S3
Storage Plugin</a></li>
             
           
@@ -1048,7 +1044,7 @@
       
         <h2 id="top-10-reasons-to-use-drill">Top 10 Reasons to Use Drill</h2>
 
-<h2 id="1.-get-started-in-minutes">1. Get started in minutes</h2>
+<h2 id="1-get-started-in-minutes">1. Get started in minutes</h2>
 
 <p>It takes just a few minutes to get started with Drill. Untar the Drill software
on your Linux, Mac, or Windows laptop and run a query on a local file. No need to set up any
infrastructure or to define schemas. Just point to the data, such as data in a file, directory,
HBase table, and drill.</p>
 <div class="highlight"><pre><code class="language-text" data-lang="text">$
tar -xvf apache-drill-&lt;version&gt;.tar.gz
@@ -1062,11 +1058,11 @@ $ &lt;install directory&gt;/bin/drill-embedded
 | 4            | Michael Spence             | Michael             | Spence        | 2   
        | VP Country Manager         | 0         | 1              | 1969-06-20  | 1998-01-01
00:00:00.0  | 40000.0  | 1              | Graduate Degree      | S               | M     
 | Senior Management     |
 | 5            | Maya Gutierrez             | Maya                | Gutierrez     | 2   
        | VP Country Manager         | 0         | 1              | 1951-05-10  | 1998-01-01
00:00:00.0  | 35000.0  | 1              | Bachelors Degree     | M               | F     
 | Senior Management     |
 </code></pre></div>
-<h2 id="2.-schema-free-json-model">2. Schema-free JSON model</h2>
+<h2 id="2-schema-free-json-model">2. Schema-free JSON model</h2>
 
 <p>Drill is the world&#39;s first and only distributed SQL engine that doesn&#39;t
require schemas. It shares the same schema-free JSON model as MongoDB and Elasticsearch. No
need to define and maintain schemas or transform data (ETL). Drill automatically understands
the structure of the data. </p>
 
-<h2 id="3.-query-complex,-semi-structured-data-in-situ">3. Query complex, semi-structured
data in-situ</h2>
+<h2 id="3-query-complex-semi-structured-data-in-situ">3. Query complex, semi-structured
data in-situ</h2>
 
 <p>Using Drill&#39;s schema-free JSON model, you can query complex, semi-structured
data in situ. No need to flatten or transform the data prior to or during query execution.
Drill also provides intuitive extensions to SQL to work with nested data. Here&#39;s a
simple query on a JSON file demonstrating how to access nested elements and arrays:</p>
 <div class="highlight"><pre><code class="language-text" data-lang="text">SELECT
* FROM (SELECT t.trans_id,
@@ -1077,7 +1073,7 @@ WHERE sq.prod_id BETWEEN 700 AND 750 AND
       sq.purchased = &#39;true&#39;
 ORDER BY sq.prod_id;
 </code></pre></div>
-<h2 id="4.-real-sql----not-&quot;sql-like&quot;">4. Real SQL -- not &quot;SQL-like&quot;</h2>
+<h2 id="4-real-sql-not-quot-sql-like-quot">4. Real SQL -- not &quot;SQL-like&quot;</h2>
 
 <p>Drill supports the standard SQL:2003 syntax. No need to learn a new &quot;SQL-like&quot;
language or struggle with a semi-functional BI tool. Drill supports many data types including
DATE, INTERVAL, TIMESTAMP, and VARCHAR, as well as complex query constructs such as correlated
sub-queries and joins in WHERE clauses. Here is an example of a TPC-H standard query that
runs in Drill:</p>
 
@@ -1094,11 +1090,11 @@ WHERE o.o_orderdate &gt;= DATE &#39;1996-10-01&#39;
       GROUP BY o.o_orderpriority
       ORDER BY o.o_orderpriority;
 </code></pre></div>
-<h2 id="5.-leverage-standard-bi-tools">5. Leverage standard BI tools</h2>
+<h2 id="5-leverage-standard-bi-tools">5. Leverage standard BI tools</h2>
 
 <p>Drill works with standard BI tools. You can use your existing tools, such as Tableau,
MicroStrategy, QlikView and Excel. </p>
 
-<h2 id="6.-interactive-queries-on-hive-tables">6. Interactive queries on Hive tables</h2>
+<h2 id="6-interactive-queries-on-hive-tables">6. Interactive queries on Hive tables</h2>
 
 <p>Apache Drill lets you leverage your investments in Hive. You can run interactive
queries with Drill on your Hive tables and access all Hive input/output formats (including
custom SerDes). You can join tables associated with different Hive metastores, and you can
join a Hive table with an HBase table or a directory of log files. Here&#39;s a simple
query in Drill on a Hive table:</p>
 <div class="highlight"><pre><code class="language-text" data-lang="text">SELECT
`month`, state, sum(order_total) AS sales
@@ -1106,7 +1102,7 @@ FROM hive.orders
 GROUP BY `month`, state
 ORDER BY 3 DESC LIMIT 5;
 </code></pre></div>
-<h2 id="7.-access-multiple-data-sources">7. Access multiple data sources</h2>
+<h2 id="7-access-multiple-data-sources">7. Access multiple data sources</h2>
 
 <p>Drill is extensible. You can connect Drill out-of-the-box to file systems (local
or distributed, such as S3 and HDFS), HBase and Hive. You can implement a storage plugin to
make Drill work with any other data source. Drill can combine data from multiple data sources
on the fly in a single query, with no centralized metadata definitions. Here&#39;s a query
that combines data from a Hive table, an HBase table (view) and a JSON file:</p>
 <div class="highlight"><pre><code class="language-text" data-lang="text">SELECT
custview.membership, sum(orders.order_total) AS sales
@@ -1115,15 +1111,15 @@ WHERE orders.cust_id = custview.cust_id AND orders.cust_id = c.user_info.cust_id
 GROUP BY custview.membership
 ORDER BY 2;
 </code></pre></div>
-<h2 id="8.-user-defined-functions-(udfs)-for-drill-and-hive">8. User-Defined Functions
(UDFs) for Drill and Hive</h2>
+<h2 id="8-user-defined-functions-udfs-for-drill-and-hive">8. User-Defined Functions
(UDFs) for Drill and Hive</h2>
 
 <p>Drill exposes a simple, high-performance Java API to build <a href="/docs/develop-custom-functions/">custom
user-defined functions</a> (UDFs) for adding your own business logic to Drill.  Drill
also supports Hive UDFs. If you have already built UDFs in Hive, you can reuse them with Drill
with no modifications. </p>
 
-<h2 id="9.-high-performance">9. High performance</h2>
+<h2 id="9-high-performance">9. High performance</h2>
 
 <p>Drill is designed from the ground up for high throughput and low latency. It doesn&#39;t
use a general purpose execution engine like MapReduce, Tez or Spark. As a result, Drill is
flexible (schema-free JSON model) and performant. Drill&#39;s optimizer leverages rule-
and cost-based techniques, as well as data locality and operator push-down, which is the capability
to push down query fragments into the back-end data sources. Drill also provides a columnar
and vectorized execution engine, resulting in higher memory and CPU efficiency.</p>
 
-<h2 id="10.-scales-from-a-single-laptop-to-a-1000-node-cluster">10. Scales from a single
laptop to a 1000-node cluster</h2>
+<h2 id="10-scales-from-a-single-laptop-to-a-1000-node-cluster">10. Scales from a single
laptop to a 1000-node cluster</h2>
 
 <p>Drill is available as a simple download you can run on your laptop. When you&#39;re
ready to analyze larger datasets, deploy Drill on your Hadoop cluster (up to 1000 commodity
servers). Drill leverages the aggregate memory in the cluster to execute queries using an
optimistic pipelined model, and automatically spills to disk when the working set doesn&#39;t
fit in memory.</p>
 

http://git-wip-us.apache.org/repos/asf/drill-site/blob/f06d8933/docs/wikipedia-edit-history/index.html
----------------------------------------------------------------------
diff --git a/docs/wikipedia-edit-history/index.html b/docs/wikipedia-edit-history/index.html
index f0a948d..0dd5b85 100644
--- a/docs/wikipedia-edit-history/index.html
+++ b/docs/wikipedia-edit-history/index.html
@@ -373,10 +373,6 @@
             
           
             
-              <li class="toctree-l2"><a class="reference internal" href="/docs/mapr-db-format/">MapR-DB
Format</a></li>
-            
-          
-            
               <li class="toctree-l2"><a class="reference internal" href="/docs/s3-storage-plugin/">S3
Storage Plugin</a></li>
             
           

http://git-wip-us.apache.org/repos/asf/drill-site/blob/f06d8933/docs/with-clause/index.html
----------------------------------------------------------------------
diff --git a/docs/with-clause/index.html b/docs/with-clause/index.html
index a8e1e84..a9c9916 100644
--- a/docs/with-clause/index.html
+++ b/docs/with-clause/index.html
@@ -373,10 +373,6 @@
             
           
             
-              <li class="toctree-l2"><a class="reference internal" href="/docs/mapr-db-format/">MapR-DB
Format</a></li>
-            
-          
-            
               <li class="toctree-l2"><a class="reference internal" href="/docs/s3-storage-plugin/">S3
Storage Plugin</a></li>
             
           

http://git-wip-us.apache.org/repos/asf/drill-site/blob/f06d8933/docs/workspaces/index.html
----------------------------------------------------------------------
diff --git a/docs/workspaces/index.html b/docs/workspaces/index.html
index 5050b32..f15c909 100644
--- a/docs/workspaces/index.html
+++ b/docs/workspaces/index.html
@@ -373,10 +373,6 @@
             
           
             
-              <li class="toctree-l2"><a class="reference internal" href="/docs/mapr-db-format/">MapR-DB
Format</a></li>
-            
-          
-            
               <li class="toctree-l2"><a class="reference internal" href="/docs/s3-storage-plugin/">S3
Storage Plugin</a></li>
             
           
@@ -1097,7 +1093,7 @@ location of the data:</p>
 
 <p><code>&lt;plugin&gt;.&lt;workspace name&gt;.`&lt;location&gt;</code>`
 </p>
 
-<h2 id="overriding-dfs.default">Overriding <code>dfs.default</code></h2>
+<h2 id="overriding-dfs-default">Overriding <code>dfs.default</code></h2>
 
 <p>You may want to override the hidden default workspace in scenarios where users do
not have permissions to access the root directory. 
 Add the following workspace entry to the <code>dfs</code> storage plugin configuration
to override the default workspace:</p>

http://git-wip-us.apache.org/repos/asf/drill-site/blob/f06d8933/faq/index.html
----------------------------------------------------------------------
diff --git a/faq/index.html b/faq/index.html
index db5a1c7..3d0d5a2 100644
--- a/faq/index.html
+++ b/faq/index.html
@@ -115,11 +115,11 @@
 
 <div class="int_text" align="left"><h2 id="overview">Overview</h2>
 
-<h3 id="why-drill?">Why Drill?</h3>
+<h3 id="why-drill">Why Drill?</h3>
 
 <p>The 40-year monopoly of the RDBMS is over. With the exponential growth of data in
recent years, and the shift towards rapid application development, new data is increasingly
being stored in non-relational datastores including Hadoop, NoSQL and cloud storage. Apache
Drill enables analysts, business users, data scientists and developers to explore and analyze
this data without sacrificing the flexibility and agility offered by these datastores. Drill
processes the data in-situ without requiring users to define schemas or transform data.</p>
 
-<h3 id="what-are-some-of-drill&#39;s-key-features?">What are some of Drill&#39;s
key features?</h3>
+<h3 id="what-are-some-of-drill-39-s-key-features">What are some of Drill&#39;s
key features?</h3>
 
 <p>Drill is an innovative distributed SQL engine designed to enable data exploration
and analytics on non-relational datastores. Users can query the data using standard SQL and
BI tools without having to create and manage schemas. Some of the key features are:</p>
 
@@ -130,7 +130,7 @@
 <li>Pluggable architecture enables connectivity to multiple datastores</li>
 </ul>
 
-<h3 id="how-does-drill-achieve-performance?">How does Drill achieve performance?</h3>
+<h3 id="how-does-drill-achieve-performance">How does Drill achieve performance?</h3>
 
 <p>Drill is built from the ground up to achieve high throughput and low latency. The
following capabilities help accomplish that:</p>
 
@@ -142,7 +142,7 @@
 <li><strong>Optimistic/pipelined execution</strong>: Drill is able to stream
data in memory between operators. Drill minimizes the use of disks unless needed to complete
the query.</li>
 </ul>
 
-<h3 id="what-datastores-does-drill-support?">What datastores does Drill support?</h3>
+<h3 id="what-datastores-does-drill-support">What datastores does Drill support?</h3>
 
 <p>Drill is primarily focused on non-relational datastores, including Hadoop, NoSQL
and cloud storage. The following datastores are currently supported:</p>
 
@@ -154,7 +154,7 @@
 
 <p>A new datastore can be added by developing a storage plugin. Drill&#39;s unique
schema-free JSON data model enables it to query non-relational datastores in-situ (many of
these systems store complex or schema-free data).</p>
 
-<h3 id="what-clients-are-supported?">What clients are supported?</h3>
+<h3 id="what-clients-are-supported">What clients are supported?</h3>
 
 <ul>
 <li><strong>BI tools</strong> via the ODBC and JDBC drivers (eg, Tableau,
Excel, MicroStrategy, Spotfire, QlikView, Business Objects)</li>
@@ -164,7 +164,7 @@
 
 <h2 id="comparisons">Comparisons</h2>
 
-<h3 id="is-drill-a-&#39;sql-on-hadoop&#39;-engine?">Is  Drill a &#39;SQL-on-Hadoop&#39;
engine?</h3>
+<h3 id="is-drill-a-39-sql-on-hadoop-39-engine">Is  Drill a &#39;SQL-on-Hadoop&#39;
engine?</h3>
 
 <p>Drill supports a variety of non-relational datastores in addition to Hadoop. Drill
takes a different approach compared to traditional SQL-on-Hadoop technologies like Hive and
Impala. For example, users can directly query self-describing data (eg, JSON, Parquet) without
having to create and manage schemas.</p>
 
@@ -219,11 +219,11 @@
 </tr>
 </tbody></table>
 
-<h3 id="is-spark-sql-similar-to-drill?">Is Spark SQL similar to Drill?</h3>
+<h3 id="is-spark-sql-similar-to-drill">Is Spark SQL similar to Drill?</h3>
 
 <p>No. Spark SQL is primarily designed to enable developers to incorporate SQL statements
in Spark programs. Drill does not depend on Spark, and is targeted at business users, analysts,
data scientists and developers. </p>
 
-<h3 id="does-drill-replace-hive?">Does Drill replace Hive?</h3>
+<h3 id="does-drill-replace-hive">Does Drill replace Hive?</h3>
 
 <p>Hive is a batch processing framework most suitable for long-running jobs. For data
exploration and BI, Drill provides a much better experience than Hive.</p>
 
@@ -231,7 +231,7 @@
 
 <h2 id="metadata">Metadata</h2>
 
-<h3 id="how-does-drill-support-queries-on-self-describing-data?">How does Drill support
queries on self-describing data?</h3>
+<h3 id="how-does-drill-support-queries-on-self-describing-data">How does Drill support
queries on self-describing data?</h3>
 
 <p>Drill&#39;s flexible JSON data model and on-the-fly schema discovery enable
it to query self-describing data.</p>
 
@@ -240,11 +240,11 @@
 <li><strong>On-the-fly schema discovery (or late binding)</strong>: Traditional
query engines (eg, relational databases, Hive, Impala, Spark SQL) need to know the structure
of the data before query execution. Drill, on the other hand, features a fundamentally different
architecture, which enables execution to begin without knowing the structure of the data.
The query is automatically compiled and re-compiled during the execution phase, based on the
actual data flowing through the system. As a result, Drill can handle data with evolving schema
or even no schema at all (eg, JSON files, MongoDB collections, HBase tables).</li>
 </ul>
 
-<h3 id="but-i-already-have-schemas-defined-in-hive-metastore?-can-i-use-that-with-drill?">But
I already have schemas defined in Hive Metastore? Can I use that with Drill?</h3>
+<h3 id="but-i-already-have-schemas-defined-in-hive-metastore-can-i-use-that-with-drill">But
I already have schemas defined in Hive Metastore? Can I use that with Drill?</h3>
 
 <p>Absolutely. Drill has a storage plugin for Hive tables, so you can simply point
Drill to the Hive Metastore and start performing low-latency queries on Hive tables. In fact,
a single Drill cluster can query data from multiple Hive Metastores, and even perform joins
across these datasets.</p>
 
-<h3 id="is-drill-&quot;anti-schema&quot;-or-&quot;anti-dba&quot;?">Is
Drill &quot;anti-schema&quot; or &quot;anti-DBA&quot;?</h3>
+<h3 id="is-drill-quot-anti-schema-quot-or-quot-anti-dba-quot">Is Drill &quot;anti-schema&quot;
or &quot;anti-DBA&quot;?</h3>
 
 <p>Not at all. Drill actually takes advantage of schemas when available. For example,
Drill leverages the schema information in Hive when querying Hive tables. However, when querying
schema-free datastores like MongoDB, or raw files on S3 or Hadoop, schemas are not available,
and Drill is still able to query that data.</p>
 
@@ -258,7 +258,7 @@
 
 <p>Drill is all about flexibility. The flexible schema management capabilities in Drill
allow users to explore raw data and then create models/structure with <code>CREATE TABLE</code>
or <code>CREATE VIEW</code> statements, or with Hive Metastore.</p>
 
-<h3 id="what-does-a-drill-query-look-like?">What does a Drill query look like?</h3>
+<h3 id="what-does-a-drill-query-look-like">What does a Drill query look like?</h3>
 
 <p>Drill uses a decentralized metadata model and relies on its storage plugins to provide
metadata. There is a storage plugin associated with each data source that is supported by
Drill.</p>
 
@@ -269,25 +269,25 @@
 <span class="k">SELECT</span> <span class="o">*</span> <span class="k">FROM</span>
<span class="n">hive1</span><span class="p">.</span><span class="n">logs</span><span
class="p">.</span><span class="n">frontend</span><span class="p">;</span>
 <span class="k">SELECT</span> <span class="o">*</span> <span class="k">FROM</span>
<span class="n">hbase1</span><span class="p">.</span><span class="n">events</span><span
class="p">.</span><span class="n">clicks</span><span class="p">;</span>
 </code></pre></div>
-<h3 id="what-sql-functionality-does-drill-support?">What SQL functionality does Drill
support?</h3>
+<h3 id="what-sql-functionality-does-drill-support">What SQL functionality does Drill
support?</h3>
 
 <p>Drill supports standard SQL (aka ANSI SQL). In addition, it features several extensions
that help with complex data, such as the <code>KVGEN</code> and <code>FLATTEN</code>
functions. For more details, refer to the <a href="/docs/sql-reference/">SQL Reference</a>.</p>
 
-<h3 id="do-i-need-to-load-data-into-drill-to-start-querying-it?">Do I need to load
data into Drill to start querying it?</h3>
+<h3 id="do-i-need-to-load-data-into-drill-to-start-querying-it">Do I need to load data
into Drill to start querying it?</h3>
 
 <p>No. Drill can query data &#39;in-situ&#39;.</p>
 
 <h2 id="getting-started">Getting Started</h2>
 
-<h3 id="what-is-the-best-way-to-get-started-with-drill?">What is the best way to get
started with Drill?</h3>
+<h3 id="what-is-the-best-way-to-get-started-with-drill">What is the best way to get
started with Drill?</h3>
 
 <p>The best way to get started is to try it out. It only takes a few minutes and all
you need is a laptop (Mac, Windows or Linux). We&#39;ve compiled <a href="/docs/tutorials-introduction/">several
tutorials</a> to help you get started.</p>
 
-<h3 id="how-can-i-ask-questions-and-provide-feedback?">How can I ask questions and
provide feedback?</h3>
+<h3 id="how-can-i-ask-questions-and-provide-feedback">How can I ask questions and provide
feedback?</h3>
 
 <p>Please post your questions and feedback to <a href="mailto:user@drill.apache.org">user@drill.apache.org</a>.
We are happy to help!</p>
 
-<h3 id="how-can-i-contribute-to-drill?">How can I contribute to Drill?</h3>
+<h3 id="how-can-i-contribute-to-drill">How can I contribute to Drill?</h3>
 
 <p>The documentation has information on <a href="/docs/contribute-to-drill/">how
to contribute</a>.</p>
 </div>

http://git-wip-us.apache.org/repos/asf/drill-site/blob/f06d8933/feed.xml
----------------------------------------------------------------------
diff --git a/feed.xml b/feed.xml
index 8a48d33..4296900 100644
--- a/feed.xml
+++ b/feed.xml
@@ -6,8 +6,8 @@
 </description>
     <link>/</link>
     <atom:link href="/feed.xml" rel="self" type="application/rss+xml"/>
-    <pubDate>Tue, 15 Dec 2015 21:09:41 -0800</pubDate>
-    <lastBuildDate>Tue, 15 Dec 2015 21:09:41 -0800</lastBuildDate>
+    <pubDate>Thu, 17 Dec 2015 17:44:03 -0800</pubDate>
+    <lastBuildDate>Thu, 17 Dec 2015 17:44:03 -0800</lastBuildDate>
     <generator>Jekyll v2.5.3</generator>
     
       <item>
@@ -254,7 +254,7 @@ Jacques Nadeau&lt;/p&gt;
   &amp;lt;version&amp;gt;1.1.0&amp;lt;/version&amp;gt;
 &amp;lt;/dependency&amp;gt;
 &lt;/code&gt;&lt;/pre&gt;&lt;/div&gt;
-&lt;h2 id=&quot;mongodb-3.0-support&quot;&gt;MongoDB 3.0 Support&lt;/h2&gt;
+&lt;h2 id=&quot;mongodb-3-0-support&quot;&gt;MongoDB 3.0 Support&lt;/h2&gt;
 
 &lt;p&gt;Drill now uses MongoDB&amp;#39;s latest Java driver and has enhanced
connection pooling for better performance and resilience in large-scale deployments.  Learn
more about using the &lt;a href=&quot;https://drill.apache.org/docs/mongodb-plugin-for-apache-drill/&quot;&gt;MongoDB
plugin&lt;/a&gt;.&lt;/p&gt;
 


Mime
View raw message