drill-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From bridg...@apache.org
Subject [1/2] drill git commit: web ui > web console
Date Thu, 17 Sep 2015 00:02:10 GMT
Repository: drill
Updated Branches:
  refs/heads/gh-pages 51371a290 -> bd2ec74a3


web ui > web console


Project: http://git-wip-us.apache.org/repos/asf/drill/repo
Commit: http://git-wip-us.apache.org/repos/asf/drill/commit/010ae6a6
Tree: http://git-wip-us.apache.org/repos/asf/drill/tree/010ae6a6
Diff: http://git-wip-us.apache.org/repos/asf/drill/diff/010ae6a6

Branch: refs/heads/gh-pages
Commit: 010ae6a6fe88968fc8ba0b0110ddaa3a85ea38d2
Parents: 51371a2
Author: Kristine Hahn <khahn@maprtech.com>
Authored: Wed Sep 16 16:51:01 2015 -0700
Committer: Kristine Hahn <khahn@maprtech.com>
Committed: Wed Sep 16 16:51:01 2015 -0700

----------------------------------------------------------------------
 .../010-architecture-introduction.md            |   2 +-
 _docs/architecture/015-drill-query-execution.md |   4 +-
 .../010-configure-drill-introduction.md         |   2 +-
 .../070-configuring-user-impersonation.md       |   2 +-
 ...ser-impersonation-with-hive-authorization.md | 104 +++++++++----------
 ...-configuring-web-ui-and-rest-api-security.md |  36 +++----
 .../configure-drill/100-ports-used-by-drill.md  |   4 +-
 .../040-persistent-configuration-storage.md     |   4 +-
 .../020-storage-plugin-registration.md          |   6 +-
 .../035-plugin-configuration-basics.md          |   8 +-
 .../060-hbase-storage-plugin.md                 |   2 +-
 .../070-hive-storage-plugin.md                  |   8 +-
 .../080-drill-default-input-format.md           |   2 +-
 .../090-mongodb-plugin-for-apache-drill.md      |   6 +-
 _docs/install/060-starting-the-web-ui.md        |  18 ++--
 .../001-log-and-debug-introduction.md           |   2 +-
 _docs/log-and-debug/002-error-messages.md       |   4 +-
 .../010-interfaces-introduction.md              |   2 +-
 .../020-tableau-examples.md                     |   2 +-
 .../010-query-plans.md                          |   8 +-
 .../020-query-profiles.md                       |  12 +--
 _docs/query-data/070-query-sys-tbl.md           |   6 +-
 ...and-canceling-queries-in-the-Drill-Web-UI.md |  14 +--
 .../005-querying-complex-data-introduction.md   |   2 +-
 .../010-installing-the-apache-drill-sandbox.md  |   8 +-
 .../020-getting-to-know-the-drill-sandbox.md    |   2 +-
 .../030-lesson-1-learn-about-the-data-set.md    |   2 +-
 27 files changed, 136 insertions(+), 136 deletions(-)
----------------------------------------------------------------------


http://git-wip-us.apache.org/repos/asf/drill/blob/010ae6a6/_docs/architecture/010-architecture-introduction.md
----------------------------------------------------------------------
diff --git a/_docs/architecture/010-architecture-introduction.md b/_docs/architecture/010-architecture-introduction.md
index b802c72..0e055bc 100755
--- a/_docs/architecture/010-architecture-introduction.md
+++ b/_docs/architecture/010-architecture-introduction.md
@@ -35,7 +35,7 @@ See [Drill Query Execution]({{ site.baseurl }}/docs/drill-query-execution/).
 You can access Drill through the following interfaces:
 
   * [Drill shell]({{ site.baseurl }}/docs/configuring-the-drill-shell/)
-  * [Drill Web UI]({{ site.baseurl }}/docs/monitoring-and-canceling-queries-in-the-drill-web-ui)
+  * [Drill Web Console]({{ site.baseurl }}/docs/monitoring-and-canceling-queries-in-the-drill-web-ui)
   * [ODBC/JDBC]({{ site.baseurl }}/docs/interfaces-introduction/#using-odbc-to-access-apache-drill-from-bi-tools) 
   * C++ API
 

http://git-wip-us.apache.org/repos/asf/drill/blob/010ae6a6/_docs/architecture/015-drill-query-execution.md
----------------------------------------------------------------------
diff --git a/_docs/architecture/015-drill-query-execution.md b/_docs/architecture/015-drill-query-execution.md
index c88c476..d4828f8 100755
--- a/_docs/architecture/015-drill-query-execution.md
+++ b/_docs/architecture/015-drill-query-execution.md
@@ -31,7 +31,7 @@ Drill uses an exchange operator to separate major fragments. An exchange is a ch
 
 Major fragments do not actually perform any query tasks. Each major fragment is divided into one or multiple minor fragments (discussed in the next section) that actually execute the operations required to complete the query and return results back to the client.
 
-You can work with major fragments within the physical plan by capturing a JSON representation of the plan in a file, manually modifying it, and then submitting it back to Drill using the SUBMIT PLAN command. You can also view major fragments in the query profile, which is visible in the Drill Web UI. See [EXPLAIN ]({{ site.baseurl }}/docs/explain/)and [Query Profiles]({{ site.baseurl }}/docs/query-profiles/) for more information.
+You can work with major fragments within the physical plan by capturing a JSON representation of the plan in a file, manually modifying it, and then submitting it back to Drill using the SUBMIT PLAN command. You can also view major fragments in the query profile, which is visible in the Drill Web Console. See [EXPLAIN ]({{ site.baseurl }}/docs/explain/)and [Query Profiles]({{ site.baseurl }}/docs/query-profiles/) for more information.
 
 ## 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.  
@@ -48,7 +48,7 @@ Minor fragments contain one or more relational operators. An operator performs a
 
 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. 
 
-You cannot modify the number of minor fragments within the execution plan. However, you can view the query profile in the Drill Web UI and modify some configuration options that change the behavior of minor fragments, such as the maximum number of slices. See [Configuration Options]({{ site.baseurl }}/docs/configuration-options-introduction/).
+You cannot modify the number of minor fragments within the execution plan. However, you can view the query profile in the Drill Web Console and modify some configuration options that change the behavior of minor fragments, such as the maximum number of slices. See [Configuration Options]({{ site.baseurl }}/docs/configuration-options-introduction/).
 
 ### Execution of Minor Fragments
 Minor fragments can run as root, intermediate, or leaf fragments. An execution tree contains only one root fragment. The coordinates of the execution tree are numbered from the root, with the root being zero. Data flows downstream from the leaf fragments to the root fragment.

http://git-wip-us.apache.org/repos/asf/drill/blob/010ae6a6/_docs/configure-drill/010-configure-drill-introduction.md
----------------------------------------------------------------------
diff --git a/_docs/configure-drill/010-configure-drill-introduction.md b/_docs/configure-drill/010-configure-drill-introduction.md
index 3a50315..6b9a3fa 100644
--- a/_docs/configure-drill/010-configure-drill-introduction.md
+++ b/_docs/configure-drill/010-configure-drill-introduction.md
@@ -25,4 +25,4 @@ statements is Parquet. Using a configuration option, you can modify Drill to sto
 
 ## Query Profile Data Storage Configuration
 
-To enjoy a problem-free Drill Web UI experience, you need to [configure the ZooKeeper PStore]({{site.baseurl}}/docs/persistent-configuration-storage/#configuring-zookeeper-pstore).
+To enjoy a problem-free Drill Web Console experience, you need to [configure the ZooKeeper PStore]({{site.baseurl}}/docs/persistent-configuration-storage/#configuring-zookeeper-pstore).

http://git-wip-us.apache.org/repos/asf/drill/blob/010ae6a6/_docs/configure-drill/070-configuring-user-impersonation.md
----------------------------------------------------------------------
diff --git a/_docs/configure-drill/070-configuring-user-impersonation.md b/_docs/configure-drill/070-configuring-user-impersonation.md
index bc7a151..074da69 100644
--- a/_docs/configure-drill/070-configuring-user-impersonation.md
+++ b/_docs/configure-drill/070-configuring-user-impersonation.md
@@ -28,7 +28,7 @@ The following table lists the clients, storage plugins, and types of queries tha
   <tr>
     <td>Clients</td>
     <td>SQLLine, ODBC, JDBC</td>
-    <td>Drill Web UI, REST API</td>
+    <td>Drill Web Console, REST API</td>
   </tr>
   <tr>
     <td>Storage Plugins</td>

http://git-wip-us.apache.org/repos/asf/drill/blob/010ae6a6/_docs/configure-drill/076-configuring-user-impersonation-with-hive-authorization.md
----------------------------------------------------------------------
diff --git a/_docs/configure-drill/076-configuring-user-impersonation-with-hive-authorization.md b/_docs/configure-drill/076-configuring-user-impersonation-with-hive-authorization.md
index 37158c6..6837cc9 100755
--- a/_docs/configure-drill/076-configuring-user-impersonation-with-hive-authorization.md
+++ b/_docs/configure-drill/076-configuring-user-impersonation-with-hive-authorization.md
@@ -45,9 +45,9 @@ Modify `<DRILL_HOME>/conf/drill-override.conf` on each Drill node to include the
                  enabled: true,
                  max_chained_user_hops: 3
             }
-           }  
-
-2. Issue the following command to restart the Drillbit process on each Drill node:  
+           }  
+
+2. Issue the following command to restart the Drillbit process on each Drill node:  
 `<DRILLINSTALL_HOME>/bin/drillbit.sh restart`  
 
 ##  Step 2:  Updating hive-site.xml  
@@ -86,52 +86,52 @@ Add the following required authorization parameters in hive-site.xml to configur
 
 ### Example of hive-site.xml configuration with the required properties for storage based authorization 
 
-       <configuration>
-         <property>
-           <name>hive.metastore.uris</name>
-           <value>thrift://10.10.100.120:9083</value>    
-         </property>  
-       
-         <property>
-           <name>javax.jdo.option.ConnectionURL</name>
-           <value>jdbc:derby:;databaseName=/opt/hive/hive-1.0/bin/metastore_db;create=true</value>    
-         </property>
-       
-         <property>
-           <name>javax.jdo.option.ConnectionDriverName</name>
-           <value>org.apache.derby.jdbc.EmbeddedDriver</value>    
-         </property>
-       
-         <property>
-           <name>hive.metastore.pre.event.listeners</name>
-           <value>org.apache.hadoop.hive.ql.security.authorization.AuthorizationPreEventListener</value>
-         </property>
-       
-         <property>
-           <name>hive.security.metastore.authenticator.manager</name>
-           <value>org.apache.hadoop.hive.ql.security.HadoopDefaultMetastoreAuthenticator</value>
-         </property>
-       
-         <property>
-           <name>hive.security.metastore.authorization.manager</name>
-           <value>org.apache.hadoop.hive.ql.security.authorization.StorageBasedAuthorizationProvider</value>
-         </property>
-       
-         <property>
-           <name>hive.security.metastore.authorization.auth.reads</name>
-           <value>true</value>
-         </property>
-       
-         <property>
-           <name>hive.metastore.execute.setugi</name>
-           <value>true</value>
-         </property>
-       
-         <property>
-           <name>hive.server2.enable.doAs</name>
-           <value>true</value>
-         </property>
-       </configuration>
+       <configuration>
+         <property>
+           <name>hive.metastore.uris</name>
+           <value>thrift://10.10.100.120:9083</value>    
+         </property>  
+       
+         <property>
+           <name>javax.jdo.option.ConnectionURL</name>
+           <value>jdbc:derby:;databaseName=/opt/hive/hive-1.0/bin/metastore_db;create=true</value>    
+         </property>
+       
+         <property>
+           <name>javax.jdo.option.ConnectionDriverName</name>
+           <value>org.apache.derby.jdbc.EmbeddedDriver</value>    
+         </property>
+       
+         <property>
+           <name>hive.metastore.pre.event.listeners</name>
+           <value>org.apache.hadoop.hive.ql.security.authorization.AuthorizationPreEventListener</value>
+         </property>
+       
+         <property>
+           <name>hive.security.metastore.authenticator.manager</name>
+           <value>org.apache.hadoop.hive.ql.security.HadoopDefaultMetastoreAuthenticator</value>
+         </property>
+       
+         <property>
+           <name>hive.security.metastore.authorization.manager</name>
+           <value>org.apache.hadoop.hive.ql.security.authorization.StorageBasedAuthorizationProvider</value>
+         </property>
+       
+         <property>
+           <name>hive.security.metastore.authorization.auth.reads</name>
+           <value>true</value>
+         </property>
+       
+         <property>
+           <name>hive.metastore.execute.setugi</name>
+           <value>true</value>
+         </property>
+       
+         <property>
+           <name>hive.server2.enable.doAs</name>
+           <value>true</value>
+         </property>
+       </configuration>
 
 
 ## SQL Standard Based Authorization  
@@ -214,7 +214,7 @@ Add the following required authorization parameters in hive-site.xml to configur
 
 ## Step 3: Modifying the Hive Storage Plugin  
 
-Modify the Hive storage plugin configuration in the Drill Web UI to include specific authorization settings. The Drillbit that you use to access the Web UI must be running.  
+Modify the Hive storage plugin configuration in the Drill Web Console to include specific authorization settings. The Drillbit that you use to access the Web Console must be running.  
 
 Complete the following steps to modify the Hive storage plugin:  
 
@@ -235,8 +235,8 @@ Complete the following steps to modify the Hive storage plugin:
                  "hive.metastore.execute.setugi" : "true"
                }
               }  
-   * For SQL standard based authorization, add the following properties:  
-
+   * For SQL standard based authorization, add the following properties:  
+
               {
                type:"hive",
                enabled: true,

http://git-wip-us.apache.org/repos/asf/drill/blob/010ae6a6/_docs/configure-drill/078-configuring-web-ui-and-rest-api-security.md
----------------------------------------------------------------------
diff --git a/_docs/configure-drill/078-configuring-web-ui-and-rest-api-security.md b/_docs/configure-drill/078-configuring-web-ui-and-rest-api-security.md
index 817e650..edaad8f 100644
--- a/_docs/configure-drill/078-configuring-web-ui-and-rest-api-security.md
+++ b/_docs/configure-drill/078-configuring-web-ui-and-rest-api-security.md
@@ -1,16 +1,16 @@
 ---
-title: "Configuring Web UI and REST API Security"
+title: "Configuring Web Console and REST API Security"
 parent: "Configure Drill"
 ---
-Drill 1.2 extends [Drill user authentication]({{site.baseurl}}/docs/configuring-user-authentication/) to the Web UI and underlying REST API. As administrator, you can control the extent of access to the Web UI and REST API client applications. For example,
-you can limit the access of certain users to Web UI functionality, such as viewing the in-progress or completed queries of other users. You can limit users from viewing other users' query profiles, who can cancel queries of other users, and other functionality.
+Drill 1.2 extends [Drill user authentication]({{site.baseurl}}/docs/configuring-user-authentication/) to the Web Console and underlying REST API. As administrator, you can control the extent of access to the Web Console and REST API client applications. For example,
+you can limit the access of certain users to Web Console functionality, such as viewing the in-progress or completed queries of other users. You can limit users from viewing other users' query profiles, who can cancel queries of other users, and other functionality.
 
-With Web UI security in place, users who do not have administrator privileges need to use the SHOW SCHEMAS command instead of the Web UI for storage plugin configuration information.
+With Web Console security in place, users who do not have administrator privileges need to use the SHOW SCHEMAS command instead of the Web Console for storage plugin configuration information.
 
 ## HTTPS Support
-Drill 1.2 uses the Linux Pluggable Authentication Module (PAM) and code-level support for transport layer security (TLS) to secure the Web UI and REST API. By default, the Web UI and REST API now support the HTTPS protocol.
+Drill 1.2 uses the Linux Pluggable Authentication Module (PAM) and code-level support for transport layer security (TLS) to secure the Web Console and REST API. By default, the Web Console and REST API now support the HTTPS protocol.
 
-By default, Drill generates a self-signed certificate that works with SSL for HTTPS access to the Web UI; however, as administrator, you can set up SSL to specify the keystore or truststore, or both, for your organization, as described in the next section.
+By default, Drill generates a self-signed certificate that works with SSL for HTTPS access to the Web Console; however, as administrator, you can set up SSL to specify the keystore or truststore, or both, for your organization, as described in the next section.
 
 ## Setting Up a Custom SSL Configuration
 
@@ -25,15 +25,15 @@ As cluster administrator, you can set the following SSL configuration parameters
 * javax.net.ssl.trustStorePassword  
   Password for accessing the trusted keystore file.
 
-## Prerequisites for Web UI and REST API Security
+## Prerequisites for Web Console and REST API Security
 
-You need to perform the following configuration tasks using Web UI and REST API security.  
+You need to perform the following configuration tasks using Web Console and REST API security.  
 
 * [User Authentication]({{site.baseurl}}/docs/configuring-user-authentication/)  
-* Set up Web UI administrators  
-  Optionally, you can set up Web UI administrator-user groups to facilitate management of multiple Web UI administrators.
+* Set up Web Console administrators  
+  Optionally, you can set up Web Console administrator-user groups to facilitate management of multiple Web Console administrators.
 
-## Setting up Web UI Administrators and Administrator-User Groups
+## Setting up Web Console Administrators and Administrator-User Groups
 
 Configure the following system options using the [ALTER SYSTEM]({{site.baseurl}}/docs/alter-system/) command:
 
@@ -42,11 +42,11 @@ Configure the following system options using the [ALTER SYSTEM]({{site.baseurl}}
 * security.admin.user_groups  
   Set the value of this option to a comma-separated list of administrators.
 
-Any user for whom you have configured Drill user authentication, but not set up as a Web UI administrator, has only user privileges to access the Web UI and REST API client applications.
+Any user for whom you have configured Drill user authentication, but not set up as a Web Console administrator, has only user privileges to access the Web Console and REST API client applications.
 
-## Web UI and REST API Privileges
+## Web Console and REST API Privileges
 
-The following table and subsections describe the privilege levels for accessing the REST API methods and corresponding Web UI functions:
+The following table and subsections describe the privilege levels for accessing the REST API methods and corresponding Web Console functions:
 
 * Administrator (ADMIN)  
 * User (USER)  
@@ -104,9 +104,9 @@ The following table and subsections describe the privilege levels for accessing
 * ADMIN - can cancel the query.  
 * USER - cancel the query only if the query is launched by the user requesting the cancellation.
 
-## Starting the Web UI Using Authentication
+## Starting the Web Console Using Authentication
 
-The following example shows the sequence of steps you typically perform to access the Web UI when authentication is enabled on a Drill cluster.
+The following example shows the sequence of steps you typically perform to access the Web Console when authentication is enabled on a Drill cluster.
 
 1. Set the JVM library path to the location of the PAM `.so` file.  
    `export DRILLBIT_JAVA_OPTS=" -Djava.library.path=/root/ "`  
@@ -117,5 +117,5 @@ The following example shows the sequence of steps you typically perform to acces
 4. Open a browser, and go to `https://<IP address>:8047`, where IP address is the host name or IP address of one of the installed Drillbits in a distributed system.  
    The login screen appears:  
 
-   ![Web UI Login]({{ site.baseurl }}/docs/img/web-ui-login.png)
-5. [Start the Web UI]({{ site.baseurl }}/docs/starting-the-web-ui/).
\ No newline at end of file
+   ![Web Console Login]({{ site.baseurl }}/docs/img/web-ui-login.png)
+5. [Start the Web Console]({{ site.baseurl }}/docs/starting-the-web-ui/).
\ No newline at end of file

http://git-wip-us.apache.org/repos/asf/drill/blob/010ae6a6/_docs/configure-drill/100-ports-used-by-drill.md
----------------------------------------------------------------------
diff --git a/_docs/configure-drill/100-ports-used-by-drill.md b/_docs/configure-drill/100-ports-used-by-drill.md
index 2cb7ba5..a90be08 100644
--- a/_docs/configure-drill/100-ports-used-by-drill.md
+++ b/_docs/configure-drill/100-ports-used-by-drill.md
@@ -7,8 +7,8 @@ type, and a description of how Drill uses the port:
 
 | Port  | Type | Description                                                                                                                                                                    |
 |-------|------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
-| 8047  | TCP  | Needed for the Drill Web UI.                                                                                                                                                   |
-| 31010 | TCP  | User port address. Used between nodes in a Drill cluster. Needed for an external client, such as Tableau, to connect into the cluster nodes. Also needed for the Drill Web UI. |
+| 8047  | TCP  | Needed for the Drill Web Console.                                                                                                                                                   |
+| 31010 | TCP  | User port address. Used between nodes in a Drill cluster. Needed for an external client, such as Tableau, to connect into the cluster nodes. Also needed for the Drill Web Console. |
 | 31011 | TCP  | Control port address. Used between nodes in a Drill cluster. Needed for multi-node installation of Apache Drill.                                                               |
 | 31012 | TCP  | Data port address. Used between nodes in a Drill cluster. Needed for multi-node installation of Apache Drill.                                                                  |
 | 46655 | UDP  | Used for JGroups and Infinispan. Needed for multi-node installation of Apache Drill.                                                                                           |

http://git-wip-us.apache.org/repos/asf/drill/blob/010ae6a6/_docs/configure-drill/configuration-options/040-persistent-configuration-storage.md
----------------------------------------------------------------------
diff --git a/_docs/configure-drill/configuration-options/040-persistent-configuration-storage.md b/_docs/configure-drill/configuration-options/040-persistent-configuration-storage.md
index 321a26f..2cd8046 100644
--- a/_docs/configure-drill/configuration-options/040-persistent-configuration-storage.md
+++ b/_docs/configure-drill/configuration-options/040-persistent-configuration-storage.md
@@ -26,11 +26,11 @@ store persistent configuration data. The ZooKeeper PStore provider stores all
 of the persistent configuration data in ZooKeeper except for query profile
 data. The ZooKeeper PStore provider offloads query profile data to the Drill log directory on Drill nodes. 
 
-You need to configure the ZooKeeper PStore to use the Drill Web UI when running multiple Drillbits. 
+You need to configure the ZooKeeper PStore to use the Drill Web Console when running multiple Drillbits. 
 
 ### Why Configure the ZooKeeper PStore
 
-When you run multiple DrillBits, configure a specific location for ZooKeeper to offload the query profile data instead of accepting the default temporary location. All Drillbits in the cluster cannot access the temporary location. Consequently, when you do not configure a location on the distributed file system, queries sent to some Drillbits do not appear in the Completed section of the Drill Web UI. Also, some Running links that you click to get information about running queries are broken links.
+When you run multiple DrillBits, configure a specific location for ZooKeeper to offload the query profile data instead of accepting the default temporary location. All Drillbits in the cluster cannot access the temporary location. Consequently, when you do not configure a location on the distributed file system, queries sent to some Drillbits do not appear in the Completed section of the Drill Web Console. Also, some Running links that you click to get information about running queries are broken links.
 
 ### How to Configure the ZooKeeper PStore
 

http://git-wip-us.apache.org/repos/asf/drill/blob/010ae6a6/_docs/connect-a-data-source/020-storage-plugin-registration.md
----------------------------------------------------------------------
diff --git a/_docs/connect-a-data-source/020-storage-plugin-registration.md b/_docs/connect-a-data-source/020-storage-plugin-registration.md
index a28e6bb..0ef8707 100644
--- a/_docs/connect-a-data-source/020-storage-plugin-registration.md
+++ b/_docs/connect-a-data-source/020-storage-plugin-registration.md
@@ -2,7 +2,7 @@
 title: "Storage Plugin Registration"
 parent: "Connect a Data Source"
 ---
-You connect Drill to a file system, Hive, HBase, or other data source through a storage plugin. On the Storage tab of the Drill Web UI, you can view and reconfigure a storage plugin if you are [authorized]({{site.baseurl}}/docs/configuring-web-ui-and-rest-api-security/) to do so. Go to `https://<IP address>:8047/storage`, where IP address is the host name or IP address of one of the installed Drillbits in a distributed system or `localhost` in an embedded system. In Drill 1.1 and earlier, go to `http://<IP address>:8047/storage` to view and configure a storage plugin.
+You connect Drill to a file system, Hive, HBase, or other data source through a storage plugin. On the Storage tab of the Drill Web Console, you can view and reconfigure a storage plugin if you are [authorized]({{site.baseurl}}/docs/configuring-web-ui-and-rest-api-security/) to do so. Go to `https://<IP address>:8047/storage`, where IP address is the host name or IP address of one of the installed Drillbits in a distributed system or `localhost` in an embedded system. In Drill 1.1 and earlier, go to `http://<IP address>:8047/storage` to view and configure a storage plugin.
 
 The Drill installation registers the `cp`, `dfs`, `hbase`, `hive`, and `mongo` default storage plugin configurations.
 
@@ -26,9 +26,9 @@ To register a new storage plugin configuration, enter a storage name, click **CR
 
 ## Storage Plugin Configuration Persistance
 
-Drill saves storage plugin configurations in a temporary directory (embedded mode) or in ZooKeeper (distributed mode). For example, on Mac OS X, Drill uses `/tmp/drill/sys.storage_plugins` to store storage plugin configurations. Enabling authorization to protect this data through the Web UI and REST API does not include protection for the data in the tmp directory or in ZooKeeper. 
+Drill saves storage plugin configurations in a temporary directory (embedded mode) or in ZooKeeper (distributed mode). For example, on Mac OS X, Drill uses `/tmp/drill/sys.storage_plugins` to store storage plugin configurations. Enabling authorization to protect this data through the Web Console and REST API does not include protection for the data in the tmp directory or in ZooKeeper. 
 
 <!-- See Drill-3780 -->
 
-The storage plugin configuration persists after upgrading, so authorized users can see a configuration that you created in one version of Drill in the Drill Web UI of an upgraded version of Drill. To revert to the default storage plugins for a particular version, in embedded mode, delete the contents of this directory and restart the Drill shell.
+The storage plugin configuration persists after upgrading, so authorized users can see a configuration that you created in one version of Drill in the Drill Web Console of an upgraded version of Drill. To revert to the default storage plugins for a particular version, in embedded mode, delete the contents of this directory and restart the Drill shell.
 

http://git-wip-us.apache.org/repos/asf/drill/blob/010ae6a6/_docs/connect-a-data-source/035-plugin-configuration-basics.md
----------------------------------------------------------------------
diff --git a/_docs/connect-a-data-source/035-plugin-configuration-basics.md b/_docs/connect-a-data-source/035-plugin-configuration-basics.md
index 2e7095b..7c03515 100644
--- a/_docs/connect-a-data-source/035-plugin-configuration-basics.md
+++ b/_docs/connect-a-data-source/035-plugin-configuration-basics.md
@@ -7,9 +7,9 @@ cluster having multiple installations of Drill, Drill broadcasts the information
 to synchronize the storage plugin configurations. You do not need to
 restart any of the Drillbits when you add or update a storage plugin configuration.
 
-## Using the Drill Web UI
+## Using the Drill Web Console
 
-Assuming you are [authorized]({{site.baseurl}}/docs/configuring-web-ui-and-rest-api-security/), you can use the Drill Web UI to update or add a new storage plugin configuration. The Drill shell needs to be running to access the Drill Web UI. In Drill 1.2 and later, to open the Drill Web UI, launch a web browser, and go to: `https://<IP address or host name>:8047` of any Drillbit in the cluster. In Drill 1.1 and earlier, use `http` instead of `https`. Select the Storage tab to view, update, or add a new storage plugin configuration. 
+Assuming you are [authorized]({{site.baseurl}}/docs/configuring-web-ui-and-rest-api-security/), you can use the Drill Web Console to update or add a new storage plugin configuration. The Drill shell needs to be running to access the Drill Web Console. In Drill 1.2 and later, to open the Drill Web Console, launch a web browser, and go to: `https://<IP address or host name>:8047` of any Drillbit in the cluster. In Drill 1.1 and earlier, use `http` instead of `https`. Select the Storage tab to view, update, or add a new storage plugin configuration. 
 
 To create a name and new configuration:
 
@@ -150,7 +150,7 @@ If you need to add a storage plugin configuration to Drill and do not want to us
   The storage plugin configuration name. 
 
 * config  
-  The attribute settings as entered in the Web UI.
+  The attribute settings as entered in the Web Console.
 
 For example, this command creates a storage plugin named myplugin for reading files of an unknown type located on the root of the file system:
 
@@ -163,7 +163,7 @@ The REST API is recommended for programmatically adding a storage plugin configu
 Currently, bootstrapping a storage plugin configuration works only when the first Drillbit in the cluster first starts up. The configuration is
 stored in ZooKeeper, preventing Drill from picking up the bootstrap-storage-plugins.json again.
 
-After cluster startup, you have to use the REST API or Drill Web UI to add a storage plugin configuration. Alternatively, you
+After cluster startup, you have to use the REST API or Drill Web Console to add a storage plugin configuration. Alternatively, you
 can modify the entry in ZooKeeper by uploading the json file for
 that plugin to the /drill directory of the zookeeper installation, or by just deleting the /drill directory if you do not have configuration properties to preserve.
 

http://git-wip-us.apache.org/repos/asf/drill/blob/010ae6a6/_docs/connect-a-data-source/060-hbase-storage-plugin.md
----------------------------------------------------------------------
diff --git a/_docs/connect-a-data-source/060-hbase-storage-plugin.md b/_docs/connect-a-data-source/060-hbase-storage-plugin.md
index d97feab..b82e5bd 100644
--- a/_docs/connect-a-data-source/060-hbase-storage-plugin.md
+++ b/_docs/connect-a-data-source/060-hbase-storage-plugin.md
@@ -4,7 +4,7 @@ parent: "Storage Plugin Configuration"
 ---
 When connecting Drill to an HBase data source using the HBase storage plugin installed with Drill, you need to specify a ZooKeeper quorum. Drill supports HBase version 0.98.
 
-To view or change the HBase storage plugin configuration, use the [Drill Web UI]({{ site.baseurl }}/docs/plugin-configuration-basics/#using-the-drill-web-ui). In the Web UI, select the **Storage** tab, and then click the **Update** button for the `hbase` storage plugin configuration. The following example shows a typical HBase storage plugin:
+To view or change the HBase storage plugin configuration, use the [Drill Web Console]({{ site.baseurl }}/docs/plugin-configuration-basics/#using-the-drill-web-ui). In the Web Console, select the **Storage** tab, and then click the **Update** button for the `hbase` storage plugin configuration. The following example shows a typical HBase storage plugin:
 
             {
               "type": "hbase",

http://git-wip-us.apache.org/repos/asf/drill/blob/010ae6a6/_docs/connect-a-data-source/070-hive-storage-plugin.md
----------------------------------------------------------------------
diff --git a/_docs/connect-a-data-source/070-hive-storage-plugin.md b/_docs/connect-a-data-source/070-hive-storage-plugin.md
index bad475d..5a4c3b3 100644
--- a/_docs/connect-a-data-source/070-hive-storage-plugin.md
+++ b/_docs/connect-a-data-source/070-hive-storage-plugin.md
@@ -21,8 +21,8 @@ To register a remote Hive metastore with Drill:
 
 1. Issue the following command to start the Hive metastore service on the system specified in the `hive.metastore.uris`:
    `hive --service metastore`
-2. In the [Drill Web UI]({{ site.baseurl }}/docs/plugin-configuration-basics/#using-the-drill-web-ui), select the **Storage** tab.
-3. In the list of disabled storage plugins in the Drill Web UI, click **Update** next to `hive`. The Hive storage plugin configuration appears:
+2. In the [Drill Web Console]({{ site.baseurl }}/docs/plugin-configuration-basics/#using-the-drill-web-ui), select the **Storage** tab.
+3. In the list of disabled storage plugins in the Drill Web Console, click **Update** next to `hive`. The Hive storage plugin configuration appears:
 
         {
           "type": "hive",
@@ -52,13 +52,13 @@ After configuring a Hive storage plugin, you can [query Hive tables]({{ site.bas
 
 The Hive metastore configuration is embedded within the Drill process. Configure an embedded metastore only in a cluster that runs a single Drillbit and only for testing purposes. Do not embed the Hive metastore in production systems.
 
-Provide the metastore database configuration settings in the Drill Web UI. Before you configure an embedded Hive metastore, verify that the driver you use to connect to the Hive metastore is in the Drill classpath located in `/<drill installation directory>/lib/.` If the driver is not there, copy the driver to `/<drill
+Provide the metastore database configuration settings in the Drill Web Console. Before you configure an embedded Hive metastore, verify that the driver you use to connect to the Hive metastore is in the Drill classpath located in `/<drill installation directory>/lib/.` If the driver is not there, copy the driver to `/<drill
 installation directory>/lib` on the Drill node. For more information about storage types and configurations, refer to ["Hive Metastore Administration"](https://cwiki.apache.org/confluence/display/Hive/AdminManual+MetastoreAdmin).
 
 To configure an embedded Hive metastore, complete the following
 steps:
 
-1. In the [Drill Web UI]({{ site.baseurl }}/docs/plugin-configuration-basics/#using-the-drill-web-ui), and select the **Storage** tab.
+1. In the [Drill Web Console]({{ site.baseurl }}/docs/plugin-configuration-basics/#using-the-drill-web-ui), and select the **Storage** tab.
 2. In the disabled storage plugin configurations section, click **Update** next to `hive`.
 3. In the configuration window, add the database configuration settings.
 

http://git-wip-us.apache.org/repos/asf/drill/blob/010ae6a6/_docs/connect-a-data-source/080-drill-default-input-format.md
----------------------------------------------------------------------
diff --git a/_docs/connect-a-data-source/080-drill-default-input-format.md b/_docs/connect-a-data-source/080-drill-default-input-format.md
index fd6b768..778e3c7 100644
--- a/_docs/connect-a-data-source/080-drill-default-input-format.md
+++ b/_docs/connect-a-data-source/080-drill-default-input-format.md
@@ -23,7 +23,7 @@ You must have a [defined workspace]({{ site.baseurl }}/docs/workspaces) before y
 
 To define a default input format for a workspace:
 
-  1. Navigate to the [Drill Web UI]({{ site.baseurl }}/docs/plugin-configuration-basics/#using-the-drill-web-ui). The Drillbit process must be running on the node before you connect to the Drill Web UI.
+  1. Navigate to the [Drill Web Console]({{ site.baseurl }}/docs/plugin-configuration-basics/#using-the-drill-web-ui). The Drillbit process must be running on the node before you connect to the Drill Web Console.
   2. Select **Storage** in the toolbar.
   3. Click **Update** next to the storage plugin configuration for which you want to define a default input format for a workspace.
   4. In the Configuration area, locate the workspace, and change the `defaultInputFormat` attribute to any of the supported file types.

http://git-wip-us.apache.org/repos/asf/drill/blob/010ae6a6/_docs/connect-a-data-source/090-mongodb-plugin-for-apache-drill.md
----------------------------------------------------------------------
diff --git a/_docs/connect-a-data-source/090-mongodb-plugin-for-apache-drill.md b/_docs/connect-a-data-source/090-mongodb-plugin-for-apache-drill.md
index e3f60c9..400a069 100644
--- a/_docs/connect-a-data-source/090-mongodb-plugin-for-apache-drill.md
+++ b/_docs/connect-a-data-source/090-mongodb-plugin-for-apache-drill.md
@@ -24,12 +24,12 @@ To query MongoDB with Drill, you install Drill and MongoDB, and then you import
 
 ## Configuring MongoDB
 
-Drill must be running in order to access the Web UI to configure a storage plugin configuration. Start Drill and view and enable the MongoDB storage plugin configuration as described in the following procedure: 
+Drill must be running in order to access the Web Console to configure a storage plugin configuration. Start Drill and view and enable the MongoDB storage plugin configuration as described in the following procedure: 
 
   1. [Start the Drill shell]({{site.baseurl}}/docs/starting-drill-on-linux-and-mac-os-x/).
 
-     The Drill shell needs to be running to access the Drill Web UI.
-  2. In the [Drill Web UI]({{ site.baseurl }}/docs/plugin-configuration-basics/#using-the-drill-web-ui), select the **Storage** tab.
+     The Drill shell needs to be running to access the Drill Web Console.
+  2. In the [Drill Web Console]({{ site.baseurl }}/docs/plugin-configuration-basics/#using-the-drill-web-ui), select the **Storage** tab.
   4. Under Disabled Storage Plugins, select **Update** to choose the `mongo` storage plugin configuration.
   5. In the Configuration window, take a look at the default configuration:
      

http://git-wip-us.apache.org/repos/asf/drill/blob/010ae6a6/_docs/install/060-starting-the-web-ui.md
----------------------------------------------------------------------
diff --git a/_docs/install/060-starting-the-web-ui.md b/_docs/install/060-starting-the-web-ui.md
index 0fdcafe..3720bb1 100644
--- a/_docs/install/060-starting-the-web-ui.md
+++ b/_docs/install/060-starting-the-web-ui.md
@@ -1,24 +1,24 @@
 ---
-title: Starting the Web UI
+title: Starting the Web Console
 parent: Install Drill
 ---
 
-The Drill Web UI is one of several [client interfaces](/docs/architecture-introduction/#drill-clients) you can use to access Drill.  To access the Web UI in Drill 1.2 and later, go to `https://<IP address>:8047`, where IP address is the host name or IP address of one of the installed Drillbits in a distributed system. In Drill 1.1 and earlier, go to `http://<IP address>:8047` to access the Web UI.
+The Drill Web Console is one of several [client interfaces](/docs/architecture-introduction/#drill-clients) you can use to access Drill.  To access the Web Console in Drill 1.2 and later, go to `https://<IP address>:8047`, where IP address is the host name or IP address of one of the installed Drillbits in a distributed system. In Drill 1.1 and earlier, go to `http://<IP address>:8047` to access the Web Console.
 
-If [user authentication]({{site.baseurl}}/docs/configuring-user-authentication/) is not enabled, the Web UI controls appear: 
+If [user authentication]({{site.baseurl}}/docs/configuring-user-authentication/) is not enabled, the Web Console controls appear: 
 
-![Web UI]({{ site.baseurl }}/docs/img/web-ui.png)
+![Web Console]({{ site.baseurl }}/docs/img/web-ui.png)
 
 If user authentication is enabled, Drill 1.2 and later prompts you for a user name and password:
 
-![Web UI Login]({{ site.baseurl }}/docs/img/web-ui-login.png)
+![Web Console Login]({{ site.baseurl }}/docs/img/web-ui-login.png)
 
-If an administrator logs in, all the Web UI controls appear: Query, Profiles, Storage, Metrics, Threads, and Options.
+If an administrator logs in, all the Web Console controls appear: Query, Profiles, Storage, Metrics, Threads, and Options.
 
-![Web UI Admin View]({{ site.baseurl }}/docs/img/web-ui-admin-view.png)
+![Web Console Admin View]({{ site.baseurl }}/docs/img/web-ui-admin-view.png)
 
-If a user, who is not an administrator, logs in, the Web UI controls are limited to Query, Metrics, Threads controls, and possibly, Profiles. An administrator can give users permission to access the Profiles control. Only administrators can see and use the Storage control for managing storage plugin configurations.
+If a user, who is not an administrator, logs in, the Web Console controls are limited to Query, Metrics, Threads controls, and possibly, Profiles. An administrator can give users permission to access the Profiles control. Only administrators can see and use the Storage control for managing storage plugin configurations.
 
-![Web UI User View]({{ site.baseurl }}/docs/img/web-ui-user-view.png)
+![Web Console User View]({{ site.baseurl }}/docs/img/web-ui-user-view.png)
 
 

http://git-wip-us.apache.org/repos/asf/drill/blob/010ae6a6/_docs/log-and-debug/001-log-and-debug-introduction.md
----------------------------------------------------------------------
diff --git a/_docs/log-and-debug/001-log-and-debug-introduction.md b/_docs/log-and-debug/001-log-and-debug-introduction.md
index 8b50cea..555ceab 100644
--- a/_docs/log-and-debug/001-log-and-debug-introduction.md
+++ b/_docs/log-and-debug/001-log-and-debug-introduction.md
@@ -12,6 +12,6 @@ Drill provides two standard output files:
 * drillbit.out
 * drill.log
 
-Drill also provides a special file, drillbit_queries.json, on each Drill node. This log provides the QueryID and profile for every query run on a Drillbit. The Profile view in the Drill Web UI lists the last one-hundred queries that Drill ran. To see information for queries beyond the last one-hundred, you can view the drillbit_queries.json file on each Drill node.
+Drill also provides a special file, drillbit_queries.json, on each Drill node. This log provides the QueryID and profile for every query run on a Drillbit. The Profile view in the Drill Web Console lists the last one-hundred queries that Drill ran. To see information for queries beyond the last one-hundred, you can view the drillbit_queries.json file on each Drill node.
 
 Drill also provides [audit logging]({{site.baseurl}}/docs/query-audit-logging/) of queries executed by various drillbits in the cluster. 

http://git-wip-us.apache.org/repos/asf/drill/blob/010ae6a6/_docs/log-and-debug/002-error-messages.md
----------------------------------------------------------------------
diff --git a/_docs/log-and-debug/002-error-messages.md b/_docs/log-and-debug/002-error-messages.md
index d0c1f7b..78a9d1e 100644
--- a/_docs/log-and-debug/002-error-messages.md
+++ b/_docs/log-and-debug/002-error-messages.md
@@ -20,6 +20,6 @@ The following table provides descriptions for the IDs included in a thread:
 
 | ID Type         | Description                                                                                                                                                                                                                                  |
 |-----------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
-| QueryID         | The identifier assigned to the query. You can locate a query in Drill Web UI by the QueryID and then cancel the query if needed. See [Query Profiles]({{ site.baseurl }}/docs/query-profiles/).                                                                    |
-| MajorFragmentID | The identifier assigned to a major fragment. Major fragments map to the physical plan. You can see major fragment activity for a query in the Drill Web UI. See [Query Profiles]({{ site.baseurl }}/docs/query-profiles) for more information. |
+| QueryID         | The identifier assigned to the query. You can locate a query in Drill Web Console by the QueryID and then cancel the query if needed. See [Query Profiles]({{ site.baseurl }}/docs/query-profiles/).                                                                    |
+| MajorFragmentID | The identifier assigned to a major fragment. Major fragments map to the physical plan. You can see major fragment activity for a query in the Drill Web Console. See [Query Profiles]({{ site.baseurl }}/docs/query-profiles) for more information. |
 | MinorFragmentID | The identifier assigned to the minor fragment. Minor fragments map to the parallelization of major fragments. See [Query Profiles]({{ site.baseurl }}/docs/query-profiles).                                                                                       |
\ No newline at end of file

http://git-wip-us.apache.org/repos/asf/drill/blob/010ae6a6/_docs/odbc-jdbc-interfaces/010-interfaces-introduction.md
----------------------------------------------------------------------
diff --git a/_docs/odbc-jdbc-interfaces/010-interfaces-introduction.md b/_docs/odbc-jdbc-interfaces/010-interfaces-introduction.md
index 2ea6b4d..917642f 100644
--- a/_docs/odbc-jdbc-interfaces/010-interfaces-introduction.md
+++ b/_docs/odbc-jdbc-interfaces/010-interfaces-introduction.md
@@ -5,7 +5,7 @@ parent: "ODBC/JDBC Interfaces"
 You can connect to Apache Drill through the following interfaces:
 
   * Drill shell
-  * Drill Web UI
+  * Drill Web Console
   * [ODBC]({{ site.baseurl }}/docs/installing-the-odbc-driver/)*
   * [JDBC]({{ site.baseurl }}/docs/using-jdbc-with-squirrel-on-windows/)
   * C++ API

http://git-wip-us.apache.org/repos/asf/drill/blob/010ae6a6/_docs/odbc-jdbc-interfaces/using-drill-with-bi-tools/020-tableau-examples.md
----------------------------------------------------------------------
diff --git a/_docs/odbc-jdbc-interfaces/using-drill-with-bi-tools/020-tableau-examples.md b/_docs/odbc-jdbc-interfaces/using-drill-with-bi-tools/020-tableau-examples.md
index 2c8f76c..df96d37 100755
--- a/_docs/odbc-jdbc-interfaces/using-drill-with-bi-tools/020-tableau-examples.md
+++ b/_docs/odbc-jdbc-interfaces/using-drill-with-bi-tools/020-tableau-examples.md
@@ -14,7 +14,7 @@ This section includes the following examples:
 
 The steps and results of these examples assume pre-configured schemas and
 source data. You define schemas by configuring storage plugins on the Storage
-tab of the [Drill Web UI]({{ site.baseurl }}/docs/getting-to-know-the-drill-sandbox#storage-plugin-overview). Also, the examples assume you [enabled the DECIMAL data type]({{site.baseurl}}/docs/supported-data-types#enabling-the-decimal-type) in Drill.  
+tab of the [Drill Web Console]({{ site.baseurl }}/docs/getting-to-know-the-drill-sandbox#storage-plugin-overview). Also, the examples assume you [enabled the DECIMAL data type]({{site.baseurl}}/docs/supported-data-types#enabling-the-decimal-type) in Drill.  
 
 ## Example: Connect to a Hive Table in Tableau
 

http://git-wip-us.apache.org/repos/asf/drill/blob/010ae6a6/_docs/performance-tuning/identifying-performance-issues/010-query-plans.md
----------------------------------------------------------------------
diff --git a/_docs/performance-tuning/identifying-performance-issues/010-query-plans.md b/_docs/performance-tuning/identifying-performance-issues/010-query-plans.md
index b08435b..c433d37 100755
--- a/_docs/performance-tuning/identifying-performance-issues/010-query-plans.md
+++ b/_docs/performance-tuning/identifying-performance-issues/010-query-plans.md
@@ -8,7 +8,7 @@ If you experience performance issues in Drill, you can typically identify the so
 
 Drill has an optimizer and a parallelizer that work together to plan a query. Drill creates logical, physical, and execution plans based on the available statistics for an associated set of files or data sources. The number of running Drill nodes and configured runtime settings contribute to how Drill plans and executes a query.
  
-You can use [EXPLAIN commands]({{ site.baseurl }}/docs/explain-commands/) to view the logical and physical plans for a query, however you cannot view the execution plan. To see how Drill executed a query, you can view the query profile in the Drill Web UI at `<drill_node_ip_address>:8047`.
+You can use [EXPLAIN commands]({{ site.baseurl }}/docs/explain-commands/) to view the logical and physical plans for a query, however you cannot view the execution plan. To see how Drill executed a query, you can view the query profile in the Drill Web Console at `<drill_node_ip_address>:8047`.
 
 ### Logical Plan  
 
@@ -26,7 +26,7 @@ Drill transforms the physical plan into an execution tree of minor fragments tha
 
 You can run the EXPLAIN command to view the physical plan for a query with or without costing formation. See EXPLAIN for Physical Plans and Costing Information. Analyze the cost-based query plan to identify the types of operators that Drill plans to use for the query and how much memory they will require. 
 
-Read the text output from bottom to top to understand the sequence of operators planned to execute the query. You can also view a visual representation of the physical plan in the Profile view of the Drill Web UI. See Query Profiles. You can modify the detailed JSON output, and submit it back to Drill through the Drill Web UI.
+Read the text output from bottom to top to understand the sequence of operators planned to execute the query. You can also view a visual representation of the physical plan in the Profile view of the Drill Web Console. See Query Profiles. You can modify the detailed JSON output, and submit it back to Drill through the Drill Web Console.
 
 The physical plan shows the major fragments and specific operators with correlating MajorFragmentIDs and OperatorIDs. See Operators. Major fragments are an abstract concept that represent a phase of the query execution. Major fragments do not perform any query tasks.
  
@@ -58,7 +58,7 @@ If you view the plan with costing information, you can see where the majority of
          
 **Modifying and Submitting a Physical Plan to Drill**
 
-You can test the performance of a physical plan that Drill generates, modify the plan and then re-submit it to Drill. For example, you can modify the plan to change the join ordering of tables. You can also submit physical plans created outside of Drill through the Drill Web UI.
+You can test the performance of a physical plan that Drill generates, modify the plan and then re-submit it to Drill. For example, you can modify the plan to change the join ordering of tables. You can also submit physical plans created outside of Drill through the Drill Web Console.
  
 **Note:** Only advanced users who know about query planning should modify and re-submit a physical plan.
  
@@ -66,7 +66,7 @@ To modify and re-submit a physical plan to Drill, complete the following steps:
 
 1. Run EXPLAIN PLAN FOR `<query>` to see the physical plan for your query.  
 2. Copy the JSON output of the physical plan, and modify as needed.  
-3. Navigate to the Drill Web UI at `<drill_node_ip_address>:8047`.  
+3. Navigate to the Drill Web Console at `<drill_node_ip_address>:8047`.  
 4. Select **Query** in the menu bar.  
 ![]({{ site.baseurl }}/docs/img/submit_plan.png)  
 

http://git-wip-us.apache.org/repos/asf/drill/blob/010ae6a6/_docs/performance-tuning/identifying-performance-issues/020-query-profiles.md
----------------------------------------------------------------------
diff --git a/_docs/performance-tuning/identifying-performance-issues/020-query-profiles.md b/_docs/performance-tuning/identifying-performance-issues/020-query-profiles.md
index badf486..24ee122 100755
--- a/_docs/performance-tuning/identifying-performance-issues/020-query-profiles.md
+++ b/_docs/performance-tuning/identifying-performance-issues/020-query-profiles.md
@@ -5,7 +5,7 @@ parent: "Identifying Performance Issues"
 
 A profile is a summary of metrics collected for each query that Drill executes. Query profiles provide information that you can use to monitor and analyze query performance. Drill creates a query profile from major, minor, operator, and input stream profiles. Each major fragment profile consists of a list of minor fragment profiles. Each minor fragment profile consists of a list of operator profiles. An operator profile consists of a list of input stream profiles. 
 
-You can view aggregate statistics across profile lists in the Profile tab of the Drill Web UI at `<drill_node_ip_address>:8047`. You can modify and resubmit queries, or cancel queries. For debugging purposes, you can use profiles in conjunction with Drill logs. See Log and Debug.
+You can view aggregate statistics across profile lists in the Profile tab of the Drill Web Console at `<drill_node_ip_address>:8047`. You can modify and resubmit queries, or cancel queries. For debugging purposes, you can use profiles in conjunction with Drill logs. See Log and Debug.
  
 Metrics in a query profile are associated with a coordinate system of IDs. Drill uses a coordinate system comprised of query, fragment, and operator identifiers to track query execution activities and resources. Drill assigns a unique QueryID to each query received and then assigns IDs to each fragment and operator that executes the query.
  
@@ -19,7 +19,7 @@ Fragment and operator IDs:
 
 ## Viewing a Query Profile  
 
-When you select the Profiles tab in the Drill Web UI at `<drill_node_ip_address>:8047`, you see a list of the last 100 queries than have run or that are currently running in the cluster.  
+When you select the Profiles tab in the Drill Web Console at `<drill_node_ip_address>:8047`, you see a list of the last 100 queries than have run or that are currently running in the cluster.  
 
 ![]({{ site.baseurl }}/docs/img/list_queries.png)
 
@@ -120,12 +120,12 @@ The physical plan view provides statistics about the actual cost of the query op
 
 ## Canceling a Query  
 
-You may want to cancel a query if it hangs or causes performance bottlenecks. You can cancel a query in the Profile tab of the Drill Web UI.
+You may want to cancel a query if it hangs or causes performance bottlenecks. You can cancel a query in the Profile tab of the Drill Web Console.
  
-To cancel a query from the Drill Web UI, complete the following steps:  
+To cancel a query from the Drill Web Console, complete the following steps:  
 
-1. Navigate to the Drill Web UI at `<drill_node_ip_address>:8047`.
-The Drill node from which you access the Drill Web UI must have an active Drillbit running.
+1. Navigate to the Drill Web Console at `<drill_node_ip_address>:8047`.
+The Drill node from which you access the Drill Web Console must have an active Drillbit running.
 2. Select Profiles in the toolbar.
 A list of running and completed queries appears.
 3. Click the query for which you want to see the profile.

http://git-wip-us.apache.org/repos/asf/drill/blob/010ae6a6/_docs/query-data/070-query-sys-tbl.md
----------------------------------------------------------------------
diff --git a/_docs/query-data/070-query-sys-tbl.md b/_docs/query-data/070-query-sys-tbl.md
index 0016e21..9a4bd19 100644
--- a/_docs/query-data/070-query-sys-tbl.md
+++ b/_docs/query-data/070-query-sys-tbl.md
@@ -83,7 +83,7 @@ Query the drillbits, version, options, boot, threads, and memory tables in the s
 The name of the node running the Drillbit service.
   * user_port  
 The user port address, used between nodes in a cluster for connecting to
-external clients and for the Drill Web UI.  
+external clients and for the Drill Web Console.  
   * control_port  
 The control port address, used between nodes for multi-node installation of
 Apache Drill.
@@ -211,7 +211,7 @@ otherwise, null.
 The name of the node running the Drillbit service.
   * user_port  
 The user port address, used between nodes in a cluster for connecting to
-external clients and for the Drill Web UI. 
+external clients and for the Drill Web Console. 
   * total_threads
 The peak thread count on the node.
   * busy_threads
@@ -233,7 +233,7 @@ The current number of live threads (daemon and non-daemon) on the node.
 The name of the node running the Drillbit service.
   * user_port  
 The user port address, used between nodes in a cluster for connecting to
-external clients and for the Drill Web UI.
+external clients and for the Drill Web Console.
   * heap_current
 The amount of memory being used on the heap, in bytes.
   * heap_max

http://git-wip-us.apache.org/repos/asf/drill/blob/010ae6a6/_docs/query-data/080-monitoring-and-canceling-queries-in-the-Drill-Web-UI.md
----------------------------------------------------------------------
diff --git a/_docs/query-data/080-monitoring-and-canceling-queries-in-the-Drill-Web-UI.md b/_docs/query-data/080-monitoring-and-canceling-queries-in-the-Drill-Web-UI.md
index 4f03c80..d11ad33 100644
--- a/_docs/query-data/080-monitoring-and-canceling-queries-in-the-Drill-Web-UI.md
+++ b/_docs/query-data/080-monitoring-and-canceling-queries-in-the-Drill-Web-UI.md
@@ -1,16 +1,16 @@
 ---
-title: "Monitoring and Canceling Queries in the Drill Web UI"
+title: "Monitoring and Canceling Queries in the Drill Web Console"
 parent: "Query Data"
 ---
-You can monitor and cancel queries from the Drill Web UI if you are [authorized]({{site.baseurl}}/docs/configuring-web-ui-and-rest-api-security/) to do so. To access the Drill
-Web UI, the Drillbit process must be running on the Drill node that you use to
-access the Drill Web UI.
+You can monitor and cancel queries from the Drill Web Console if you are [authorized]({{site.baseurl}}/docs/configuring-web-ui-and-rest-api-security/) to do so. To access the Drill
+Web Console, the Drillbit process must be running on the Drill node that you use to
+access the Drill Web Console.
 
-To monitor or cancel a query from the Drill Web UI, complete the following
+To monitor or cancel a query from the Drill Web Console, complete the following
 steps:
 
-  1. Navigate to the Drill Web UI at `<drill_node_ip_address>:8047.`  
-When you access the Drill Web UI, you see some general information about Drill
+  1. Navigate to the Drill Web Console at `<drill_node_ip_address>:8047.`  
+When you access the Drill Web Console, you see some general information about Drill
 running in your cluster, such as the nodes running the Drillbit process, the
 various ports Drill is using, and the amount of direct memory assigned to
 Drill.  

http://git-wip-us.apache.org/repos/asf/drill/blob/010ae6a6/_docs/query-data/querying-complex-data/005-querying-complex-data-introduction.md
----------------------------------------------------------------------
diff --git a/_docs/query-data/querying-complex-data/005-querying-complex-data-introduction.md b/_docs/query-data/querying-complex-data/005-querying-complex-data-introduction.md
index 099e047..16aebe4 100644
--- a/_docs/query-data/querying-complex-data/005-querying-complex-data-introduction.md
+++ b/_docs/query-data/querying-complex-data/005-querying-complex-data-introduction.md
@@ -48,7 +48,7 @@ your own queries, you need to be aware of the basic data types in these files:
   * boolean values: true, false
 
 Check that you have the following configuration setting for JSON files in the
-Drill Web UI (`dfs` storage plugin configuration):
+Drill Web Console (`dfs` storage plugin configuration):
 
     "json" : {
       "type" : "json"

http://git-wip-us.apache.org/repos/asf/drill/blob/010ae6a6/_docs/tutorials/learn-drill-with-the-mapr-sandbox/010-installing-the-apache-drill-sandbox.md
----------------------------------------------------------------------
diff --git a/_docs/tutorials/learn-drill-with-the-mapr-sandbox/010-installing-the-apache-drill-sandbox.md b/_docs/tutorials/learn-drill-with-the-mapr-sandbox/010-installing-the-apache-drill-sandbox.md
index 9030a58..316bfe1 100755
--- a/_docs/tutorials/learn-drill-with-the-mapr-sandbox/010-installing-the-apache-drill-sandbox.md
+++ b/_docs/tutorials/learn-drill-with-the-mapr-sandbox/010-installing-the-apache-drill-sandbox.md
@@ -54,7 +54,7 @@ VMware Player or VMware Fusion:
               Open a browser on your host machine and enter the URL in the browser's address field.
               You can access the host via SSH by ssh mapr@localhost -p 2222
               Log in to this virtual machine: Linux/Windows <Alt+F2>, Mac OS X <Options+F5>
-**Note:** The URL provided corresponds to the Web UI in Apache Drill.  
+**Note:** The URL provided corresponds to the Web Console in Apache Drill.  
      
 6. Verify that a DNS entry was created on the host machine for the virtual machine. If not, create the entry.
     * For Linux and Mac, create the entry in `/etc/hosts`.  
@@ -62,7 +62,7 @@ VMware Player or VMware Fusion:
      
            Example: `127.0.1.1 <vm_hostname>`
 
-7. Navigate to [localhost:8047](http://localhost:8047) to experience the Drill Web UI, or log in to the sandbox through the command line.  
+7. Navigate to [localhost:8047](http://localhost:8047) to experience the Drill Web Console, or log in to the sandbox through the command line.  
 
    * Login using ssh as described in ["Getting to Know the Sandbox"]({{site.baseurl}}/docs/getting-to-know-the-drill-sandbox). When prompted, enter `mapr` as the login name and password.  
    * Alternatively, access the command line on the VM: Press Alt+F2 on Windows or Option+F5 on Mac.  
@@ -112,9 +112,9 @@ network, select **Host-only Networks** and the **Host-Only Ethernet**.
               You can access the host via SSH by ssh mapr@localhost -p 2222
               Log in to this virtual machine: Linux/Windows <Alt+F2>, Mac OS X <Options+F5>  
 
-       **Note:** The URL provided corresponds to the Web UI in Apache Drill.        
+       **Note:** The URL provided corresponds to the Web Console in Apache Drill.        
 
-10. Navigate to [localhost:8047](http://localhost:8047) to experience the Drill Web UI, or log into the sandbox through the command line.  
+10. Navigate to [localhost:8047](http://localhost:8047) to experience the Drill Web Console, or log into the sandbox through the command line.  
        * Login using ssh as described in ["Getting to Know the Sandbox"]({{site.baseurl}}/docs/getting-to-know-the-drill-sandbox). When prompted, enter `mapr` as the login name and password.  
        * Alternatively, access the command line on the VM: Press Alt+F2 on Windows or Option+F5 on Mac.   
 

http://git-wip-us.apache.org/repos/asf/drill/blob/010ae6a6/_docs/tutorials/learn-drill-with-the-mapr-sandbox/020-getting-to-know-the-drill-sandbox.md
----------------------------------------------------------------------
diff --git a/_docs/tutorials/learn-drill-with-the-mapr-sandbox/020-getting-to-know-the-drill-sandbox.md b/_docs/tutorials/learn-drill-with-the-mapr-sandbox/020-getting-to-know-the-drill-sandbox.md
index d3b4994..275be55 100755
--- a/_docs/tutorials/learn-drill-with-the-mapr-sandbox/020-getting-to-know-the-drill-sandbox.md
+++ b/_docs/tutorials/learn-drill-with-the-mapr-sandbox/020-getting-to-know-the-drill-sandbox.md
@@ -22,7 +22,7 @@ Drill includes a shell for connecting to relational databases and executing SQL
 In this tutorial you query a number of data sets, including Hive and HBase, and files on the file system, such as CSV, JSON, and Parquet files. To access these diverse data sources, you connect Drill to storage plugins. 
 
 ## Storage Plugin Overview
-You use a [storage plugins]({{ site.baseurl }}/docs/connect-a-data-source-introduction) to connect to a data source, such as a file or the Hive metastore. Take a look at the storage plugin definitions by opening the Storage tab in the Drill Web UI. Launch a web browser and go to: `http://<IP address>:8047/storage`. 
+You use a [storage plugins]({{ site.baseurl }}/docs/connect-a-data-source-introduction) to connect to a data source, such as a file or the Hive metastore. Take a look at the storage plugin definitions by opening the Storage tab in the Drill Web Console. Launch a web browser and go to: `http://<IP address>:8047/storage`. 
 
 The control panel for managing storage plugins appears.
 

http://git-wip-us.apache.org/repos/asf/drill/blob/010ae6a6/_docs/tutorials/learn-drill-with-the-mapr-sandbox/030-lesson-1-learn-about-the-data-set.md
----------------------------------------------------------------------
diff --git a/_docs/tutorials/learn-drill-with-the-mapr-sandbox/030-lesson-1-learn-about-the-data-set.md b/_docs/tutorials/learn-drill-with-the-mapr-sandbox/030-lesson-1-learn-about-the-data-set.md
index dc2ce89..f6304f9 100644
--- a/_docs/tutorials/learn-drill-with-the-mapr-sandbox/030-lesson-1-learn-about-the-data-set.md
+++ b/_docs/tutorials/learn-drill-with-the-mapr-sandbox/030-lesson-1-learn-about-the-data-set.md
@@ -32,7 +32,7 @@ the Drill shell, type:
 
 `0: jdbc:drill:> !quit`
 
-Examples in this tutorial use the Drill shell. You can also execute queries using the Drill Web UI.
+Examples in this tutorial use the Drill shell. You can also execute queries using the Drill Web Console.
 
 ### Enable the DECIMAL Data Type
 


Mime
View raw message