apache · jnturton · Dec 10, 2020 · Aug 9, 2020 · Aug 9, 2020 · Aug 9, 2020
diff --git a/README.md b/README.md
@@ -16,7 +16,7 @@ Please make sure that specific versions of libraries are installed since buildin
 
 # Documentation Guidelines
 
-The documentation pages are placed under `_docs`. You can modify existing .md files, or you can create new .md files to add to the Apache Drill documentation site. Create pull requests to submit your documentation updates. 
+The documentation pages are placed under `_docs`. You can modify existing .md files, or you can create new .md files to add to the Apache Drill documentation site. Create pull requests to submit your documentation updates. The Kramdown MarkDown processor employed by Jekyll supports [a dialect of MarkDown](https://kramdown.gettalong.org/quickref.html) which is a superset of standard MarkDown.
 
 ## Creating New MarkDown Files
 

diff --git a/_config.yml b/_config.yml
@@ -11,25 +11,25 @@ description: > # this means to ignore newlines until "baseurl:"
 
 baseurl: "/drill" # Base URL when hosted on GitHub Pages (drill repository under apache account)
 noindex: 1
-markdown: redcarpet
 
-redcarpet:
-  extensions: ["no_intra_emphasis", "fenced_code_blocks", "autolink", "tables", "with_toc_data"]
+# Uncomment to use the redcarpet Markdown processor (not supported by GH Pages) instead of Kramdown
+#markdown: redcarpet
+#redcarpet:
+#  extensions: ["no_intra_emphasis", "fenced_code_blocks", "autolink", "tables", "with_toc_data"]
 
 collections:
   docs:
     output: true
-    permalink: /docs/:title/
+    permalink: /docs/:slug/
 
 defaults:
-  -
-    scope:
+  - scope:
       type: docs # This defines the default for anything in the docs collection. An alternative would be to use "path: _docs" here.
     values:
       layout: docpage
 
 sass:
   style: :compressed
 
-gems:
+plugins:
   - jekyll-redirect-from
diff --git a/_data/authors.json b/_data/authors.json
@@ -40,5 +40,11 @@
      "title": "Committer",
      "org": "MapR Technologies",
      "email": "bbevens@mapr.com"
+   },
+   "agirish": {
+     "name": "Abhishek Girish",
+     "title": "Committer",
+     "org": "MapR Technologies",
+     "email": "agirish@mapr.com"
    }
   }
diff --git a/_data/docs.json b/_data/docs.json
diff --git a/_docs/010-getting-started.md b/_docs/010-getting-started.md
@@ -1,3 +1,4 @@
 ---
 title: "Getting Started"
+slug: "Getting Started"
 ---
diff --git a/_docs/020-architecture.md b/_docs/020-architecture.md
@@ -1,3 +1,4 @@
 ---
 title: "Architecture"
+slug: "Architecture"
 ---
diff --git a/_docs/030-tutorials.md b/_docs/030-tutorials.md
@@ -1,4 +1,5 @@
 ---
 title: "Tutorials"
+slug: "Tutorials"
 nocontent: true
 ---
diff --git a/_docs/031-drill-on-yarn.md b/_docs/031-drill-on-yarn.md
@@ -1,4 +1,5 @@
 ---
 title: "Drill-on-YARN"
+slug: "Drill-on-YARN"
 nocontent: true
 ---
diff --git a/_docs/040-install-drill.md b/_docs/040-install-drill.md
@@ -1,5 +1,6 @@
 ---
 title: "Install Drill"
+slug: "Install Drill"
 ---
 
 

diff --git a/_docs/045-configure-drill.md b/_docs/045-configure-drill.md
@@ -1,5 +1,6 @@
 ---
 title: "Configure Drill"
+slug: "Configure Drill"
 ---
 
 

diff --git a/_docs/050-connect-a-data-source.md b/_docs/050-connect-a-data-source.md
@@ -1,3 +1,4 @@
 ---
 title: "Connect a Data Source"
+slug: "Connect a Data Source"
 ---
diff --git a/_docs/060-odbc-jdbc-interfaces.md b/_docs/060-odbc-jdbc-interfaces.md
@@ -1,3 +1,4 @@
 ---
 title: "ODBC/JDBC Interfaces"
+slug: "ODBC/JDBC Interfaces"
 ---
diff --git a/_docs/070-query-data.md b/_docs/070-query-data.md
@@ -1,5 +1,6 @@
 ---
 title: "Query Data"
+slug: "Query Data"
 ---
 
 
diff --git a/_docs/072-performance-tuning.md b/_docs/072-performance-tuning.md
@@ -1,5 +1,6 @@
 ---
 title: "Performance Tuning"
+slug: "Performance Tuning"
 ---
 
 
diff --git a/_docs/073-log-and-debug.md b/_docs/073-log-and-debug.md
@@ -1,3 +1,4 @@
 ---
 title: "Log and Debug"
+slug: "Log and Debug"
 ---
diff --git a/_docs/080-sql-reference.md b/_docs/080-sql-reference.md
@@ -1,3 +1,4 @@
 ---
 title: "SQL Reference"
+slug: "SQL Reference"
 ---
diff --git a/_docs/090-data-sources-and-file-formats.md b/_docs/090-data-sources-and-file-formats.md
@@ -1,5 +1,6 @@
 ---
 title: "Data Sources and File Formats"
+slug: "Data Sources and File Formats"
 ---
 
 

diff --git a/_docs/100-develop-custom-functions.md b/_docs/100-develop-custom-functions.md
@@ -1,4 +1,5 @@
 ---
 title: "Develop Custom Functions"
+slug: "Develop Custom Functions"
 ---
 
diff --git a/_docs/110-troubleshooting.md b/_docs/110-troubleshooting.md
@@ -1,6 +1,6 @@
 ---
 title: "Troubleshooting"
-date: 2017-02-24 22:12:36 UTC
+slug: "Troubleshooting"
 ---
 
 You may experience certain known issues when using Drill. This document lists some known issues and resolutions for each.
@@ -182,8 +182,10 @@ Turn on ODBC driver debug logging to better understand failure.
 ### JDBC/ODBC Connection Issues with ZooKeeper
 
 Symptom: Client cannot resolve ZooKeeper host names for JDBC/ODBC.
+Symptom: "IllegalStateException: No active Drillbit endpoint found from ZooKeeper. Check connection parameters?" 
+
+Solution: Ensure that Zookeeper is up and running. Verify that Drill has the correct `drill-override.conf` settings for the Zookeeper quorum.  If `cluster-id` in file drill-override.conf is not the default value, it must be specified in the JDBC connection string.  See [Using the JDBC Driver]({{ site.baseurl }}/docs/using-the-jdbc-driver/).
 
-Solution: Ensure that Zookeeper is up and running. Verify that Drill has the correct `drill-override.conf` settings for the Zookeeper quorum.
 
 ### Metadata Queries Take a Long Time to Return
 

diff --git a/_docs/120-developer-information.md b/_docs/120-developer-information.md
@@ -1,5 +1,6 @@
 ---
 title: "Developer Information"
+slug: "Developer Information"
 ---
 
 
diff --git a/_docs/130-rn.md b/_docs/130-rn.md
@@ -1,3 +1,4 @@
 ---
 title: "Release Notes"
+slug: "Release Notes"
 ---
diff --git a/_docs/140-sample-datasets.md b/_docs/140-sample-datasets.md
@@ -1,3 +1,4 @@
 ---
 title: "Sample Datasets"
+slug: "Sample Datasets"
 ---
diff --git a/_docs/170-bylaws.md b/_docs/170-bylaws.md
@@ -1,6 +1,6 @@
 ---
 title: "Project Bylaws"
-date: 2018-11-02
+slug: "Project Bylaws"
 ---
 ## Introduction
 

diff --git a/_docs/171-ecosystem.md b/_docs/171-ecosystem.md
@@ -1,5 +1,6 @@
 ---
 title: "Ecosystem"
+slug: "Ecosystem"
 ---
 
 
diff --git a/_docs/architecture/010-architecture-introduction.md b/_docs/architecture/010-architecture-introduction.md
@@ -1,6 +1,7 @@
 ---
 title: "Architecture Introduction"
-date: 2018-12-08
+slug: "Architecture Introduction"
+slug: "Architecture Introduction"
 parent: "Architecture"
 ---
 Apache Drill is a low latency distributed query engine for large-scale

diff --git a/_docs/architecture/015-drill-query-execution.md b/_docs/architecture/015-drill-query-execution.md
@@ -1,32 +1,32 @@
 ---
 title: "Drill Query Execution"
-date: 2018-12-08
+slug: "Drill Query Execution"
 parent: "Architecture"
 ---
 
 When you submit a Drill query, a client or an application sends the query in the form of an SQL statement to a Drillbit in the Drill cluster. A Drillbit is the process running on each active Drill node that coordinates, plans, and executes queries, as well as distributes query work across the cluster to maximize data locality.
 
 The following image represents the communication between clients, applications, and Drillbits:
 
-![]({{ site.baseurl }}/docs/img/query-flow-client.png)
+![]({{ site.baseurl }}/images/docs/query-flow-client.png)
 
 The Drillbit that receives the query from a client or application becomes the Foreman for the query and drives the entire query. A parser in the Foreman parses the SQL, applying custom rules to convert specific SQL operators into a specific logical operator syntax that Drill understands. This collection of logical operators forms a logical plan. The logical plan describes the work required to generate the query results and defines which data sources and operations to apply.
 
 The Foreman sends the logical plan into a cost-based optimizer to optimize the order of SQL operators in a statement and read the logical plan. The optimizer applies various types of rules to rearrange operators and functions into an optimal plan. The optimizer converts the logical plan into a physical plan that describes how to execute the query.
 
-![]({{ site.baseurl }}/docs/img/client-phys-plan.png)
+![]({{ site.baseurl }}/images/docs/client-phys-plan.png)
 
 A parallelizer in the Foreman transforms the physical plan into multiple phases, called major and minor fragments. These fragments create a multi-level execution tree that rewrites the query and executes it in parallel against the configured data sources, sending the results back to the client or application.
 
-![]({{ site.baseurl }}/docs/img/execution-tree.PNG)  
+![]({{ site.baseurl }}/images/docs/execution-tree.PNG)  
 
 
 ## Major Fragments
 A major fragment is a concept that represents a phase of the query execution. A phase can consist of one or multiple operations that Drill must perform to execute the query. Drill assigns each major fragment a MajorFragmentID.
 
 For example, to perform a hash aggregation of two files, Drill may create a plan with two major phases (major fragments) where the first phase is dedicated to scanning the two files and the second phase is dedicated to the aggregation of the data.  
 
-![]({{ site.baseurl }}/docs/img/ex-operator.png)
+![]({{ site.baseurl }}/images/docs/ex-operator.png)
 
 Drill uses an exchange operator to separate major fragments. An exchange is a change in data location and/or parallelization of the physical plan. An exchange is composed of a sender and a receiver to allow data to move between nodes. 
 
@@ -37,15 +37,15 @@ You can work with major fragments within the physical plan by capturing a JSON r
 ## Minor Fragments
 Each major fragment is parallelized into minor fragments. A minor fragment is a logical unit of work that runs inside a thread. A logical unit of work in Drill is also referred to as a slice. The execution plan that Drill creates is composed of minor fragments. Drill assigns each minor fragment a MinorFragmentID.  
 
-![]({{ site.baseurl }}/docs/img/min-frag.png)
+![]({{ site.baseurl }}/images/docs/min-frag.png)
 
 The parallelizer in the Foreman creates one or more minor fragments from a major fragment at execution time, by breaking a major fragment into as many minor fragments as it can usefully run at the same time on the cluster.
 
 Drill executes each minor fragment in its own thread as quickly as possible based on its upstream data requirements. Drill schedules the minor fragments on nodes with data locality. Otherwise, Drill schedules them in a round-robin fashion on the existing, available Drillbits.
 
 Minor fragments contain one or more relational operators. An operator performs a relational operation, such as scan, filter, join, or group by. Each operator has a particular operator type and an OperatorID. Each OperatorID defines its relationship within the minor fragment to which it belongs. See [Physical Operators]({{ site.baseurl }}/docs/physical-operators/).
 
-![]({{ site.baseurl }}/docs/img/operators.png)
+![]({{ site.baseurl }}/images/docs/operators.png)
 
 For example, when performing a hash aggregation of two files, Drill breaks the first phase dedicated to scanning into two minor fragments. Each minor fragment contains scan operators that scan the files. Drill breaks the second phase dedicated to aggregation into four minor fragments. Each of the four minor fragments contain hash aggregate operators that perform the hash  aggregation operations on the data. 
 
@@ -60,7 +60,7 @@ Intermediate fragments start work when data is available or fed to them from oth
 
 The leaf fragments scan tables in parallel and communicate with the storage layer or access data on local disk. The leaf fragments pass partial results to the intermediate fragments, which perform parallel operations on intermediate results.  
 
-![]({{ site.baseurl }}/docs/img/leaf-frag.png)    
+![]({{ site.baseurl }}/images/docs/leaf-frag.png)    
 
 Drill only plans queries that have concurrent running fragments. For example, if 20 available slices exist in the cluster, Drill plans a query that runs no more than 20 minor fragments in a particular major fragment. Drill is optimistic and assumes that it can complete all of the work in parallel. All minor fragments for a particular major fragment start at the same time based on their upstream data dependency.
 
diff --git a/_docs/architecture/020-core-modules.md b/_docs/architecture/020-core-modules.md
@@ -1,11 +1,11 @@
 ---
 title: "Core Modules"
-date: 2018-11-02
+slug: "Core Modules"
 parent: "Architecture"
 ---
 The following image represents components within each Drillbit:
 
-![drill query flow]({{ site.baseurl }}/docs/img/DrillbitModules.png)
+![drill query flow]({{ site.baseurl }}/images/docs/DrillbitModules.png)
 
 The following list describes the key components of a Drillbit:
 

diff --git a/_docs/architecture/030-performance.md b/_docs/architecture/030-performance.md
@@ -1,6 +1,6 @@
 ---
 title: "Performance"
-date: 2018-11-02
+slug: "Performance"
 parent: "Architecture"
 ---
 Drill is designed from the ground up for high performance on large datasets.
@@ -42,7 +42,7 @@ generates highly efficient custom code for every single query.
 The following image shows the Drill compilation/code generation
 process:
 
-![drill compiler]({{ site.baseurl }}/docs/img/58.png)
+![drill compiler]({{ site.baseurl }}/images/docs/58.png)
 
 **_Optimistic and pipelined query execution_**
 

diff --git a/_docs/configure-drill/010-configure-drill-introduction.md b/_docs/configure-drill/010-configure-drill-introduction.md
@@ -1,6 +1,6 @@
 ---
 title: "Configure Drill Introduction"
-date: 2018-12-08
+slug: "Configure Drill Introduction"
 parent: "Configure Drill"
 ---
 

diff --git a/_docs/configure-drill/020-configuring-drill-memory.md b/_docs/configure-drill/020-configuring-drill-memory.md
@@ -1,6 +1,6 @@
 ---
 title: "Configuring Drill Memory"
-date: 2018-03-26 17:37:50 UTC
+slug: "Configuring Drill Memory"
 parent: "Configure Drill"
 ---
 
@@ -90,7 +90,7 @@ Additionally, if the available free memory is less than the allocation, the foll
        [WARN] Drillbit will start up, but can potentially crash due to oversubscribing of system memory.  
 
 
-##Modifying Memory Allocated to Queries  
+## Modifying Memory Allocated to Queries  
 
 You can configure the amount of memory that Drill allocates to each query as a hard limit or a percentage of the total direct memory. The `planner.memory.max_query_memory_per_node` and `planner.memory.percent_per_query` options set the amount of memory that Drill can allocate to a query on a node. Both options are enabled by default. Of these two options, Drill picks the setting that provides the most memory. For more information about these options, see [Sort-Based and Hash-Based Memory Constrained Operators](https://drill.apache.org/docs/sort-based-and-hash-based-memory-constrained-operators/).  
 
@@ -109,7 +109,7 @@ Use the ALTER SYSTEM SET command to change the settings, as shown:
 
        ALTER SYSTEM SET `drill.exec.memory.operator.output_batch_size` = <value>;  
 
-##Bounds Checking 
+## Bounds Checking 
 
 If performance is an issue, add -Dbounds=false, as shown in the following example:
 

diff --git a/_docs/configure-drill/030-configuring-a-multitenant-cluster-introduction.md b/_docs/configure-drill/030-configuring-a-multitenant-cluster-introduction.md
@@ -1,6 +1,6 @@
 ---
 title: "Configuring a Multitenant Cluster Introduction"
-date: 2016-11-21 21:27:46 UTC
+slug: "Configuring a Multitenant Cluster Introduction"
 parent: "Configuring a Multitenant Cluster"
 ---
 

diff --git a/_docs/configure-drill/031-securing-drill.md b/_docs/configure-drill/031-securing-drill.md
@@ -1,5 +1,6 @@
 ---
 title: "Securing Drill"
+slug: "Securing Drill"
 parent: "Configure Drill"
 ---
 

diff --git a/_docs/configure-drill/040-configuring-a-multitenant-cluster.md b/_docs/configure-drill/040-configuring-a-multitenant-cluster.md
@@ -1,5 +1,6 @@
 ---
 title: "Configuring a Multitenant Cluster"
+slug: "Configuring a Multitenant Cluster"
 parent: "Configure Drill"
 ---
 
diff --git a/_docs/configure-drill/050-configuring-multitenant-resources.md b/_docs/configure-drill/050-configuring-multitenant-resources.md
@@ -1,6 +1,6 @@
 ---
 title: "Configuring Multitenant Resources"
-date: 2015-12-29 01:12:25 UTC
+slug: "Configuring Multitenant Resources"
 parent: "Configuring a Multitenant Cluster"
 ---
 Drill operations are memory and CPU-intensive. Currently, Drill resources are managed outside of any cluster management service. In a multitenant or any other type of cluster, YARN-enabled or not, you configure memory and memory usage limits for Drill by modifying the `drill-env.sh` file as described in ["Configuring Drill Memory"]({{site.baseurl}}/docs/configuring-drill-memory).

diff --git a/_docs/configure-drill/060-configuring-a-shared-drillbit.md b/_docs/configure-drill/060-configuring-a-shared-drillbit.md
@@ -1,11 +1,11 @@
 ---
 title: "Configuring Resources for a Shared Drillbit"
-date: 2016-11-21 22:42:10 UTC
+slug: "Configuring Resources for a Shared Drillbit"
 parent: "Configuring a Multitenant Cluster"
 ---
 To manage a cluster in which multiple users share a Drillbit, you configure Drill queuing and parallelization in addition to memory, as described in the previous section, ["Configuring Drill Memory"]({{site.baseurl}}/docs/configuring-drill-memory/).
 
-##Configuring Query Queuing
+## Configuring Query Queuing
 
 Set [options in sys.options]({{site.baseurl}}/docs/configuration-options-introduction/) to enable and manage query queuing, which is turned off by default. There are two types of queues: large and small. You configure a maximum number of queries that each queue allows by configuring the following options in the `sys.options` table:
 

diff --git a/_docs/configure-drill/080-configuration-options.md b/_docs/configure-drill/080-configuration-options.md
@@ -1,5 +1,6 @@
 ---
 title: "Configuration Options"
+slug: "Configuration Options"
 parent: "Configure Drill"
 ---
 

diff --git a/_docs/configure-drill/100-ports-used-by-drill.md b/_docs/configure-drill/100-ports-used-by-drill.md
@@ -1,6 +1,6 @@
 ---
 title: "Ports Used by Drill"
-date: 2018-12-08
+slug: "Ports Used by Drill"
 parent: "Configure Drill"
 ---